linux-kernel - Re: what's the incompatibility between hibernation and hotplug?memory

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 28 Mar 2008 00:44:00 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Pavel Machek <pavel@....cz>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: what's the incompatibility between hibernation and hotplug?memory

On Friday, 28 of March 2008, Pavel Machek wrote:
> On Thu 2008-03-27 21:55:01, Rafael J. Wysocki wrote:
> > On Thursday, 27 of March 2008, Jeremy Fitzhardinge wrote:
> > > Pavel Machek wrote:
> > > > Hi!
> > > >
> > > >   
> > > >>> I noticed that Kconfig warns that hibernation and hotplug memory are not 
> > > >>> compatible.  What's the issue?
> > > >>>       
> > > >> Generally, we might not be able to handle memory unplugged at a wrong time
> > > >> (eg. after we've created the image).
> > > >>
> > > >> Which part of Kconfig says that exactly?
> > > >>     
> > > >
> > > > Actually I believe it is simpler than that. We were not prepared to
> > > > deal with memory holes in hibernation code, so we just disabled it in
> > > > Kconfig...
> > > 
> > > Doesn't that mean its generally incompatible with non-flatmem memory 
> > > arrangements rather than hotplug memory specifically?
> > 
> > No, it should work with NUMA nowadays, actually.
> > 
> > Perhaps it's worth trying it with hotplug memory and see what problems arise?
> 
> Good. I believe it is good chance it will work with hotplug, too... as
> long as memory is not inserted/removed during suspend/resume.

Well, there may be a problem if it's inserted after we've created the image
and before powering off, because the resumed kernel will not have any idea of
the new memory.  It probably will require us to add some resume callbacks
for the memory hotplugging to handle this cleanly.

Thanks,
Rafael
--
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/