From: "Raj, Ashok" <ashok.raj@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: bp@suse.de, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ashok Raj <ashok.raj@intel.com>
Subject: Re: [PATCH] x86/microcode/intel: Check microcode revision before updating sibling threads
Date: Sat, 17 Feb 2018 04:10:43 -0800 [thread overview]
Message-ID: <20180217121042.GA23981@araj-mobl1.jf.intel.com> (raw)
In-Reply-To: <20180217075053.2muugr2ioqvawfxv@gmail.com>
Hi Ingo
On Sat, Feb 17, 2018 at 08:50:53AM +0100, Ingo Molnar wrote:
>
> Also, more fundamentally, during microcode early testing, isn't it possible for
> internal iterations of the microcode to have the same revision, but be different?
Atleast we don't do that here. Such debug microcode isn't OS loadable.
Anything that comes out ready for OS loading, the version will keep moving.
> This patch would prevent re-loading it - for a seemingly minimal benefit.
Cheers,
Ashok
next prev parent reply other threads:[~2018-02-17 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 19:34 Ashok Raj
2018-02-17 7:50 ` Ingo Molnar
2018-02-17 12:10 ` Raj, Ashok [this message]
2018-02-18 12:46 ` Ingo Molnar
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=20180217121042.GA23981@araj-mobl1.jf.intel.com \
--to=ashok.raj@intel.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®