From: Greg KH <gregkh@linuxfoundation.org>
To: Ashok Raj <ashok.raj@intel.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, bp@suse.de, thomas.lendacky@amd.com,
arjan.van.de.ven@intel.com, asit.k.mallick@intel.com
Subject: Re: [4.15 & 4.14 stable 00/12] Series to update microcode loading.
Date: Tue, 10 Apr 2018 17:47:51 +0200 [thread overview]
Message-ID: <20180410154751.GA11614@kroah.com> (raw)
In-Reply-To: <1523039426-3938-1-git-send-email-ashok.raj@intel.com>
On Fri, Apr 06, 2018 at 11:30:14AM -0700, Ashok Raj wrote:
> Hi Greg
>
> Here is a series that addresses microcode loading stability issues post
> Spectre. All of them are simply cherry-picked and the patches themselves
> have the upstream commit ID's.
>
> I checked this for Intel platforms and thanks to Boris for checking
> on AMD platforms.
Thanks, now queued up.
> I'm still working on a 4.9 backport, will send those once i get them to
> work. stop_machine differences seem big enough that i might choose a
> different approach for the 4.9 backport.
Ick, be careful, it's best to stick with almost identical code where
ever possible. Otherwise you are almost always guaranteed to break
something :(
greg k-h
prev parent reply other threads:[~2018-04-10 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 18:30 [4.15 & 4.14 stable 00/12] Series to update microcode loading Ashok Raj
2018-04-06 18:30 ` [4.15 & 4.14 stable 01/12] x86/microcode: Propagate return value from updating functions Ashok Raj
2018-04-06 18:30 ` [4.15 & 4.14 stable 02/12] x86/CPU: Add a microcode loader callback Ashok Raj
2018-04-06 18:30 ` [4.15 & 4.14 stable 03/12] x86/CPU: Check CPU feature bits after microcode upgrade Ashok Raj
2018-04-06 18:30 ` [4.15 & 4.14 stable 04/12] x86/microcode: Get rid of struct apply_microcode_ctx Ashok Raj
2018-04-06 18:30 ` [4.15 & 4.14 stable 05/12] x86/microcode/intel: Check microcode revision before updating sibling threads Ashok Raj
2018-04-06 18:30 ` [4.15 & 4.14 stable 06/12] x86/microcode/intel: Writeback and invalidate caches before updating microcode Ashok Raj
2018-04-06 18:30 ` [4.15 & 4.14 stable 07/12] x86/microcode: Do not upload microcode if CPUs are offline Ashok Raj
2018-04-06 18:30 ` [4.15 & 4.14 stable 08/12] x86/microcode/intel: Look into the patch cache first Ashok Raj
2018-04-06 18:30 ` [4.15 & 4.14 stable 09/12] x86/microcode: Request microcode on the BSP Ashok Raj
2018-04-06 18:30 ` [4.15 & 4.14 stable 10/12] x86/microcode: Synchronize late microcode loading Ashok Raj
2018-04-06 18:30 ` [4.15 & 4.14 stable 11/12] x86/microcode: Attempt late loading only when new microcode is present Ashok Raj
2018-04-06 18:30 ` [4.15 & 4.14 stable 12/12] x86/microcode: Fix CPU synchronization routine Ashok Raj
2018-04-10 15:47 ` Greg KH [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=20180410154751.GA11614@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arjan.van.de.ven@intel.com \
--cc=ashok.raj@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
/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).