From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jan Beulich <jbeulich@novell.com>,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: simplify HIGHMEM-related Kconfig entries
Date: Thu, 15 Jan 2009 09:10:20 -0800 [thread overview]
Message-ID: <496F6DFC.90006@zytor.com> (raw)
In-Reply-To: <20090115085728.GA28607@elte.hu>
Ingo Molnar wrote:
>>>
>>> No highmem - No highmem, no PAE
>>> HIGHMEM4G - Highmem, no PAE
>>> HIGHMEM64G - Highmem, PAE
>>>
>>> So X86_PAE and HIGHMEM4G is a bit of a contradiction. I haven't looked
>>> at the logic in detail, or remember offhand if there have been any
>>> weakening of the definitions above; e.g. someone could have implemented
>>> a way to do PAE without highmem, to get access to the NX bits.
>> Exactly - .23 made PAE an independently selectable option (in
>> particular, the no-highmem+PAE combination is now valid), but I can't
>> see why it added the !HIGHMEM4G dependency.
>
> There's no deep reason, it just has never really been tested that way. I
> think we should try it.
If so, what would be the difference between HIGHMEM4G and HIGHMEM64G in
that case at all?
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-01-15 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 12:31 [PATCH] x86: simplify HIGHMEM-related Kconfig entries Jan Beulich
2009-01-14 19:39 ` H. Peter Anvin
2009-01-15 8:53 ` Jan Beulich
2009-01-15 8:57 ` Ingo Molnar
2009-01-15 17:10 ` H. Peter Anvin [this message]
2009-01-16 11:57 ` Jan Beulich
2009-01-16 18:22 ` H. Peter Anvin
2009-01-16 21:18 ` Ingo Molnar
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=496F6DFC.90006@zytor.com \
--to=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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).