From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Dave Jones" <davej@redhat.com>
Cc: "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: Mon, 19 May 2008 22:53:58 -0700 [thread overview]
Message-ID: <86802c440805192253s34b3acb2r63c657db86676792@mail.gmail.com> (raw)
In-Reply-To: <200805200409.m4K49Ybn024338@gelk.kernelslacker.org>
On Mon, May 19, 2008 at 9:09 PM, Dave Jones <davej@redhat.com> wrote:
> * Add an enablepat boot parameter, useful for testing CPUs not yet
> added to the whitelist.
> * Don't try to enable PAT if it was never enabled in the first place.
>
> Signed-off-by: Dave Jones <davej@redhat.com>
>
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index 72c07a0..e179c22 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -236,6 +236,10 @@ and is between 256 and 4096 characters. It is defined in the file
> try_unsupported: try to drive unsupported chipsets
> (may crash computer or cause data corruption)
>
> + enablepat [i386,x86-64]
> + Force the CPU's PAT feature to be used even if it
> + isn't in the kernels whitelist.
> +
> enable_timer_pin_1 [i386,x86-64]
> Enable PIN 1 of APIC timer
> Can be useful to work around chipset bugs
> diff --git a/arch/x86/kernel/cpu/addon_cpuid_features.c b/arch/x86/kernel/cpu/addon_cpuid_features.c
> index c2e1ce3..6ce3202 100644
> --- a/arch/x86/kernel/cpu/addon_cpuid_features.c
> +++ b/arch/x86/kernel/cpu/addon_cpuid_features.c
> @@ -50,9 +50,28 @@ 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);
> +
> +
> #ifdef CONFIG_X86_PAT
> void __cpuinit validate_pat_support(struct cpuinfo_x86 *c)
> {
> + if (!test_cpu_cap(c, X86_FEATURE_PAT))
> + return;
> +
> + if (forcepat == 1) {
> + printk(KERN_INFO "Force enabling PAT\n");
> + set_cpu_cap(c, X86_FEATURE_PAT);
you don't need to set that bit again...
prevoious !test_cpu_cap(..) already get out.
> + return;
> + }
> +
> switch (c->x86_vendor) {
> case X86_VENDOR_AMD:
> if (c->x86 >= 0xf && c->x86 <= 0x11)
>
YH
next prev parent reply other threads:[~2008-05-20 5:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 4:09 Dave Jones
2008-05-20 5:53 ` Yinghai Lu [this message]
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
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=86802c440805192253s34b3acb2r63c657db86676792@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=davej@redhat.com \
--cc=hpa@zytor.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
all inboxes | Powered by JetHome®