All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: what's the incompatibility between hibernation and hotplug?memory
Date: Thu, 3 Apr 2008 00:25:55 +0200	[thread overview]
Message-ID: <20080402222555.GF4644@elf.ucw.cz> (raw)
In-Reply-To: <200803280044.00982.rjw@sisk.pl>

On Fri 2008-03-28 00:44:00, Rafael J. Wysocki wrote:
> 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.

Well, "not having any idea of new memory" should not lead to big
problems. 

"Not being aware that memory was removed" would be worse ;-).

And I think that we have the ammount of memory check, and will refuse
the resume which is good failsafe behaviour.

...so someone interested should just test it ;-).
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2008-04-02 22:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 23:17 what's the incompatibility between hibernation and hotplug memory Jeremy Fitzhardinge
2008-03-26 23:27 ` Rafael J. Wysocki
2008-03-26 23:33   ` Jeremy Fitzhardinge
2008-03-27  8:49   ` Pavel Machek
2008-03-27 20:49     ` Jeremy Fitzhardinge
2008-03-27 20:55       ` Rafael J. Wysocki
2008-03-27 23:38         ` what's the incompatibility between hibernation and hotplug?memory Pavel Machek
2008-03-27 23:44           ` Rafael J. Wysocki
2008-04-02 22:25             ` Pavel Machek [this message]

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=20080402222555.GF4644@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.