public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: arjan@linux.intel.com, tglx@linutronix.de, karahmed@amazon.de,
	x86@kernel.org,  linux-kernel@vger.kernel.org,
	tim.c.chen@linux.intel.com, bp@alien8.de,  peterz@infradead.org,
	pbonzini@redhat.com, torvalds@linux-foundation.org,
	 gregkh@linux-foundation.org, thomas.lendacky@amd.com
Subject: Re: [PATCH v2 5/5] x86/pti: Do not enable PTI on fixed Intel processors
Date: Wed, 24 Jan 2018 01:21:51 +0000	[thread overview]
Message-ID: <1516756911.13558.60.camel@infradead.org> (raw)
In-Reply-To: <20180123181201.GO7844@tassilo.jf.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]

On Tue, 2018-01-23 at 10:12 -0800, Andi Kleen wrote:
> > -     if (c->x86_vendor != X86_VENDOR_AMD)
> > -             setup_force_cpu_bug(X86_BUG_CPU_MELTDOWN);
> > +     if (c->x86_vendor != X86_VENDOR_AMD) {
> > +             u64 ia32_cap = 0;
> > +
> > +             if (cpu_has(c, X86_FEATURE_ARCH_CAPABILITIES))
> > +                     rdmsrl(MSR_IA32_ARCH_CAPABILITIES, ia32_cap);
> > +             if (!(ia32_cap & ARCH_CAP_RDCL_NO))
> > +                     setup_force_cpu_bug(X86_BUG_CPU_MELTDOWN);
> 
> This means that in a hypervisor which passes through the CPUID,
> but actually doesn't implement the MSR (so rdmsr #GPs and returns 0)
> it would be cleared. 
> 
> It would be better to usr rdmsrl_safe and check the return value.

This particular CPUID bit exists *purely* to advertise that the
IA32_ARCH_CAPABILITIES MSR exists. Nothing else. A hypervisor which
tells us the MSR exists and then doesn't expose it is fairly broken.
Not that it won't happen, of course.

But reading zero is fine. If the bit isn't set we do set the MELTDOWN
bug flag.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5213 bytes --]

  reply	other threads:[~2018-01-24  1:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 16:52 [PATCH v2 0/5] Basic Speculation Control feature support David Woodhouse
2018-01-23 16:52 ` [PATCH v2 1/5] x86/cpufeatures: Add CPUID_7_EDX CPUID leaf David Woodhouse
2018-01-23 16:52 ` [PATCH v2 2/5] x86/cpufeatures: Add Intel feature bits for Speculation Control David Woodhouse
2018-01-23 18:43   ` Dave Hansen
2018-01-24  1:23     ` Woodhouse, David
2018-01-24  1:28       ` Dave Hansen
2018-01-24  8:13         ` Woodhouse, David
2018-01-23 16:52 ` [PATCH v2 3/5] x86/cpufeatures: Add AMD " David Woodhouse
2018-01-24  8:39   ` Kirill A. Shutemov
2018-01-24  8:40     ` David Woodhouse
2018-01-23 16:52 ` [PATCH v2 4/5] x86/msr: Add definitions for new speculation control MSRs David Woodhouse
2018-01-23 18:27   ` Dave Hansen
2018-01-23 18:31     ` Greg KH
2018-01-23 18:48       ` Woodhouse, David
2018-01-23 16:52 ` [PATCH v2 5/5] x86/pti: Do not enable PTI on fixed Intel processors David Woodhouse
2018-01-23 18:12   ` Andi Kleen
2018-01-24  1:21     ` David Woodhouse [this message]
2018-01-23 18:40   ` Dave Hansen
2018-01-24  1:27     ` David Woodhouse
2018-01-23 18:41   ` Dave Hansen
2018-01-23 18:44     ` Woodhouse, David
2018-01-23 18:45   ` Alan Cox
2018-01-23 19:02     ` Andrew Cooper
2018-01-23 20:45       ` Alan Cox
2018-01-23 20:38     ` Linus Torvalds
2018-01-23 20:50     ` David Woodhouse
2018-01-24 16:25     ` David Woodhouse
2018-01-24 17:07       ` Alan Cox
2018-01-24 17:42         ` David Woodhouse
2018-01-24 18:40           ` Alan Cox
2018-01-24 18:59             ` David Woodhouse
2018-01-24 19:37             ` David Woodhouse

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=1516756911.13558.60.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=ak@linux.intel.com \
    --cc=arjan@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=gregkh@linux-foundation.org \
    --cc=karahmed@amazon.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=tim.c.chen@linux.intel.com \
    --cc=torvalds@linux-foundation.org \
    --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