From: Rene Herman <rene.herman@keyaccess.nl>
To: 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>,
hpa@zytor.com
Subject: Re: [X86] Add a boot parameter to force-enable PAT
Date: Tue, 20 May 2008 23:49:26 +0200 [thread overview]
Message-ID: <48334766.1020701@keyaccess.nl> (raw)
In-Reply-To: <20080520195846.GA29806@redhat.com>
On 20-05-08 21:58, Dave Jones wrote:
> diff --git a/arch/x86/kernel/cpu/addon_cpuid_features.c b/arch/x86/kernel/cpu/addon_cpuid_features.c
> index c2e1ce3..e22e809 100644
> --- a/arch/x86/kernel/cpu/addon_cpuid_features.c
> +++ b/arch/x86/kernel/cpu/addon_cpuid_features.c
> @@ -50,9 +50,27 @@ void __cpuinit init_scattered_cpuid_features(struct cpuinfo_x86 *c)
> }
> }
>
> +static int forcepat;
> +
> +static int __init x86_forcepat_setup(char *s)
> +{
> + forcepat = 1;
> + return 1;
> +}
> +__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?
> +
> +
> #ifdef CONFIG_X86_PAT
> void __cpuinit validate_pat_support(struct cpuinfo_x86 *c)
> {
> + if (!test_cpu_cap(c, X86_FEATURE_PAT))
> + return;
It seems you needn't test this, the !cpu_has_pat test in pat_init() will
trigger and user knows best... :-)
> +
> + if (forcepat == 1) {
> + printk(KERN_INFO "Force enabling PAT\n");
> + return;
> + }
> +
> switch (c->x86_vendor) {
> case X86_VENDOR_AMD:
> if (c->x86 >= 0xf && c->x86 <= 0x11)
Rene.
next prev parent reply other threads:[~2008-05-20 21: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 [this message]
2008-05-20 22:21 ` H. Peter Anvin
2008-05-20 22:42 ` Rene Herman
2008-05-20 22:42 ` H. Peter Anvin
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=48334766.1020701@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mingo@elte.hu \
--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