[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201103292139.35645.rjw@sisk.pl>
Date: Tue, 29 Mar 2011 21:39:35 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Ian Campbell <Ian.Campbell@...rix.com>
Cc: "linux-pm@...ts.linux-foundation.org"
<linux-pm@...ts.linux-foundation.org>,
Shriram Rajagopalan <rshriram@...ubc.ca>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH] PM / Hibernate: Introduce CONFIG_HIBERNATE_INTERFACE
On Tuesday, March 29, 2011, Ian Campbell wrote:
> Hi Rafael,
>
> On Sat, 2011-03-26 at 11:29 +0000, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki <rjw@...k.pl>
> >
> > Xen save/restore is going to use hibernate device callbacks for
> > quiescing devices and putting them back to normal operations and it
> > would need to select CONFIG_HIBERNATION for this purpose. However,
> > that also would cause the hibernate interfaces for user space to be
> > enabled, which might confuse user space, because the Xen kernels
> > don't support hibernation. Moreover, it would be wasteful, as it
> > would make the Xen kernels include a substantial amount of code that
> > they would never use.
> >
> > To address this issue introduce new power management Kconfig option
> > CONFIG_HIBERNATE_INTERFACE, such that the hibernate interfaces for
> > user space and the image-handling code will depend on it and it will
> > select CONFIG_HIBERNATION. Then, Xen save/restore will be able to
> > select CONFIG_HIBERNATION without dragging the entire hibernate code
> > along with it.
> >
> > Signed-off-by: Rafael J. Wysocki <rjw@...k.pl>
>
> Were you planning to put this forward for 2.6.39 or are you waiting for
> 2.6.40?
I'm goint to push it for 2.6.39. In fact, I'm going to send the pull request
shortly.
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/
Powered by blists - more mailing lists