[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440803251701s125ce73dp3c5c03aa4a9e89ef@mail.gmail.com>
Date: Tue, 25 Mar 2008 17:01:12 -0700
From: "Yinghai Lu" <yhlu.kernel@...il.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
Cc: "H. Peter Anvin" <hpa@...or.com>, "Ingo Molnar" <mingo@...e.hu>,
"Thomas Gleixner" <tglx@...utronix.de>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"kernel list" <linux-kernel@...r.kernel.org>,
"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
"Barnes, Jesse" <jesse.barnes@...el.com>
Subject: Re: [PATCH] x86: pat cpu feature bit setting for known cpus
On Tue, Mar 25, 2008 at 4:38 PM, Pallipadi, Venkatesh
<venkatesh.pallipadi@...el.com> wrote:
>
>
>
> >-----Original Message-----
> >From: Yinghai Lu [mailto:yhlu.kernel@...il.com]
> >Sent: Tuesday, March 25, 2008 4:09 PM
> >To: H. Peter Anvin
> >Cc: Ingo Molnar; Pallipadi, Venkatesh; Thomas Gleixner; Andrew
> >Morton; kernel list; Siddha, Suresh B
> >Subject: Re: [PATCH] x86: pat cpu feature bit setting for known cpus
> >
> >On Tue, Mar 25, 2008 at 4:06 PM, H. Peter Anvin <hpa@...or.com> wrote:
> >> Yinghai Lu wrote:
> >> >>
> >> >> By the way, I want to clarify: I didn't mean it was
> >*intended* as
> >> >> vendor-lockin, just that it's an undesirable effect of this.
> >> >
> >> > if the PAT works, we may need to trim the memory
> >according to MTRR, right?
> >> >
> >>
> >> That doesn't seem like it's specific to PAT?
> >
> >could page table to set WRBACK the range that is not covered
> >by MTRR in e820..
> >
>
> Trimming of e820 memory is already done by Jesse's patch here
> commit 99fc8d424bc5d80
> Are you referring to similar thing?
>
Yes.
YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists