| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20060809115145.GT3308@elf.ucw.cz> Date: Wed, 9 Aug 2006 13:51:45 +0200 From: Pavel Machek <pavel@...e.cz> To: "Rafael J. Wysocki" <rjw@...k.pl> Cc: LKML <linux-kernel@...r.kernel.org>, Linux PM <linux-pm@...l.org> Subject: Re: [RFC][PATCH -mm 3/5] swsusp: Fix handling of highmem Hi! > Make swsusp handle highmem pages similarly to the pages of the "normal" > memory. Is it feasible to create kernel/power/highmem.c? > include/linux/suspend.h | 6 > kernel/power/power.h | 2 > kernel/power/snapshot.c | 822 ++++++++++++++++++++++++++++++++++++------------ > kernel/power/swap.c | 2 > kernel/power/swsusp.c | 53 +-- > kernel/power/user.c | 2 > mm/vmscan.c | 3 > 7 files changed, 658 insertions(+), 232 deletions(-) +400 lines for highmem... I hope highmem dies, dies, dies. Anyway, I'd hate to debug this at the same time as the bitmap code. Can we get the bitmaps in, wait for a while, and only then change highmem handling? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists