From: Nigel Cunningham <ncunningham@crca.org.au>
To: Gerald Schaefer <gerald.schaefer@de.ibm.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Yasunori Goto <y-goto@jp.fujitsu.com>
Subject: Re: [PATCH] hibernate / memory hotplug: always use for_each_populated_zone()
Date: Tue, 21 Jul 2009 07:29:58 +1000 [thread overview]
Message-ID: <4A64E1D6.8090102@crca.org.au> (raw)
In-Reply-To: <1248103551.23961.0.camel@localhost.localdomain>
Hi.
Gerald Schaefer wrote:
> From: Gerald Schaefer <gerald.schaefer@de.ibm.com>
>
> Use for_each_populated_zone() instead of for_each_zone() in hibernation
> code. This fixes a bug on s390, where we allow both config options
> HIBERNATION and MEMORY_HOTPLUG, so that we also have a ZONE_MOVABLE
> here. We only allow hibernation if no memory hotplug operation was
> performed, so in fact both features can only be used exclusively, but
> this way we don't need 2 differently configured (distribution) kernels.
>
> If we have an unpopulated ZONE_MOVABLE, we allow hibernation but run
> into a BUG_ON() in memory_bm_test/set/clear_bit() because hibernation
> code iterates through all zones, not only the populated zones, in
> several places. For example, swsusp_free() does for_each_zone() and
> then checks for pfn_valid(), which is true even if the zone is not
> populated, resulting in a BUG_ON() later because the pfn cannot be
> found in the memory bitmap.
I agree with your logic and patch, but doesn't this also imply that the
s390 implementation pfn_valid should be changed to return false for
those pages?
Regards,
Nigel
next prev parent reply other threads:[~2009-07-20 21:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 15:25 [PATCH] hibernate / memory hotplug: always use for_each_populated_zone() Gerald Schaefer
2009-07-20 16:04 ` Rafael J. Wysocki
2009-07-20 16:15 ` KOSAKI Motohiro
2009-07-20 21:29 ` Nigel Cunningham [this message]
2009-07-21 7:15 ` Heiko Carstens
2009-07-21 7:21 ` Nick Piggin
2009-07-21 7:38 ` KAMEZAWA Hiroyuki
2009-07-21 14:11 ` Rafael J. Wysocki
2009-07-22 0:25 ` KAMEZAWA Hiroyuki
2009-07-22 0:38 ` KAMEZAWA Hiroyuki
2009-07-22 17:49 ` Rafael J. Wysocki
2009-07-22 23:46 ` KAMEZAWA Hiroyuki
2009-07-29 11:20 ` Gerald Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A64E1D6.8090102@crca.org.au \
--to=ncunningham@crca.org.au \
--cc=akpm@linux-foundation.org \
--cc=gerald.schaefer@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=schwidefsky@de.ibm.com \
--cc=y-goto@jp.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox