All of lore.kernel.org
 help / color / mirror / Atom feed
From: Terence Ripperda <tripperda@nvidia.com>
From: <tripperda@nvidia.com>
To: mikpe@csd.uu.se
Cc: Terence Ripperda <tripperda@nvidia.com>, linux-kernel@vger.kernel.org
Subject: Re: pat support in the kernel
Date: Tue, 20 May 2003 15:31:32 -0500	[thread overview]
Message-ID: <20030520203132.GF1050@hygelac> (raw)
In-Reply-To: <16074.33371.411219.528228@gargle.gargle.HOWL>

Thanks Mikael,

I was unaware of the errata, I'll check into that.

Terence

On Tue, May 20, 2003 at 09:30:35PM +0200, mikpe@csd.uu.se wrote:
> Terence Ripperda <tripperda@nvidia.com>, <tripperda@nvidia.com> writes:
>  > Hello all,
>  > 
>  > I've discussed adding Page Attribute Table (PAT) support to the kernel w/ a few developers offline. They were very supportive and suggested I bring the discussion to lkml so others could get involved.
> 
> Not that I disagre with utilising the PAT, but I don't see anything in this code to
> deal with the widespread PAT indexing erratum in Intel's processors. I don't have
> the errata sheets here, but it definitely affected the PIIIs and I think also some P4s.
> (Large pages ignoring PAT index bit 2, or something like that.)
> 
> /Mikael

  reply	other threads:[~2003-05-20 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 18:54 pat support in the kernel Terence Ripperda, tripperda
2003-05-20 19:30 ` mikpe
2003-05-20 20:31   ` Terence Ripperda, tripperda [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
     [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   ` Andi Kleen
2003-05-21 10:12     ` mikpe
2003-05-21 10:23       ` Andi Kleen

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=20030520203132.GF1050@hygelac \
    --to=tripperda@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.