From: Alan Cox <alan@linux.intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Rich Felker <dalias@libc.org>
Cc: 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: Mon, 16 Jul 2018 19:55:03 +0100 [thread overview]
Message-ID: <1531767303.4364.109.camel@linux.intel.com> (raw)
In-Reply-To: <193fb2f5-8f6c-8fe6-298f-a6af4fae862a@linux.intel.com>
On Mon, 2018-07-16 at 10:28 -0700, Dave Hansen wrote:
> On 07/16/2018 09:56 AM, Thomas Gleixner wrote:
> > On Mon, 16 Jul 2018, Rich Felker wrote:
> > > At least the Centerton (late-generation Bonnell uarch) Atom
> > > family is
> > > omitted from the cpu_no_speculation table added by commit
> > > fec9434a12f3
> > > to arch/x86/kernel/cpu/common.c. Is this intentional? Would a
> > > patch
> > > adding it and possibly other omissions be welcome?
> >
> > Probably. Dave?
>
> IIRC, Alan Cox was compiling a list on what is affected vs. not. He
> would know way better than I.
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.
Alan
next prev parent reply other threads:[~2018-07-16 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 16:05 cpu_no_speculation omissions? Rich Felker
2018-07-16 16:56 ` Thomas Gleixner
2018-07-16 17:28 ` Dave Hansen
2018-07-16 18:55 ` Alan Cox [this message]
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
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=1531767303.4364.109.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=dalias@libc.org \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw@amazon.co.uk \
--cc=hpa@zytor.com \
--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 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.