From: Xiaotian Feng <dfeng@redhat.com>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: [RFC PATCH -tip] x86/pat: fix pat_x_mtrr_type to its essentials
Date: Tue, 01 Dec 2009 09:55:52 +0800 [thread overview]
Message-ID: <4B1477A8.1000206@redhat.com> (raw)
In-Reply-To: <1259623292.2651.218.camel@sbs-t61.sc.intel.com>
On 12/01/2009 07:21 AM, Suresh Siddha wrote:
> Xiaotian,
>
> We look through the mtrr's only when the incoming request type is WB
> (which is mostly the case for legacy /dev/mem mmap mapping). And only in
> this scenario we use more conservative UC- instead of WC, if mtrr says
> WC.
>
> This will ensure the scenarios like ioremap() (which defaults to UC-) by
> legacy drivers, before and after the user level mmap are consistent and
> don't fail because of inconsistent mappings etc.
>
> There is no reason why we need to use WC when especially the incoming
> request was not strict enough and specified WB.
>
> Also BTW, your current effective return values mentioned in the below
> table () is wrong.
>
> i.e., for example, when we use UC- for PAT and mtrr has WC, effective
> memory type used by cpu will be WC.
Thanks for the detailed explanation, I'm clear now, thank you very much.
>
> thanks,
> suresh
>
> On Thu, 2009-11-26 at 04:15 -0800, Xiaotian Feng wrote:
>> Due to the IA-32 SDM vol 3a "Effective Memory Type" tables, the PAT
>> and mtrr relations should be:
>> | UC UC- WC WB [PAT]
>> --------+--------------------------------------
>> UC | UC UC(UC-) WC UC(UC-)
>> WC | UC WC(UC-) WC WC(UC-)
>> WB | UC UC(UC-) WC WB
>> [MTRR]
>> * In () is the current return value.
>>
>> So, commit b6ff32, Fix pat_x_mtrr_type() to use UC_MINUS when the
>> mtrr type return UC. But it also made mtrr type WC use UC_MINUS.
>> This is not reasonable.
>>
>> Signed-off-by: Xiaotian Feng<dfeng@redhat.com>
>> Cc: Thomas Gleixner<tglx@linutronix.de>
>> Cc: Ingo Molnar<mingo@redhat.com>
>> Cc: H. Peter Anvin<hpa@zytor.com>
>> Cc: Suresh Siddha<suresh.b.siddha@intel.com>
>> Cc: Venkatesh Pallipadi<venkatesh.pallipadi@intel.com>
>> ---
>> arch/x86/mm/pat.c | 9 +++++----
>> 1 files changed, 5 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/x86/mm/pat.c b/arch/x86/mm/pat.c
>> index c37fd51..92e9627 100644
>> --- a/arch/x86/mm/pat.c
>> +++ b/arch/x86/mm/pat.c
>> @@ -228,10 +228,11 @@ static unsigned long pat_x_mtrr_type(u64 start, u64 end, unsigned long req_type)
>> u8 mtrr_type;
>>
>> mtrr_type = mtrr_type_lookup(start, end);
>> - if (mtrr_type != MTRR_TYPE_WRBACK)
>> - return _PAGE_CACHE_UC_MINUS;
>> -
>> - return _PAGE_CACHE_WB;
>> + if (mtrr_type == MTRR_TYPE_WRBACK)
>> + return _PAGE_CACHE_WB;
>> + else if (mtrr_type == MTRR_TYPE_WRCOMB)
>> + return _PAGE_CACHE_WC;
>> + return _PAGE_CACHE_UC_MINUS;
>> }
>>
>> return req_type;
>
>
prev parent reply other threads:[~2009-12-01 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 12:15 [RFC PATCH -tip] x86/pat: fix pat_x_mtrr_type to its essentials Xiaotian Feng
2009-11-30 23:21 ` Suresh Siddha
2009-12-01 1:55 ` Xiaotian Feng [this message]
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=4B1477A8.1000206@redhat.com \
--to=dfeng@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
--cc=x86@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