mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/5] x86/pti: Do not enable PTI on fixed Intel processors
Date: Wed, 24 Jan 2018 18:40:35 +0000	[thread overview]
Message-ID: <20180124183958.267e405b@alans-desktop> (raw)
In-Reply-To: <1516815723.13558.164.camel@infradead.org>

> > AND K5 speculates, Cyrix 6x86 speculates, IDT WinChip does not. I think
> > this should be
> > 
> > X86_VENDOR_ANY, 4
> > X86_VENDOR_INTEL, 5,
> > X86_VENDOR_CENTAUR, 5,  
> 
> Hm, for the specific case of controlling X86_BUG_CPU_MELTDOWN it's not
> just "speculates" which is the criterion. It's "optimises away the
> permissions checks while speculating, on the assumption that it'll be
> fixed up before retiring the instruction".

Nobody has published official statements on Cyrix or AMD 32bit processors
so we don't know if they are vulnerable to meltdown. One problem I
suspect is that as with things like Alpha 21264 - the people who knew are
probably long retired. We do know the Intel ones I listed are OK and the
Centaur.

If someone can figure out the Cyrix and AMD cases that would be great.

> By the time the dust settles we might end up with a bunch of different
> match tables, *one* of which is "does not speculate at all". And the
> conditions for the different bugs will each use different sets of match
> tables. For example
> 
>  if (!x86_match_cpu(cpu_no_speculation_at_all) &&
>      !x86_match_cpu(speculation_but_no_meltdown) &&
>      !cpu_sets_rdcl_no())
> 	setup_force_cpu_bug(X86_BUG_CPU_MELTDOWN);
> 
>  if (!x86_match_cpu(cpu_no_speculation_at_all) &&
>      !x86_match_cpu(no_branch_target_buffer))
> 	setup_force_cpu_bug(X86_BUG_SPECTRE_V2);

There are afaik no x86 processors that speculate and don't have a BTB.
It's a bit like building a racing car with no gearbox.

Alan

  reply	other threads:[~2018-01-24 18:40 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
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 [this message]
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=20180124183958.267e405b@alans-desktop \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=dave.hansen@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.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

Powered by JetHome