From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [RFC][PATCH -mm 3/5] swsusp: Fix handling of highmem Date: Wed, 9 Aug 2006 13:51:45 +0200 Message-ID: <20060809115145.GT3308@elf.ucw.cz> References: <200608091152.49094.rjw@sisk.pl> <200608091209.03695.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <200608091209.03695.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org To: "Rafael J. Wysocki" Cc: LKML , Linux PM List-Id: linux-pm@vger.kernel.org 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