All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Van De Ven, Arjan" <arjan.van.de.ven@intel.com>
To: David Woodhouse <dwmw2@infradead.org>,
	Alexander Sergeyev <sergeev917@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>, Kyle Huey <me@kylehuey.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Levin, Alexander (Sasha Levin)" <alexander.levin@verizon.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: update spectre v2 microcodes blacklist
Date: Mon, 12 Feb 2018 13:56:15 +0000	[thread overview]
Message-ID: <0575AF4FD06DD142AD198903C74E1CC87A61260B@ORSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <1518428086.6606.11.camel@infradead.org>

> > Raw diff between the mainline blacklist and the bulletin looks like:
> > @@ -1,5 +1,6 @@
> >  { INTEL_FAM6_BROADWELL_CORE,     0x04, 0x28 },
> >  { INTEL_FAM6_BROADWELL_GT3E,     0x01, 0x1b },
> > +{ INTEL_FAM6_BROADWELL_X,        0x01, 0x0b000023 },
> >  { INTEL_FAM6_BROADWELL_X,        0x01, 0x0b000025 },
> 
> That's redundant since blacklisting 0x0b000025 will also stop us from
> using 0x0b000023 anyway.

and 23 is the pre security version so known good.




  reply	other threads:[~2018-02-12 13:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-10 12:31 update spectre v2 microcodes blacklist Alexander Sergeyev
2018-02-10 17:14 ` Alexander Sergeyev
2018-02-12  9:34   ` David Woodhouse
2018-02-12 13:56     ` Van De Ven, Arjan [this message]
2018-02-12 14:11       ` Alexander Sergeyev

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=0575AF4FD06DD142AD198903C74E1CC87A61260B@ORSMSX103.amr.corp.intel.com \
    --to=arjan.van.de.ven@intel.com \
    --cc=alexander.levin@verizon.com \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@kylehuey.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sergeev917@gmail.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.