From: Borislav Petkov <bp@alien8.de>
To: Zhenzhong Duan <zhenzhong.duan@oracle.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
mingo@redhat.com, tglx@linutronix.de,
Srinivas REDDY Eeda <srinivas.eeda@oracle.com>,
hpa@zytor.com
Subject: Re: [PATCH] x86/microcode/intel: Ensure new microcode processor flags match with cpu's pf
Date: Tue, 19 Jun 2018 11:12:05 +0200 [thread overview]
Message-ID: <20180619091205.GA30870@zn.tnic> (raw)
In-Reply-To: <ed92d414-9869-cd06-eee1-1035cc574cf4@oracle.com>
On Tue, Jun 19, 2018 at 12:49:40PM +0800, Zhenzhong Duan wrote:
> Imagine kernel already found a microcode blob A with extended sig/pf
> matching current cpu, then another microcode B is checked which doesn't
> match current cpu...
Do you see the
if (!microcode_matches(mc_header, uci->cpu_sig.sig)) {
call a couple of lines earlier?
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-06-19 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 8:16 [PATCH] x86/microcode/intel: Ensure new microcode processor flags match with cpu's pf Zhenzhong Duan
2018-06-18 19:56 ` Borislav Petkov
2018-06-19 4:49 ` Zhenzhong Duan
2018-06-19 9:12 ` Borislav Petkov [this message]
2018-06-19 9:24 ` Zhenzhong Duan
2018-06-19 9:35 ` Borislav Petkov
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=20180619091205.GA30870@zn.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=srinivas.eeda@oracle.com \
--cc=tglx@linutronix.de \
--cc=zhenzhong.duan@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