Hi.

On Mon, 2008-11-03 at 12:51 -0800, Andrew Morton wrote:

On Wed, 29 Oct 2008 13:25:00 +0100
"Rafael J. Wysocki" [off-list ref] wrote:

quoted

On Wednesday, 29 of October 2008, Pavel Machek wrote:

quoted

hibernation + memory hotplug was disabled in kconfig because we could
not handle hibernation + sparse mem at some point. It seems to work
now, so I guess we can enable it.

OK, if "it seems to work now" means that it has been tested and confirmed to
work, no objection from me.

yes, that was not a terribly confidence-inspiring commit message.

3947be1969a9ce455ec30f60ef51efb10e4323d1 said "For now, disable memory
hotplug when swsusp is enabled.  There's a lot of churn there right
now.  We'll fix it up properly once it calms down." which is also
rather rubbery.  

Cough up, guys: what was the issue with memory hotplug and swsusp, and
is it indeed now fixed?

IIRC, at least part of the question was "What if memory is hot unplugged
in the middle of hibernating, or between hibernating and
resuming." (Would apply to cold unplugging too).

Regards,

Nigel