From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"kernel list" <linux-kernel@vger.kernel.org>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"Barnes, Jesse" <jesse.barnes@intel.com>
Subject: Re: [PATCH] x86: pat cpu feature bit setting for known cpus
Date: Tue, 25 Mar 2008 17:01:12 -0700 [thread overview]
Message-ID: <86802c440803251701s125ce73dp3c5c03aa4a9e89ef@mail.gmail.com> (raw)
In-Reply-To: <924EFEDD5F540B4284297C4DC59F3DEEC3E1EB@orsmsx423.amr.corp.intel.com>
On Tue, Mar 25, 2008 at 4:38 PM, Pallipadi, Venkatesh
<venkatesh.pallipadi@intel.com> wrote:
>
>
>
> >-----Original Message-----
> >From: Yinghai Lu [mailto:yhlu.kernel@gmail.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@zytor.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
next prev parent reply other threads:[~2008-03-26 0:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 6:24 Yinghai Lu
2008-03-25 10:58 ` Ingo Molnar
2008-03-25 13:38 ` H. Peter Anvin
2008-03-25 18:03 ` Yinghai Lu
2008-03-25 19:08 ` Venki Pallipadi
2008-03-25 20:08 ` Ingo Molnar
2008-03-25 20:38 ` H. Peter Anvin
2008-03-25 23:01 ` H. Peter Anvin
2008-03-25 23:05 ` Yinghai Lu
2008-03-25 23:06 ` H. Peter Anvin
2008-03-25 23:08 ` Yinghai Lu
2008-03-25 23:38 ` Pallipadi, Venkatesh
2008-03-26 0:01 ` Yinghai Lu [this message]
2008-03-26 0:10 ` H. Peter Anvin
2008-03-28 13:41 ` Pavel Machek
2008-03-28 14:51 ` Yinghai Lu
2008-03-30 11:43 ` dean gaudet
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=86802c440803251701s125ce73dp3c5c03aa4a9e89ef@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jesse.barnes@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.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
all inboxes | Powered by JetHome®