public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Roland Dreier <rdreier@cisco.com>,
	linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@linuxtronix.de,
	hpa@zytor.com
Subject: Re: [PATCH] x86: Relegate CONFIG_PAT to EMBEDDED
Date: Sun, 11 Oct 2009 15:47:45 -0300	[thread overview]
Message-ID: <20091011184745.GA18578@khazad-dum.debian.net> (raw)
In-Reply-To: <20091011103302.62bded41@infradead.org>

On Sun, 11 Oct 2009, Arjan van de Ven wrote:
> MTRR and PAT support (which got added to CPUs over 10 years ago) are no
> longer really optional in that more and more things are depending on PAT
> just working, including various drivers and newer versions of X.  (to not
> even speak of MTRR)

Please take a look at early_init_intel() in arch/x86/kernel/cpu/intel.c.
it disables PAT for what must amount to more than a *million* of
machines.  It certainly includes all Centrino laptops, for example(!).

FYI, these computers will be with us for at least 10 years, still.  I
still have users of Mobile Pentium II reporting bugs on thinkpad-acpi,
and I know of a *huge* number of active Pentium II and Pentium III
desktops in Brazil.  My 5-year-old ThinkPad T43 (Centrino, Pentium M)
cheerfully reports "PAT not supported by CPU" at boot if I decide to
waste memory by enabling CONFIG_X86_PAT.

So, unless that blacklist can be drastically reduced somehow, can we
*please* fix anything that depends on PAT "just working"?  Because as
far as the kernel is concerned right now, way too many machines can't
even dream of using PAT.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2009-10-11 18:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-11 15:43 [PATCH] x86: Relegate CONFIG_PAT to EMBEDDED Arjan van de Ven
2009-10-11 17:04 ` Roland Dreier
2009-10-11 17:19   ` Robert Hancock
2009-10-11 17:33   ` Arjan van de Ven
2009-10-11 18:47     ` Henrique de Moraes Holschuh [this message]
2009-10-12 11:10     ` [tip:x86/pat] x86: Relegate CONFIG_PAT and CONFIG_MTRR configurability " tip-bot for Arjan van de Ven
2009-10-12 17:28       ` H. Peter Anvin
2009-10-12 17:45         ` Arjan van de Ven
2009-10-12 17:56           ` Ingo Molnar

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=20091011184745.GA18578@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=arjan@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdreier@cisco.com \
    --cc=tglx@linuxtronix.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