From: Terence Ripperda <tripperda@nvidia.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Terence Ripperda <tripperda@nvidia.com>,
Dave Airlie <airlied@gmail.com>
Subject: Re: PAT status?
Date: Thu, 1 Dec 2005 14:49:22 -0600 [thread overview]
Message-ID: <20051201204922.GT4365@hygelac> (raw)
In-Reply-To: <438CD4AD.9070806@pobox.com>
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.
the second part was to make sure we didn't create any cache aliasing
via duplicate mappings. this part is a bit more involved and what was
holding everything back. I've been meaning to get back to looking at
this, but really haven't had the time.
I don't know if you still want to limit the additional of the first
step, based on completion of the second step. I can try to set time
aside over the next month to try and sync up and take a look at where
we stand w/ the cachemap portion of the code. I think there where
still issues with gathering/passing in the correct attributes.
Thanks,
Terence
On Tue, Nov 29, 2005 at 05:22:37PM -0500, jgarzik@pobox.com wrote:
>
> What's the status of PAT support?
>
> I'm interested in that sort of stuff, for use with on-board GPUs such as
> Intel/VIA/SiS, where system memory is used rather than offboard ram.
>
> Jeff
>
>
>
next prev parent reply other threads:[~2005-12-01 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 22:22 PAT status? Jeff Garzik
2005-12-01 20:49 ` Terence Ripperda [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-12-08 15:37 Daniel J Blueman
2005-12-09 18:45 ` Dave Jones
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=20051201204922.GT4365@hygelac \
--to=tripperda@nvidia.com \
--cc=airlied@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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