All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Lendacky <thomas.lendacky@amd.com>
To: Borislav Petkov <bp@alien8.de>, X86 ML <x86@kernel.org>
Cc: Arjan Van De Ven <arjan.van.de.ven@intel.com>,
	Ashok Raj <ashok.raj@intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/7] x86/microcode: Improve late loading
Date: Mon, 5 Mar 2018 16:12:39 -0600	[thread overview]
Message-ID: <a9162ec0-0440-3369-5c07-c6d58fdb7154@amd.com> (raw)
In-Reply-To: <20180228102846.13447-1-bp@alien8.de>

On 2/28/2018 4:28 AM, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
> 
> Hi,
> 
> here are a bunch of patches which improve microcode late loading.
> 
> Before you read any further: the early loading method is still the
> preferred one and you should always do that. This patchset is improving
> the late loading mechanism for long running jobs and cloud use cases -
> i.e., use cases where early loading is, hm, a bit problematic.
> 
> Ashok Raj (4):
>   x86/microcode/intel: Check microcode revision before updating sibling
>     threads
>   x86/microcode/intel: Writeback and invalidate caches before updating
>     microcode
>   x86/microcode: Do not upload microcode if CPUs are offline
>   x86/microcode: Synchronize late microcode loading
> 
> Borislav Petkov (3):
>   x86/microcode: Get rid of struct apply_microcode_ctx
>   x86/microcode/intel: Look into the patch cache first
>   x86/microcode: Request microcode on the BSP
> 
>  arch/x86/kernel/cpu/microcode/core.c  | 158 +++++++++++++++++++++++++---------
>  arch/x86/kernel/cpu/microcode/intel.c |  48 +++++++++--
>  2 files changed, 159 insertions(+), 47 deletions(-)
> 

Tested on my Family 17h (EPYC) system (including taking CPUs offline and
back on before and after reloads).  I'll try and find some additional
systems to test on, but for now:

Tested-by: Tom Lendacky <thomas.lendacky@amd.com>

  parent reply	other threads:[~2018-03-05 22:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28 10:28 Borislav Petkov
2018-02-28 10:28 ` [PATCH 1/7] x86/microcode: Get rid of struct apply_microcode_ctx Borislav Petkov
2018-03-08  9:25   ` [tip:x86/pti] " tip-bot for Borislav Petkov
2018-02-28 10:28 ` [PATCH 2/7] x86/microcode/intel: Check microcode revision before updating sibling threads Borislav Petkov
2018-03-08  9:25   ` [tip:x86/pti] " tip-bot for Ashok Raj
2018-02-28 10:28 ` [PATCH 3/7] x86/microcode/intel: Writeback and invalidate caches before updating microcode Borislav Petkov
2018-03-08  9:26   ` [tip:x86/pti] " tip-bot for Ashok Raj
2018-02-28 10:28 ` [PATCH 4/7] x86/microcode: Do not upload microcode if CPUs are offline Borislav Petkov
2018-02-28 13:11   ` Henrique de Moraes Holschuh
2018-02-28 13:26     ` Raj, Ashok
2018-02-28 19:07       ` Henrique de Moraes Holschuh
2018-03-05 22:06   ` Tom Lendacky
2018-03-08  9:26   ` [tip:x86/pti] " tip-bot for Ashok Raj
2018-02-28 10:28 ` [PATCH 5/7] x86/microcode/intel: Look into the patch cache first Borislav Petkov
2018-03-08  9:27   ` [tip:x86/pti] " tip-bot for Borislav Petkov
2018-02-28 10:28 ` [PATCH 6/7] x86/microcode: Request microcode on the BSP Borislav Petkov
2018-03-05 22:08   ` Tom Lendacky
2018-03-08  9:27   ` [tip:x86/pti] " tip-bot for Borislav Petkov
2018-02-28 10:28 ` [PATCH 7/7] x86/microcode: Synchronize late microcode loading Borislav Petkov
2018-02-28 13:59   ` Henrique de Moraes Holschuh
2018-02-28 14:08     ` Borislav Petkov
2018-02-28 17:48       ` Henrique de Moraes Holschuh
2018-03-05 22:09   ` Tom Lendacky
2018-03-08  9:28   ` [tip:x86/pti] " tip-bot for Ashok Raj
2018-03-05 22:12 ` Tom Lendacky [this message]
2018-03-05 23:51   ` [PATCH 0/7] x86/microcode: Improve late loading Raj, Ashok

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=a9162ec0-0440-3369-5c07-c6d58fdb7154@amd.com \
    --to=thomas.lendacky@amd.com \
    --cc=arjan.van.de.ven@intel.com \
    --cc=ashok.raj@intel.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.org \
    --subject='Re: [PATCH 0/7] x86/microcode: Improve late loading' \
    /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

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.