From: Harald Hoyer <harald@redhat.com>
To: Borislav Petkov <bp@alien8.de>, Josh Boyer <jwboyer@fedoraproject.org>
Cc: Laura Abbott <labbott@redhat.com>, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/6] x86/microcode: Merge early loader
Date: Mon, 9 Nov 2015 10:42:13 +0100 [thread overview]
Message-ID: <56406A75.3030006@redhat.com> (raw)
In-Reply-To: <20151106193122.GE19522@pd.tnic>
Am 06.11.2015 um 20:31 schrieb Borislav Petkov:
> On Fri, Nov 06, 2015 at 02:22:42PM -0500, Josh Boyer wrote:
>> So this broke dracut. Dracut will look at the config file for the
>> INTEL or AMD early config options being set.
>
> Nothing outside the kernel should depend on Kconfig symbols.
>
>> Do we have suggestions on how to work this out going forward? I
>> suppose we could assume the check should only be done on 4.3 or older
>> kernels, but I'm not sure making assumptions about newer kernels is a
>> great idea either.
>
> How about always adding AMD and Intel microcode always? Maybe with a
> switch to disable adding any microcode for testing purposes only...
>
Will this work with kernels not supporting the microcode loading?
Theoretically the old kernels would just unpack all cpios one after the other,
right?
next prev parent reply other threads:[~2015-11-09 9:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 9:54 [PATCH 0/6] x86/microcode: Merge the early loader Borislav Petkov
2015-10-20 9:54 ` [PATCH 1/6] x86/microcode: Unmodularize driver Borislav Petkov
2015-10-21 10:07 ` [tip:ras/core] x86/microcode: Unmodularize the microcode driver tip-bot for Borislav Petkov
2015-10-20 9:54 ` [PATCH 2/6] x86/microcode: Merge early loader Borislav Petkov
2015-10-21 10:07 ` [tip:ras/core] x86/microcode: Merge the early microcode loader tip-bot for Borislav Petkov
2015-11-06 19:22 ` [PATCH 2/6] x86/microcode: Merge early loader Josh Boyer
2015-11-06 19:31 ` Borislav Petkov
2015-11-09 9:42 ` Harald Hoyer [this message]
2015-11-09 10:11 ` Borislav Petkov
2015-10-20 9:54 ` [PATCH 3/6] x86/microcode: Remove modularization leftovers Borislav Petkov
2015-10-21 10:08 ` [tip:ras/core] " tip-bot for Borislav Petkov
2015-10-20 9:54 ` [PATCH 4/6] x86/microcode/amd: Remove maintainers from comments Borislav Petkov
2015-10-21 10:08 ` [tip:ras/core] " tip-bot for Borislav Petkov
2015-10-20 9:54 ` [PATCH 5/6] x86/microcode/intel: Move ifdef DEBUG inside the function Borislav Petkov
2015-10-21 10:08 ` [tip:ras/core] x86/microcode/intel: Move #ifdef " tip-bot for Borislav Petkov
2015-10-20 9:54 ` [PATCH 6/6] MAINTAINERS: Unify microcode driver section Borislav Petkov
2015-10-21 10:09 ` [tip:ras/core] MAINTAINERS: Unify the " tip-bot for Borislav Petkov
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=56406A75.3030006@redhat.com \
--to=harald@redhat.com \
--cc=bp@alien8.de \
--cc=jwboyer@fedoraproject.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox