From: Borislav Petkov <bp@alien8.de>
To: "Raj, Ashok" <ashok.raj@intel.com>
Cc: Mihai Carabas <mihai.carabas@oracle.com>,
linux-kernel@vger.kernel.org, boris.ostrovsky@oracle.com,
konrad.wilk@oracle.com, patrick.colp@oracle.com,
kanth.ghatraju@oracle.com, Jon.Grimm@amd.com,
Thomas.Lendacky@amd.com
Subject: Re: [PATCH 1/2] x86/microcode: Update late microcode in parallel
Date: Tue, 27 Aug 2019 14:25:01 +0200 [thread overview]
Message-ID: <20190827122501.GD29752@zn.tnic> (raw)
In-Reply-To: <20190826202339.GA49895@otc-nc-03>
On Mon, Aug 26, 2019 at 01:23:39PM -0700, Raj, Ashok wrote:
> > Cloud customers have expressed discontent as services disappear for a
> > prolonged time. The restriction is that only one core goes through the
> s/one core/one thread of a core/
>
> > update while other cores are quiesced.
> s/cores/other thread(s) of the core
Changed it to:
"Cloud customers have expressed discontent as services disappear for
a prolonged time. The restriction is that only one core (or only one
thread of a core in the case of an SMT system) goes through the update
while other cores (or respectively, SMT threads) are quiesced."
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-08-27 12:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 20:43 [PATCH] Parallel microcode update in Linux Mihai Carabas
2019-08-22 20:43 ` [PATCH] x86/microcode: Update microcode for all cores in parallel Mihai Carabas
2019-08-24 8:51 ` Borislav Petkov
2019-08-24 8:53 ` [PATCH 1/2] x86/microcode: Update late microcode " Borislav Petkov
2019-08-26 12:53 ` Boris Ostrovsky
2019-08-26 13:03 ` Borislav Petkov
2019-08-26 20:32 ` Raj, Ashok
2019-08-27 19:43 ` Boris Ostrovsky
2019-08-27 21:24 ` Boris Ostrovsky
2019-08-28 19:16 ` Borislav Petkov
2019-08-26 20:23 ` Raj, Ashok
2019-08-27 12:25 ` Borislav Petkov [this message]
2019-08-28 0:56 ` Raj, Ashok
2019-08-28 19:13 ` Borislav Petkov
2019-08-28 19:45 ` Raj, Ashok
2019-08-24 8:53 ` [PATCH 2/2] x86/microcode/intel: Issue the revision updated message only on the BSP Borislav Petkov
2019-08-26 13:34 ` Boris Ostrovsky
2019-08-26 13:45 ` Borislav Petkov
2019-10-01 17:43 ` [tip: x86/microcode] " tip-bot2 for Borislav Petkov
2019-10-01 17:43 ` [tip: x86/microcode] x86/microcode: Update late microcode in parallel tip-bot2 for Ashok Raj
2019-09-01 17:25 ` [PATCH] Parallel microcode update in Linux Pavel Machek
2019-09-02 7:27 ` Mihai Carabas
2019-09-02 7:39 ` Pavel Machek
2019-09-02 11:10 ` Mihai Carabas
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=20190827122501.GD29752@zn.tnic \
--to=bp@alien8.de \
--cc=Jon.Grimm@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=ashok.raj@intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=kanth.ghatraju@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.carabas@oracle.com \
--cc=patrick.colp@oracle.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
Powered by JetHome