[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01f705f1-484b-4407-7b7a-e8e69966581f@amd.com>
Date: Mon, 14 Nov 2016 10:51:27 -0600
From: Tom Lendacky <thomas.lendacky@....com>
To: "Kani, Toshimitsu" <toshi.kani@....com>,
"bp@...en8.de" <bp@...en8.de>
CC: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dvyukov@...gle.com" <dvyukov@...gle.com>,
"corbet@....net" <corbet@....net>, "arnd@...db.de" <arnd@...db.de>,
"matt@...eblueprint.co.uk" <matt@...eblueprint.co.uk>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"aryabinin@...tuozzo.com" <aryabinin@...tuozzo.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"konrad.wilk@...cle.com" <konrad.wilk@...cle.com>,
"kasan-dev@...glegroups.com" <kasan-dev@...glegroups.com>,
"x86@...nel.org" <x86@...nel.org>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"riel@...hat.com" <riel@...hat.com>,
"lwoodman@...hat.com" <lwoodman@...hat.com>,
"mingo@...hat.com" <mingo@...hat.com>,
"joro@...tes.org" <joro@...tes.org>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"hpa@...or.com" <hpa@...or.com>,
"luto@...nel.org" <luto@...nel.org>,
"glider@...gle.com" <glider@...gle.com>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"rkrcmar@...hat.com" <rkrcmar@...hat.com>
Subject: Re: [RFC PATCH v3 02/20] x86: Set the write-protect cache mode for
full PAT support
On 11/10/2016 07:26 PM, Kani, Toshimitsu wrote:
> On Thu, 2016-11-10 at 14:14 +0100, Borislav Petkov wrote:
>> + Toshi.
>>
>> On Wed, Nov 09, 2016 at 06:34:48PM -0600, Tom Lendacky wrote:
>>>
>>> For processors that support PAT, set the write-protect cache mode
>>> (_PAGE_CACHE_MODE_WP) entry to the actual write-protect value
>>> (x05).
>
> Using slot 6 may be more cautious (for the same reason slot 7 was used
> for WT), but I do not have a strong opinion for it.
>
> set_page_memtype() cannot track the use of WP type since there is no
> extra-bit available for WP, but WP is only supported by
> early_memremap_xx() interfaces in this series. So, I think we should
> just document that WP is only intended for temporary mappings at boot-
> time until this issue is resolved. Also, we need to make sure that
> this early_memremap for WP is only called after pat_init() is done.
Sounds good, I'll add documentation to cover these points.
>
> A nit - please add WP to the function header comment below.
> "This function initializes PAT MSR and PAT table with an OS-defined
> value to enable additional cache attributes, WC and WT."
Will do.
Thanks,
Tom
>
> Thanks,
> -Toshi
>
Powered by blists - more mailing lists