From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Ondrej Zary <linux@rainbow-software.org>,
whiteheadm@acm.org, David Woodhouse <dwmw2@infradead.org>,
Guenter Roeck <linux@roeck-us.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hugh Dickins <hughd@google.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Jiri Kosina <jikos@kernel.org>, Borislav Petkov <bp@alien8.de>,
Kees Cook <keescook@chromium.org>,
Jamie Iles <jamie@jamieiles.com>,
Eduardo Valentin <eduval@amazon.com>,
Laura Abbott <labbott@redhat.com>,
Rik van Riel <riel@surriel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2
Date: Thu, 8 Feb 2018 21:16:36 +0000 [thread overview]
Message-ID: <20180208211636.28d82edd@alans-desktop> (raw)
In-Reply-To: <CAK8P3a2kuHXpJOVKux2v-B_=CrpnQBTMfV24sJqY+nQaSMf+KA@mail.gmail.com>
On Thu, 8 Feb 2018 16:22:40 +0100
Arnd Bergmann <arnd@arndb.de> wrote:
> On Thu, Feb 8, 2018 at 2:49 PM, Alan Cox <gnomes@lxorguk.ukuu.org.uk> wrote:
> >> What about Pentium II and 3? I'm using 5 such machines (and also a Pentium
> >> MMX). I've tried a spectre test before and it wasn't reading anything useful.
> >> Don't know about meltdown. Is there a complete test program? (The web is so
> >> full of crap that even google can't find anything useful.)
> >
> > For x86 speculation came in (as far as I can tell) in
> >
> > AMD Am5x86
> > Cyrix 5x86, but branch predictors are disabled by default according to
> > the docs
> > Cyrix 6x86, branch prediction on by default
> > Pentium Pro
> >
> > There are later processors that don't have speculation: Quark series, Nat
> > Semi/Cyrix Geode, earliest AMD geode (I think), some Intel Atom
> > processors.
>
> Wasn't Am5x86 just a 486 clone? AFAICT, speculation only came with the
> K6 (Am6x86 aka NexGen Nx6x86)
The AMD 486 was a 486, just like UMC. The Am5x86 was a sort of super 486.
But you are correct I'm muddling that with the K5 - which does speculate
or at least some of them do. The K5 branch predictor is software
controllable via the HWCR MSR but who has one today to test or cares 8)
> All the Geode are apparently derived from Cyrix 5x86 (I always thought
Not quite all. The older ones are Cyrix 5x86 related which indeed means
they don't have branch prediction on by default until the LX. Just to
confuse the AMD Geode NX is basically an Athlon mobile.
Alan
next prev parent reply other threads:[~2018-02-08 21:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 4:52 [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2 tedheadster
2018-02-03 7:37 ` David Woodhouse
2018-02-06 18:33 ` tedheadster
2018-02-06 19:02 ` Greg Kroah-Hartman
2018-02-06 19:10 ` David Woodhouse
2018-02-06 19:13 ` Guenter Roeck
2018-02-06 19:17 ` David Woodhouse
2018-02-06 19:24 ` tedheadster
2018-02-06 20:45 ` tedheadster
2018-02-06 20:54 ` David Woodhouse
2018-02-06 22:11 ` tedheadster
2018-02-07 8:18 ` Ondrej Zary
2018-02-08 13:49 ` Alan Cox
2018-02-08 15:22 ` Arnd Bergmann
2018-02-08 17:02 ` David Laight
2018-02-08 17:27 ` tedheadster
2018-02-08 21:50 ` Arnd Bergmann
2018-02-09 8:41 ` Ondrej Zary
2018-02-13 21:04 ` Pavel Machek
2018-02-15 9:53 ` What was last kernel that booted on hardware XY? database was Re: [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2A Pavel Machek
2018-02-15 13:16 ` tedheadster
2018-02-17 21:16 ` Pavel Machek
2018-02-17 22:39 ` tedheadster
2018-02-23 8:07 ` Pavel Machek
2018-02-08 17:50 ` [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2 tedheadster
2018-02-08 20:52 ` Alan Cox
2018-02-13 21:04 ` Pavel Machek
2018-02-13 23:45 ` Alan Cox
2018-02-08 21:16 ` Alan Cox [this message]
2018-02-08 21:57 ` Arnd Bergmann
2018-02-06 21:59 ` Alan Cox
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=20180208211636.28d82edd@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=eduval@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=jamie@jamieiles.com \
--cc=jikos@kernel.org \
--cc=keescook@chromium.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=linux@roeck-us.net \
--cc=riel@surriel.com \
--cc=tglx@linutronix.de \
--cc=whiteheadm@acm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.