From: Ingo Molnar <mingo@elte.hu>
To: Dave Jones <davej@redhat.com>, Yinghai Lu <Yinghai.Lu@Sun.COM>,
venkatesh.pallipadi@intel.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] X86: fix typo PAT to X86_PAT
Date: Fri, 18 Jan 2008 22:02:10 +0100 [thread overview]
Message-ID: <20080118210210.GB10717@elte.hu> (raw)
In-Reply-To: <20080118182437.GA10167@redhat.com>
* Dave Jones <davej@redhat.com> wrote:
> > you mean modifies MTRRs? Which code is that? (besides the
> > /proc/mtrr userspace API)
>
> This exclusion is going to be a real pain in the ass for distro
> kernels. It's impossible for example to build a kernel that will now
> support the MTRR-alike registers on the AMD K6/early Cyrix etc and
> also support PAT.
>
> Additionally, given people tend to update their kernels a lot more
> often than they update to a whole new version of X, it means until
> userspace has caught up, we can't ship a kernel with PAT supported, or
> else X gets a lot slower due to the missing mtrr support.
there's no exclusion enforced right now, and if a CPU is PAT-incapable
(or if the kernel is booted nopat) then the MTRR bits should be usable.
But if we boot with PAT enabled, and Xorg gets /proc/mtrr wrong, we'll
see nasty crashes. If it gets them right, it should all still work just
fine. Is this ok? Then, in a year or two, distros can disable write
support to /proc/mtrr. Hm?
Ingo
next prev parent reply other threads:[~2008-01-18 21:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 3:50 Yinghai Lu
2008-01-18 8:10 ` Ingo Molnar
2008-01-18 9:03 ` Yinghai Lu
2008-01-18 12:31 ` Ingo Molnar
2008-01-18 18:24 ` Dave Jones
2008-01-18 18:47 ` Pallipadi, Venkatesh
2008-01-18 18:56 ` Dave Jones
2008-01-18 21:03 ` Ingo Molnar
2008-01-18 21:02 ` Ingo Molnar [this message]
2008-01-19 3:28 ` Dave Jones
2008-01-19 7:56 ` [PATCH] X86: disable X86_PAT really Yinghai Lu
2008-01-19 7:58 ` [PATCH] X86: fix typo PAT to X86_PAT Yinghai Lu
2008-01-22 18:26 ` Pallipadi, Venkatesh
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=20080118210210.GB10717@elte.hu \
--to=mingo@elte.hu \
--cc=Yinghai.Lu@Sun.COM \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®