From: Rich Felker <dalias@libc.org>
To: Joerg Roedel <jroedel@suse.de>
Cc: Jiri Kosina <jikos@kernel.org>, Alan Cox <alan@linux.intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
David Woodhouse <dwmw@amazon.co.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: cpu_no_speculation omissions?
Date: Thu, 26 Jul 2018 11:54:05 -0400 [thread overview]
Message-ID: <20180726155405.GX1392@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180726141842.56ppkwy3d3hwr56p@suse.de>
On Thu, Jul 26, 2018 at 04:18:42PM +0200, Joerg Roedel wrote:
> On Thu, Jul 26, 2018 at 03:29:53PM +0200, Jiri Kosina wrote:
> > On Mon, 16 Jul 2018, Alan Cox wrote:
> > > The pre Silvermont atom cores are in order. When I did the original
> > > list I didn't bother with all the 32bit cores as we didn't have any
> > > 32bit mitigations then.
> >
> > Now that 32bit PTI is in tip, I believe refresh of that list would be
> > justified. CCing Joerg.
>
> Agreed, PTI for x86-32 is in -tip now and will likely make it into
> v4.19. In-order cores (which should not be not affected by Meltdown)
> should be on the list, otherwise they will get a huge performance hit.
Does anyone have a complete list of pre-speculation Atom models? Mine
is one of the few 64-bit ones, but there are lots of 32-bit Atoms that
PTI would hit hard.
Rich
prev parent reply other threads:[~2018-07-26 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 16:05 Rich Felker
2018-07-16 16:56 ` Thomas Gleixner
2018-07-16 17:28 ` Dave Hansen
2018-07-16 18:55 ` Alan Cox
2018-07-16 19:20 ` Thomas Gleixner
2018-07-16 19:54 ` Rich Felker
2018-07-16 20:38 ` Thomas Gleixner
2018-07-26 13:29 ` Jiri Kosina
2018-07-26 14:18 ` Joerg Roedel
2018-07-26 15:54 ` Rich Felker [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=20180726155405.GX1392@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=alan@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw@amazon.co.uk \
--cc=hpa@zytor.com \
--cc=jikos@kernel.org \
--cc=jroedel@suse.de \
--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
all inboxes | Powered by JetHome®