public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
	tglx@linutronix.de, mingo@redhat.com,
	venkatesh.pallipadi@intel.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.26-rc1 lies about PAT not being available
Date: Tue, 06 May 2008 08:17:17 -0700	[thread overview]
Message-ID: <4820767D.8040202@zytor.com> (raw)
In-Reply-To: <20080506114839.GD32591@elte.hu>

Ingo Molnar wrote:
>> I know about Intel's PAT erratum (only 4 PAT entries work) and 
>> understand that the kernel might not want to use a half-broken PAT 
>> implementation, but the statement above is blatantly false: the kernel 
>> IS built with PAT support and the CPU DOES have (half-broken) PAT HW 
>> support as /proc/cpuinfo from earlier kernels confirms.
> 
> well the code is just being overly conservative, and the message is 
> right: the kernel does not support PAT on that hw. Yet.
> 
> Please send us a patch and test whether it's working on your box? That's 
> how the PAT code evolved: it initially was only enabled on a very small 
> subset of CPUs. We can enable it on more CPUs if people test it.
> 
> To be conservative, please make the code emit a printk that this is PAT 
> on not fully-working hw platform (only 4 PAT entries work). If there 
> _is_ some erratum on that CPU affecting PAT reliability down the line, 
> we at least want to have some clue in the syslog.
> 

For what it's worth, we only use four PAT entries, so it doesn't matter 
that only four work.

	-hpa


      reply	other threads:[~2008-05-06 15:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06  8:18 2.6.26-rc1 lies about PAT not being available Mikael Pettersson
2008-05-06 11:48 ` Ingo Molnar
2008-05-06 15:17   ` H. Peter Anvin [this message]

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=4820767D.8040202@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.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