From: Dave Jones <davej@redhat.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: tripperda@nvidia.com, Linux Kernel <linux-kernel@vger.kernel.org>,
ak@suse.de, jgarzik@pobox.com
Subject: Re: PAT status?
Date: Fri, 9 Dec 2005 13:45:17 -0500 [thread overview]
Message-ID: <20051209184517.GB7473@redhat.com> (raw)
In-Reply-To: <6278d2220512080737t30a83011k11e88e85c0974a11@mail.gmail.com>
On Thu, Dec 08, 2005 at 03:37:43PM +0000, Daniel J Blueman wrote:
> Terence Ripperda wrote:
> > Hi Jeff,
> >
> > I unfortunately haven't had much time to look at the status of the PAT
> > code I had been working on. there are really 2 steps to the code:
> >
> > the first is enabling and configuring the PAT registers. this then
> > allows a page table entry define that can be passed to traditional
> > interfaces, such as remap_page_range or change_page_attr. this is
> > pretty simple and we've been using a similar interface in our driver
> > for some time now.
>
> Presumably, the aliasing will only bite where eg the X server sets up
> MTRRs and PAT is used for the region also. For x86_64 and IA32, the
> Intel IA32 system guides tell us that strong store ordering (ie
> write-through) takes precendence over weaker store ordering (eg
> write-combining), so we should be safe. For processors with known
> errata with PAT etc, we can disable PAT support.
>
> Would it be useful to get a rough patch covering point #1 onto LKML
> for discussion?
http://lwn.net/Articles/135883/ is Terrence's last patch
rediffed against 2.6.12 patch.
Dave
next prev parent reply other threads:[~2005-12-09 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 15:37 PAT status? Daniel J Blueman
2005-12-09 18:45 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-30 12:04 Daniel J Blueman
2005-11-30 21:58 ` Andi Kleen
2005-12-01 14:30 ` Daniel J Blueman
2005-11-29 22:22 Jeff Garzik
2005-12-01 20:49 ` Terence Ripperda
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=20051209184517.GB7473@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=daniel.blueman@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tripperda@nvidia.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