From: Andrew Morton <akpm@osdl.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: prevent swsusp with PAE
Date: Thu, 31 Aug 2006 15:48:28 -0700 [thread overview]
Message-ID: <20060831154828.4313327c.akpm@osdl.org> (raw)
In-Reply-To: <20060831223521.GB31125@elf.ucw.cz>
On Fri, 1 Sep 2006 00:35:21 +0200
Pavel Machek <pavel@ucw.cz> wrote:
> > > diff --git a/include/asm-i386/suspend.h b/include/asm-i386/suspend.h
> > > index 08be1e5..01cd812 100644
> > > --- a/include/asm-i386/suspend.h
> > > +++ b/include/asm-i386/suspend.h
> > > @@ -16,6 +16,15 @@ arch_prepare_suspend(void)
> > > printk(KERN_ERR "PSE is required for swsusp.\n");
> > > return -EPERM;
> > > }
> > > +
> > > +#ifdef CONFIG_X86_PAE
> > > + printk(KERN_ERR "swsusp is incompatible with PAE.\n");
> > > + /* This is actually instance of the same problem. We need
> > > + identity mapping self-contained in swsusp_pg_dir, and PAE
> > > + prevents that. Solution could be copied from x86_64. */
> > > + return -EPERM;
> > > +#endif
> > > +
> > > return 0;
> > > }
> >
> > Why not do this in Kconfig??
>
> Well, Kconfig does not provide natural place for comments, and
> disappearing config option is sure to confuse people. But of course I
> can do it.
It would be more conventional.
I think what this really points at is a weakness in the menuconfig/xconfig/etc
user interfaces. It should be possible to navigate to the presently-disabled
config option and ask it "why can't I turn you on?".
next prev parent reply other threads:[~2006-08-31 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 13:53 Pavel Machek
2006-08-31 17:43 ` Andrew Morton
2006-08-31 22:35 ` Pavel Machek
2006-08-31 22:48 ` Randy.Dunlap
2006-08-31 22:48 ` Andrew Morton [this message]
2006-08-31 22:52 ` Pavel Machek
2006-08-31 23:05 ` Randy.Dunlap
2006-09-01 0:16 ` Andrew Morton
2006-09-01 0:44 ` Randy.Dunlap
2006-09-02 23:16 ` Pavel Machek
2006-09-01 7:22 ` Jan Engelhardt
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=20060831154828.4313327c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome