From: Andi Kleen <ak@suse.de>
To: mikpe@csd.uu.se
Cc: tripperda@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: pat support in the kernel
Date: Wed, 21 May 2003 12:23:40 +0200 [thread overview]
Message-ID: <20030521122340.74f6502b.ak@suse.de> (raw)
In-Reply-To: <16075.20763.659219.636543@gargle.gargle.HOWL>
On Wed, 21 May 2003 12:12:43 +0200
mikpe@csd.uu.se wrote:
> Andi Kleen writes:
> > mikpe@csd.uu.se writes:
> >
> > > (Large pages ignoring PAT index bit 2, or something like that.)
> >
> > change_page_attr will force 4K pages for these anyways, so for the kernel
> > direct mapping it should not be an issue.
> >
> > For the hugetlbfs user mapping you may need to check the case, but
> > it's probably reasonable to EINVAL there.
> >
> > Other than that everything should be 4K mapped.
>
> The bug is that 4K pages get the wrong PAT index; the large page
> thing is the trigger but the large pages themselves arent' affected.
>
> So 4K pages need to be restricted to the low 4 PAT types.
Should be no issue. cache disabled and write combining seem to be the
only really useful caching types anyways. You don't even need to mess
with the PAT registers for them, the default 486/586 compatible WC and CD PTE
bits should work.
-Andi
next prev parent reply other threads:[~2003-05-21 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030520185409.GB941@hygelac.suse.lists.linux.kernel>
[not found] ` <16074.33371.411219.528228@gargle.gargle.HOWL.suse.lists.linux.kernel>
2003-05-21 9:41 ` pat support in the kernel Andi Kleen
2003-05-21 10:12 ` mikpe
2003-05-21 10:23 ` Andi Kleen [this message]
[not found] <20030520190017$773c@gated-at.bofh.it>
2003-05-20 19:10 ` Andi Kleen
2003-05-20 20:18 ` Terence Ripperda, tripperda
2003-05-21 9:33 ` Andi Kleen
2003-05-22 18:23 ` Terence Ripperda, tripperda
2003-05-20 18:54 Terence Ripperda, tripperda
2003-05-20 19:30 ` mikpe
2003-05-20 20:31 ` Terence Ripperda, tripperda
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=20030521122340.74f6502b.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--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