From: "H. Peter Anvin" <hpa@zytor.com>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Dave Jones <davej@redhat.com>, Mikael Pettersson <mikpe@it.uu.se>,
Yinghai Lu <yhlu.kernel@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [X86] Add a boot parameter to force-enable PAT
Date: Tue, 20 May 2008 15:42:49 -0700 [thread overview]
Message-ID: <483353E9.7090001@zytor.com> (raw)
In-Reply-To: <483353DB.7010708@keyaccess.nl>
Rene Herman wrote:
> On 21-05-08 00:21, H. Peter Anvin wrote:
>
>> Rene Herman wrote:
>>>> +}
>>>> +__setup("enablepat", x86_forcepat_setup);
>>>
>>> This should probably be called plain "pat" to mirror
>>> arch/x86/mm/pat.c "nopat" force off parameter. That by the way is an
>>> early_param which I guess this should then also be?
>>>
>>
>> Either that or "pat={off,on,force}" to give space for other options...
>> would mean keeping "nopat" around as an alias for now, though...
>
> Yes, that would be nicer. As to the alias; "nopat" hasn't been in a
> released kernel yet so should be okay to do away with? It's not like
> it's in Documentation/kernel-parameters.txt or anything... ;-/
>
OK, just double-checked... since it's not in Linus we can still change
it, and as so I'd suggest the pat= option.
-hpa
next prev parent reply other threads:[~2008-05-20 22:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 4:09 [X86] Add a boot parameter to force-enable PAT Dave Jones
2008-05-20 5:53 ` Yinghai Lu
2008-05-20 13:23 ` Dave Jones
2008-05-20 14:41 ` Mikael Pettersson
2008-05-20 19:58 ` Dave Jones
2008-05-20 21:49 ` Rene Herman
2008-05-20 22:21 ` H. Peter Anvin
2008-05-20 22:42 ` Rene Herman
2008-05-20 22:42 ` H. Peter Anvin [this message]
2008-05-20 22:56 ` Dave Jones
2008-05-21 1:10 ` Rene Herman
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=483353E9.7090001@zytor.com \
--to=hpa@zytor.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mingo@elte.hu \
--cc=rene.herman@keyaccess.nl \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.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