From: Stanislav Kozina <skozina@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Petr Oros <poros@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/microcode/intel: print previous microcode revision during early update
Date: Wed, 07 Feb 2018 21:05:20 +0100 [thread overview]
Message-ID: <1518033920.1872.23.camel@redhat.com> (raw)
In-Reply-To: <20180207152158.GB8698@pd.tnic>
> Now let's take a step back: you don't really need the previous revision
> in the spectre case! Not really.
I understand all your points.
We submitted the patch to ease debugging of microcode issues where the
systems impacted are not yet identified and thus can't be blacklisted.
Best Regards,
-Stanislav
prev parent reply other threads:[~2018-02-07 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 10:34 [PATCH] x86/microcode/intel: print previous microcode revision during early update Petr Oros
2018-01-26 10:41 ` Borislav Petkov
2018-01-26 11:45 ` Petr Oros
2018-01-26 11:58 ` Borislav Petkov
2018-01-26 13:50 ` Petr Oros
2018-01-26 14:49 ` Borislav Petkov
2018-02-01 18:40 ` Petr Oros
2018-02-07 14:02 ` Stanislav Kozina
2018-02-07 15:21 ` Borislav Petkov
2018-02-07 20:05 ` Stanislav Kozina [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=1518033920.1872.23.camel@redhat.com \
--to=skozina@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=poros@redhat.com \
--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 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.