Subject: Re: [PATCH 2/6] x86/microcode: Merge early loader
To: Borislav Petkov <bp@alien8.de>, Josh Boyer <jwboyer@fedoraproject.org>
References: <1445334889-300-1-git-send-email-bp@alien8.de>
 <1445334889-300-3-git-send-email-bp@alien8.de>
 <CA+5PVA5McA9pL9Nvz8GsU45mjqHDgf=9YHNWzR0jK7YwQUgS5Q@mail.gmail.com>
 <20151106193122.GE19522@pd.tnic>
Cc: Laura Abbott <labbott@redhat.com>, X86 ML <x86@kernel.org>,
        LKML <linux-kernel@vger.kernel.org>
From: Harald Hoyer <harald@redhat.com>
Message-ID: <56406A75.3030006@redhat.com>
Date: Mon, 9 Nov 2015 10:42:13 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <20151106193122.GE19522@pd.tnic>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1078
Lines: 24

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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/