From: Borislav Petkov <bp@alien8.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Chuck Ebbert <cebbert.lkml@gmail.com>,
Andy Lutomirski <luto@amacapital.net>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: x86, microcode: BUG: microcode update that changes x86_capability
Date: Thu, 25 Sep 2014 14:10:07 +0200 [thread overview]
Message-ID: <20140925121007.GA25334@nazgul.tnic> (raw)
In-Reply-To: <20140925113643.GB10569@khazad-dum.debian.net>
On Thu, Sep 25, 2014 at 08:36:45AM -0300, Henrique de Moraes Holschuh wrote:
> This isn't an useless fix, it will allow systems without early initramfs
> support to operate correctly after a microcode update.
So what do we do if we update the microcode late and some userspace task
is using HLE and all of a sudden it segfaults and gets killed due to
#UD. I'll forward all those complaint emails to you then, no?
:-)
What's saying is, a reboot in this case is maybe the lesser of two evils.
--
Regards/Gruss,
Boris.
--
next prev parent reply other threads:[~2014-09-25 12:10 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 13:52 x86, microcode: BUG: microcode update that changes x86_capability Henrique de Moraes Holschuh
2014-09-18 19:14 ` Andy Lutomirski
2014-09-18 19:53 ` Chuck Ebbert
2014-09-18 19:55 ` H. Peter Anvin
2014-09-18 20:06 ` Henrique de Moraes Holschuh
2014-09-19 0:13 ` Henrique de Moraes Holschuh
2014-09-19 0:23 ` Andy Lutomirski
2014-09-19 0:28 ` H. Peter Anvin
2014-09-19 1:00 ` Andy Lutomirski
2014-09-19 8:03 ` Borislav Petkov
2014-09-19 11:00 ` Henrique de Moraes Holschuh
2014-09-19 11:29 ` Borislav Petkov
2014-09-19 12:54 ` Chuck Ebbert
2014-09-19 13:14 ` Josh Boyer
2014-09-19 13:37 ` Chuck Ebbert
2014-09-19 15:00 ` Borislav Petkov
2014-09-19 16:13 ` Andy Lutomirski
2014-09-19 16:54 ` Henrique de Moraes Holschuh
2014-09-19 16:42 ` Henrique de Moraes Holschuh
2014-09-23 20:00 ` Borislav Petkov
2014-09-24 14:56 ` Henrique de Moraes Holschuh
2014-09-24 15:00 ` Andy Lutomirski
2014-09-24 17:45 ` Henrique de Moraes Holschuh
2014-09-24 17:48 ` Andy Lutomirski
2014-09-24 18:59 ` Henrique de Moraes Holschuh
2014-09-24 19:34 ` Andy Lutomirski
2014-09-25 8:57 ` Borislav Petkov
2014-09-25 8:51 ` Borislav Petkov
2014-09-25 11:36 ` Henrique de Moraes Holschuh
2014-09-25 12:10 ` Borislav Petkov [this message]
2014-09-25 14:40 ` Henrique de Moraes Holschuh
2014-09-25 14:56 ` Borislav Petkov
2014-09-25 15:30 ` Henrique de Moraes Holschuh
2014-09-25 15:50 ` Borislav Petkov
2014-09-25 16:41 ` Henrique de Moraes Holschuh
2014-09-25 16:57 ` Borislav Petkov
2014-09-25 17:09 ` Henrique de Moraes Holschuh
2014-09-19 13:51 ` Henrique de Moraes Holschuh
2014-09-19 14:49 ` Borislav Petkov
2014-09-19 17:22 ` Henrique de Moraes Holschuh
2014-09-19 22:35 ` Henrique de Moraes Holschuh
2014-09-29 11:51 ` Henrique de Moraes Holschuh
2014-09-19 9:56 ` Henrique de Moraes Holschuh
2014-09-19 16:11 ` Henrique de Moraes Holschuh
2014-09-22 0:37 ` Andi Kleen
2014-09-22 0:51 ` H. Peter Anvin
2014-09-22 0:58 ` Andi Kleen
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=20140925121007.GA25334@nazgul.tnic \
--to=bp@alien8.de \
--cc=cebbert.lkml@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
/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;
as well as URLs for NNTP newsgroup(s).