From: "Alexander E. Patrakov" <patrakov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Guido Trentalancia
<guido-D1bseh+SzQhuxeB9wqlrNw@public.gmane.org>,
Andrei Borzenkov
<arvidjaar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] dracut: add support for updating the CPU microcode
Date: Sat, 16 Apr 2016 20:20:10 +0500 [thread overview]
Message-ID: <5712582A.2090502@gmail.com> (raw)
In-Reply-To: <1460814862.4296.4.camel-D1bseh+SzQhuxeB9wqlrNw@public.gmane.org>
16.04.2016 18:54, Guido Trentalancia пишет:
> Hello Andrei,
>
> thanks for getting back on this...
>
> On Sat, 16/04/2016 at 09.01 +0300, Andrei Borzenkov wrote:
>> 16.04.2016 02:18, Guido Trentalancia пишет:
>>> This is the initial version of a new "microcode" dracut module
>>> that can be used to update the microcode on Intel(R) CPUs.
>>>
>>
>> ??? dracut already supports early microcode loading, why it is not
>> enough and what problem this patch solves?
>
> To be honest, I didn't notice it. I was expecting such support, if
> available, to be a module and I couldn't find it, so I wrote it.
>
> However, I have noticed it is much simpler than the actual
> implementation. It doesn't differentiate between Intel and AMD (why it
> should ?), it just loads the microcode in the standard location as
> defined by the microcode update utility.
The microcode update utility stopped working when a Haswell microcode
update got released that makes some CPU instructions illegal (because
they didn't work properly in the first place). Please see
http://bugs.debian.org/762195
Sure, glibc no longer uses these instructions, but now (exactly to avoid
repetition of this bug) the only supported way to update the microcode
is to place it in the initcpio so that "early microcode update" in the
kernel loader notices it.
--
Alexander E. Patrakov
next prev parent reply other threads:[~2016-04-16 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 23:18 [PATCH] dracut: add support for updating the CPU microcode Guido Trentalancia
[not found] ` <1460762332.3054.2.camel-D1bseh+SzQhuxeB9wqlrNw@public.gmane.org>
2016-04-16 6:01 ` Andrei Borzenkov
[not found] ` <5711D522.3090907-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-16 13:54 ` Guido Trentalancia
[not found] ` <1460814862.4296.4.camel-D1bseh+SzQhuxeB9wqlrNw@public.gmane.org>
2016-04-16 15:20 ` Alexander E. Patrakov [this message]
[not found] ` <5712582A.2090502-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-16 21:05 ` Guido Trentalancia
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=5712582A.2090502@gmail.com \
--to=patrakov-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=arvidjaar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=guido-D1bseh+SzQhuxeB9wqlrNw@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.