xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Frank Pan <frankpzh@gmail.com>,
	Ian Campbell <Ian.Campbell@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Shriram Rajagopalan <rshriram@cs.ubc.ca>
Subject: Re: Q: Clarification about extra option ..Re: Re: [PATCH] pvops: Make suspend work when CONFIG_SUSPEND=n
Date: Fri, 4 Mar 2011 21:05:48 +0100	[thread overview]
Message-ID: <201103042105.49031.rjw@sisk.pl> (raw)
In-Reply-To: <20110304182602.GA4004@dumpdata.com>

On Friday, March 04, 2011, Konrad Rzeszutek Wilk wrote:
> .. snip..
> > >>  Someone suggested creating a new user visible hibernate symbol that would
> > >> solve this issue and make the main hibernate logic depend on this symbol rather
> > >> than the HIBERNATE symbol. I could certainly spin up a patch for that but nobody
> > >> seemed to have reached a conclusion.
> > >
> > > Please do. I was under the understanding that we were waiting for a victi^H^H^Hvolunteer
> > > to implement that.
> > >
> > > That was the only thing gatting your patchset going in.
> > >
> > >
> > 
> > I certainly would have long time ago but for this comment in the thread
> > "xen: fix XEN_SAVE_RESTORE Kconfig dependencies"
> > 
> > Rafael:
> >  I think we can introduce CONFIG_HIBERNATE_INTERFACE that will be user-visible
> > option instead of CONFIG_HIBERNATION and will select the latter.  Then,
> > CONFIG_XEN_SAVE_RESTORE will also be able to select CONFIG_HIBERNATION without
> > building the hibernate interface in, which will prevent user space from being
> > confused, but that will cause too much code to be built anyway.
> > 
> > If by "too much code to be built", he meant the increase in kernel
> > image size, then its not much of a deal :P.
> > But if he meant, "too much code rework", then it is an issue.
> 
> The idea here is that the /sys/power/state won't be exposed with the "disk"
> option.
> 
> > 
> > But IMO, the CONFIG_HIBERNATE_INTERFACE needs to go in,
> > only in the main hibernation initiator logic, as we still need the
> > CONFIG_HIBERNATE
> > pieces of every driver anyway (their freeze/thaw routines).
> 
> Right. The idea here is to seperate the sysfs interface to be behind
> another config option. So you can still enable the hibernate kernel code
> but without exposing it to the userland.
> 
> Rafael,
> 
> That is the general idea, right?

Right.  We can only make the code in kernel/power/snapshot.c depend on
CONFIG_HIBERNATE_INTERFACE and the ioctl interface too.

Thanks,
Rafael

      parent reply	other threads:[~2011-03-04 20:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 11:20 [PATCH] pvops: Make suspend work when CONFIG_SUSPEND=n Frank Pan
2011-03-04 11:35 ` Ian Campbell
2011-03-04 11:45   ` Frank Pan
2011-03-04 11:52     ` Ian Campbell
2011-03-04 15:42       ` Shriram Rajagopalan
2011-03-04 15:56         ` Konrad Rzeszutek Wilk
2011-03-04 16:29           ` Shriram Rajagopalan
2011-03-04 18:26             ` Q: Clarification about extra option ..Re: " Konrad Rzeszutek Wilk
2011-03-04 19:49               ` Shriram Rajagopalan
2011-03-04 20:07                 ` Rafael J. Wysocki
2011-03-06 20:31                   ` Shriram Rajagopalan
2011-03-06 22:12                     ` Rafael J. Wysocki
2011-03-07 12:44                       ` Stefano Stabellini
2011-03-07 16:33                         ` Shriram Rajagopalan
2011-03-07 17:53                           ` Konrad Rzeszutek Wilk
2011-03-07 18:17                             ` Shriram Rajagopalan
2011-03-08 15:53                               ` Konrad Rzeszutek Wilk
2011-03-07 17:39                       ` Konrad Rzeszutek Wilk
2011-03-04 20:05               ` Rafael J. Wysocki [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=201103042105.49031.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Jeremy.Fitzhardinge@citrix.com \
    --cc=frankpzh@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=rshriram@cs.ubc.ca \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).