public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: 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 recent Centaur CPUs to PAT whitelist
Date: Thu, 22 May 2008 13:02:23 -0400	[thread overview]
Message-ID: <20080522170223.GA32314@redhat.com> (raw)
In-Reply-To: <4835A3EC.1030307@zytor.com>

On Thu, May 22, 2008 at 09:48:44AM -0700, H. Peter Anvin wrote:
 > Dave Jones wrote:
 > > On Wed, May 21, 2008 at 04:56:28PM -0700, H. Peter Anvin wrote:
 > >  > Dave Jones wrote:
 > >  > > 
 > >  > > From conversation with Centaur engineers, both the newer generations
 > >  > > of the VIA C7, and their future CPUs support PAT, with no known errata.
 > >  > > 
 > >  > > Signed-off-by: Dave Jones <davej@redhat.com>
 > >  > > 
 > >  > 
 > >  > Question: are there any VIA CPUs that display the PAT CPUID flag that 
 > >  > aren't covered by the above?
 > > 
 > > No.  They only added PAT support with the current Esther (C7) generation iirc.
 > > 
 > 
 > OK, so we should just enable VIA unconditionally as long as PAT is 
 > displayed and not worry about generation numbers; same with Transmeta 
 > (only the Transmeta Efficeon supported PAT, and it had a 
 > strictly-coherent memory system.)

Like so?

Unconditionally enable PAT support on Centaur and Transmeta CPUs.
All known models that advertise PAT have no known errata.

Signed-off-by: Dave Jones <davej@redhat.com>

--- linux-2.6/arch/x86/kernel/cpu/addon_cpuid_features.c~	2008-05-22 12:59:07.000000000 -0400
+++ linux-2.6/arch/x86/kernel/cpu/addon_cpuid_features.c	2008-05-22 12:59:36.000000000 -0400
@@ -62,6 +62,9 @@ void __cpuinit validate_pat_support(stru
 		if (c->x86 == 0xF || (c->x86 == 6 && c->x86_model >= 15))
 			return;
 		break;
+	case X86_VENDOR_CENTAUR:
+	case X86_VENDOR_TRANSMETA:
+		return;
 	}
 
 	pat_disable(cpu_has_pat ?

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2008-05-22 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20  4:09 [X86] Add recent Centaur CPUs to PAT whitelist Dave Jones
2008-05-20  5:49 ` Yinghai Lu
2008-05-20 13:19   ` Dave Jones
2008-05-21 23:56     ` H. Peter Anvin
2008-05-22 14:07       ` Dave Jones
2008-05-22 16:48         ` H. Peter Anvin
2008-05-22 17:02           ` Dave Jones [this message]
2008-05-22 20:23             ` H. Peter Anvin

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=20080522170223.GA32314@redhat.com \
    --to=davej@redhat.com \
    --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