From: Pavel Machek <pavel@ucw.cz>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: tedheadster <tedheadster@gmail.com>,
whiteheadm@acm.org, David Laight <David.Laight@aculab.com>,
Arnd Bergmann <arnd@arndb.de>,
Ondrej Zary <linux@rainbow-software.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: Tue, 13 Feb 2018 22:04:48 +0100 [thread overview]
Message-ID: <20180213210448.GB6569@amd> (raw)
In-Reply-To: <20180208205240.0c53631f@alans-desktop>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On Thu 2018-02-08 20:52:40, Alan Cox wrote:
> > > Also worth nothing that the difference between the cpu and memory
> > > speeds is much lower - so far fewer instructions could be speculatively
> > > executed while waiting a cache miss.
>
> But they also have more instructions that take a lot of clocks and are
> easier to stall - eg by doing things like opening and mmapping
> a framebuffer and then doing a floating point double store to it
> misaligned.
>
> Meltdown we can at least reasonably test but spectre is hard.
Do you have pointer for simple meltdown test?
I've got https://github.com/IAIK/meltdown.git but could not get it to
work even on machines that should be vulnerable.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-02-13 21:04 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 [this message]
2018-02-13 23:45 ` Alan Cox
2018-02-08 21:16 ` Alan Cox
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=20180213210448.GB6569@amd \
--to=pavel@ucw.cz \
--cc=David.Laight@aculab.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=eduval@amazon.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--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=tedheadster@gmail.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 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).