From: Borislav Petkov <bp@suse.de>
To: speck@linutronix.de
Subject: [MODERATED] Re: Re: [patch 03/15] Hidden 3
Date: Wed, 16 May 2018 10:53:50 +0200 [thread overview]
Message-ID: <20180516085350.GA17184@pd.tnic> (raw)
In-Reply-To: <alpine.DEB.2.21.1805160955420.1627@nanos.tec.linutronix.de>
On Wed, May 16, 2018 at 10:07:55AM +0200, speck for Thomas Gleixner wrote:
> Similarly, we don't reevaluate mitigation selection and command line
> options after early boot, so just special casing it for virtualization does
> not make much sense to me.
Yes, we do:
void microcode_check(void)
...
pr_warn("x86/CPU: CPU features have changed after loading microcode, but might not take effect.\n");
pr_warn("x86/CPU: Please consider either early loading through initrd/built-in or a potential BIOS update.\n");
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2018-05-16 8:54 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 14:00 [patch 00/15] Hidden 0 Thomas Gleixner
2018-05-13 14:00 ` [patch 01/15] Hidden 1 Thomas Gleixner
2018-05-13 22:17 ` [MODERATED] " Borislav Petkov
2018-05-15 9:30 ` Paolo Bonzini
2018-05-16 2:32 ` Konrad Rzeszutek Wilk
2018-05-16 7:51 ` Thomas Gleixner
2018-05-13 14:00 ` [patch 02/15] Hidden 2 Thomas Gleixner
2018-05-16 2:39 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-13 14:00 ` [patch 03/15] Hidden 3 Thomas Gleixner
2018-05-14 10:02 ` [MODERATED] " Borislav Petkov
2018-05-16 2:49 ` Konrad Rzeszutek Wilk
2018-05-16 8:07 ` Thomas Gleixner
2018-05-16 8:53 ` Borislav Petkov [this message]
2018-05-13 14:00 ` [patch 04/15] Hidden 4 Thomas Gleixner
2018-05-14 11:11 ` [MODERATED] " Borislav Petkov
2018-05-16 2:53 ` Konrad Rzeszutek Wilk
2018-05-13 14:00 ` [patch 05/15] Hidden 5 Thomas Gleixner
2018-05-14 11:18 ` [MODERATED] " Borislav Petkov
2018-05-16 3:24 ` Konrad Rzeszutek Wilk
2018-05-16 9:09 ` Thomas Gleixner
2018-05-13 14:00 ` [patch 06/15] Hidden 6 Thomas Gleixner
2018-05-14 12:01 ` [MODERATED] " Borislav Petkov
2018-05-14 12:09 ` Peter Zijlstra
2018-05-14 12:46 ` Thomas Gleixner
2018-05-16 3:15 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-16 8:44 ` Thomas Gleixner
2018-05-13 14:00 ` [patch 07/15] Hidden 7 Thomas Gleixner
2018-05-14 17:07 ` [MODERATED] " Borislav Petkov
2018-05-16 3:22 ` Konrad Rzeszutek Wilk
2018-05-16 8:46 ` Thomas Gleixner
2018-05-16 12:15 ` Thomas Gleixner
2018-05-13 14:00 ` [patch 08/15] Hidden 8 Thomas Gleixner
2018-05-14 17:58 ` [MODERATED] " Borislav Petkov
2018-05-16 3:31 ` Konrad Rzeszutek Wilk
2018-05-16 12:22 ` Thomas Gleixner
2018-05-16 13:48 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-13 14:00 ` [patch 09/15] Hidden 9 Thomas Gleixner
2018-05-14 19:49 ` [MODERATED] " Borislav Petkov
2018-05-13 14:00 ` [patch 10/15] Hidden 10 Thomas Gleixner
2018-05-16 3:38 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-16 8:51 ` Thomas Gleixner
2018-05-13 14:00 ` [patch 11/15] Hidden 11 Thomas Gleixner
2018-05-14 20:02 ` [MODERATED] " Borislav Petkov
2018-05-16 3:35 ` Konrad Rzeszutek Wilk
2018-05-16 8:50 ` Thomas Gleixner
2018-05-13 14:01 ` [patch 12/15] Hidden 12 Thomas Gleixner
2018-05-14 20:18 ` [MODERATED] " Borislav Petkov
2018-05-16 3:40 ` Konrad Rzeszutek Wilk
2018-05-13 14:01 ` [patch 13/15] Hidden 13 Thomas Gleixner
2018-05-15 9:27 ` [MODERATED] " Borislav Petkov
2018-05-16 3:42 ` Konrad Rzeszutek Wilk
2018-05-16 8:56 ` Thomas Gleixner
2018-05-13 14:01 ` [patch 14/15] Hidden 14 Thomas Gleixner
2018-05-15 15:35 ` [MODERATED] " Borislav Petkov
2018-05-16 3:44 ` Konrad Rzeszutek Wilk
2018-05-13 14:01 ` [patch 15/15] Hidden 15 Thomas Gleixner
2018-05-13 14:22 ` [patch 00/15] Hidden 0 Thomas Gleixner
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=20180516085350.GA17184@pd.tnic \
--to=bp@suse.de \
--cc=speck@linutronix.de \
/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.