[prev in list] [next in list] [prev in thread] [next in thread]
List: gentoo-user
Subject: Re: [gentoo-user] Re: Where is CONFIG_MICROCODE gone in kernel 4.4.6-gentoo?
From: Neil Bothwick <neil () digimed ! co ! uk>
Date: 2016-04-30 16:50:44
Message-ID: 5B834F92-9FDA-417A-8BE0-87AD1B3014A0 () digimed ! co ! uk
[Download RAW message or body]
On 30 April 2016 16:02:49 BST, Peter Humphrey <peter@prh.myzen.co.uk> wrote:
> On Saturday 30 Apr 2016 10:05:40 Jonathan Callen wrote:
>
> > The proper way to load microcode into the kernel is now to have it
> be
> > part of an initramfs (the initramfs doesn't (I think) have to
> actually
> > do anything, just have the microcode firmware in the appropriate
> > location). This is because some things in userspace (like glibc
> itself)
> > only check once for certain CPU features at startup, and newer
> microcode
> > will actually disable some of those features on some CPUs (because
> they
> > are completely broken anyway). This means that loading the
> microcode
> > before any userspace programs run will ensure that applications like
> > /sbin/init won't crash just because a feature they thought they
> could
> > use suddenly disappeared.
>
> Still, it would be better if all kernel versions behaved the same way
> in
> this respect.
>
> --
> Rgds
> Peter
Not if the newer way is better, which appears to be the case here.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
[Attachment #3 (text/html)]
<html><head></head><body><div class="gmail_quote">On 30 April 2016 16:02:49 BST, \
Peter Humphrey <peter@prh.myzen.co.uk> wrote:<blockquote class="gmail_quote" \
style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); \
padding-left: 1ex;"> <pre class="k9mail">On Saturday 30 Apr 2016 10:05:40 Jonathan \
Callen wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex \
0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> The proper way to load \
microcode into the kernel is now to have it be<br /> part of an initramfs (the \
initramfs doesn't (I think) have to actually<br /> do anything, just have the \
microcode firmware in the appropriate<br /> location). This is because some things \
in userspace (like glibc itself)<br /> only check once for certain CPU features at \
startup, and newer microcode<br /> will actually disable some of those features on \
some CPUs (because they<br /> are completely broken anyway). This means that loading \
the microcode<br /> before any userspace programs run will ensure that applications \
like<br /> /sbin/init won't crash just because a feature they thought they could<br \
/> use suddenly disappeared.<br /></blockquote><br />Still, it would be better if all \
kernel versions behaved the same way in <br />this respect.<br \
/></pre></blockquote></div><br clear="all">Not if the newer way is better, which \
appears to be the case here. <br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.</body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic