linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Alok Kataria <akataria@vmware.com>
Cc: "hpa@zytor.com" <hpa@zytor.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Dunn <ddunn@vmware.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"jongman.heo@samsung.com" <jongman.heo@samsung.com>
Subject: Re: [PATCH] x86: don't rely on VMWare emulating PAT MSR correctly
Date: Wed, 07 Jan 2015 05:58:26 +0100	[thread overview]
Message-ID: <54ACBCF2.3010807@suse.com> (raw)
In-Reply-To: <1418792295.4473.70.camel@akataria-dtop.eng.vmware.com>

x86 maintainers, could you please consider taking my patch?

There have been several reports now regarding this issue, all could be
fixed using my patch.

Juergen

On 12/17/2014 05:57 AM, Alok Kataria wrote:
> Hi,
>
> On Tue, 2014-12-16 at 10:58 +0100, Juergen Gross wrote:
>> VMWare seems not to emulate the PAT MSR correctly: reaeding
>> MSR_IA32_CR_PAT returns 0 even after writing another value to it.
>>
>> Detect this bug and don't use the read value if it is 0.
>>
>> Commit bd809af16e3ab1f8d55b3e2928c47c67e2a865d2 ("x86: Enable PAT to
>> use cache mode translation tables") triggers this VMWare bug when the
>> kernel is booted as a VMWare guest.
>
> Thanks for taking care of this, we are fine with this workaround. On
> newer version of our product, where PAT is virtualized correctly on our
> platform we will go back to using PAT, I will give it a spin sometime
> later to verify it.
>
> Acked-by: Alok N Kataria <akataria@vmware.com>
>
>> Reported-by: Jongman Heo <jongman.heo@samsung.com>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> Tested-by: Jongman Heo <jongman.heo@samsung.com>
>> ---
>>   arch/x86/mm/pat.c | 7 ++++++-
>>   1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/mm/pat.c b/arch/x86/mm/pat.c
>> index edf299c..7ac6869 100644
>> --- a/arch/x86/mm/pat.c
>> +++ b/arch/x86/mm/pat.c
>> @@ -234,8 +234,13 @@ void pat_init(void)
>>   	      PAT(4, WB) | PAT(5, WC) | PAT(6, UC_MINUS) | PAT(7, UC);
>>
>>   	/* Boot CPU check */
>> -	if (!boot_pat_state)
>> +	if (!boot_pat_state) {
>>   		rdmsrl(MSR_IA32_CR_PAT, boot_pat_state);
>> +		if (!boot_pat_state) {
>> +			pat_disable("PAT read returns always zero, disabled.");
>> +			return;
>> +		}
>> +	}
>>
>>   	wrmsrl(MSR_IA32_CR_PAT, pat);
>>
>
> Alok
> N�����r��y���b�X��ǧv�^�)޺{.n�+����{����zX��\x17��ܨ}���Ơz�&j:+v���\a����zZ+��+zf���h���~����i���z�\x1e�w���?����&�)ߢ^[f��^jǫy�m��@A�a��\x7f�\f0��h�\x0f�i\x7f
>


      reply	other threads:[~2015-01-07  4:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16  9:58 [PATCH] x86: don't rely on VMWare emulating PAT MSR correctly Juergen Gross
2014-12-16 16:47 ` H. Peter Anvin
2014-12-17  4:52   ` Juergen Gross
2014-12-17  4:57 ` Alok Kataria
2015-01-07  4:58   ` Juergen Gross [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=54ACBCF2.3010807@suse.com \
    --to=jgross@suse.com \
    --cc=akataria@vmware.com \
    --cc=ddunn@vmware.com \
    --cc=hpa@zytor.com \
    --cc=jongman.heo@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).