From: Pavel Machek <pavel@ucw.cz>
To: yhlu.kernel@gmail.com
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: pat cpu feature bit setting for known cpus
Date: Fri, 28 Mar 2008 14:41:02 +0100 [thread overview]
Message-ID: <20080328134102.GA4404@ucw.cz> (raw)
In-Reply-To: <200803242324.35357.yhlu.kernel@gmail.com>
On Mon 2008-03-24 23:24:34, Yinghai Lu wrote:
> [PATCH] x86: pat cpu feature bit setting for known cpus
>
> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
>
> diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
> index eb94460..b186047 100644
> --- a/arch/x86/kernel/cpu/common.c
> +++ b/arch/x86/kernel/cpu/common.c
> @@ -309,6 +309,19 @@ static void __cpuinit early_get_cap(struct cpuinfo_x86 *c)
>
> }
>
> + clear_cpu_cap(c, X86_FEATURE_PAT);
> +
> + switch (c->x86_vendor) {
> + case X86_VENDOR_AMD:
> + if (c->x86 >= 0xf && c->x86 <= 0x11)
> + set_cpu_cap(c, X86_FEATURE_PAT);
> + break;
> + case X86_VENDOR_INTEL:
> + if (c->x86 == 0xF || (c->x86 == 6 && c->x86_model >= 15))
> + set_cpu_cap(c, X86_FEATURE_PAT);
> + break;
> + }
> +
> }
>
> /*
> @@ -397,6 +410,18 @@ static void __cpuinit generic_identify(struct cpuinfo_x86 *c)
> init_scattered_cpuid_features(c);
> }
>
> + clear_cpu_cap(c, X86_FEATURE_PAT);
> +
> + switch (c->x86_vendor) {
> + case X86_VENDOR_AMD:
> + if (c->x86 >= 0xf && c->x86 <= 0x11)
> + set_cpu_cap(c, X86_FEATURE_PAT);
> + break;
> + case X86_VENDOR_INTEL:
> + if (c->x86 == 0xF || (c->x86 == 6 && c->x86_model >= 15))
> + set_cpu_cap(c, X86_FEATURE_PAT);
> + break;
> + }
> }
>
Cut&paste programming? Can you make it a function?
> diff --git a/arch/x86/kernel/setup_64.c b/arch/x86/kernel/setup_64.c
> index 3f1dc97..ddaaaaa 100644
> --- a/arch/x86/kernel/setup_64.c
> +++ b/arch/x86/kernel/setup_64.c
> @@ -979,12 +979,19 @@ static void __cpuinit early_identify_cpu(struct cpuinfo_x86 *c)
> if (c->extended_cpuid_level >= 0x80000007)
> c->x86_power = cpuid_edx(0x80000007);
>
> +
> + clear_cpu_cap(c, X86_FEATURE_PAT);
> switch (c->x86_vendor) {
> case X86_VENDOR_AMD:
> early_init_amd(c);
> + if (c->x86 >= 0xf && c->x86 <= 0x11)
> + set_cpu_cap(c, X86_FEATURE_PAT);
> break;
> case X86_VENDOR_INTEL:
> early_init_intel(c);
> + if (c->x86 == 0xF || (c->x86 == 6 && c->x86_model >= 15))
> + set_cpu_cap(c, X86_FEATURE_PAT);
> break;
> }
one more copy...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-03-28 13:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 6:24 [PATCH] x86: pat cpu feature bit setting for known cpus Yinghai Lu
2008-03-25 10:58 ` Ingo Molnar
2008-03-25 13:38 ` H. Peter Anvin
2008-03-25 18:03 ` Yinghai Lu
2008-03-25 19:08 ` Venki Pallipadi
2008-03-25 20:08 ` Ingo Molnar
2008-03-25 20:38 ` H. Peter Anvin
2008-03-25 23:01 ` H. Peter Anvin
2008-03-25 23:05 ` Yinghai Lu
2008-03-25 23:06 ` H. Peter Anvin
2008-03-25 23:08 ` Yinghai Lu
2008-03-25 23:38 ` Pallipadi, Venkatesh
2008-03-26 0:01 ` Yinghai Lu
2008-03-26 0:10 ` H. Peter Anvin
2008-03-28 13:41 ` Pavel Machek [this message]
2008-03-28 14:51 ` Yinghai Lu
2008-03-30 11:43 ` dean gaudet
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=20080328134102.GA4404@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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