[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161215171422.4blmkcgqduribmbj@pd.tnic>
Date: Thu, 15 Dec 2016 18:14:22 +0100
From: Borislav Petkov <bp@...e.de>
To: Andrew Cooper <andrew.cooper3@...rix.com>
Cc: Jan Beulich <JBeulich@...e.com>, Juergen Gross <JGross@...e.com>,
xen-devel <xen-devel@...ts.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] Can't boot as Xen dom0 due to commit fe055896
On Thu, Dec 15, 2016 at 04:59:49PM +0000, Andrew Cooper wrote:
> Xen has the same logic as Linux does to look for an uncompressed
> microcode blob in the initrd and apply it early in boot.
>
> If dom0 goes looking, it should see the same microcode version as it has
> in its initrd.
So it sounds to me like I wanna do this:
---
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index dd47e60aabf5..e238119b5dff 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1202,6 +1202,7 @@ config X86_REBOOTFIXUPS
config MICROCODE
bool "CPU microcode loading support"
default y
+ depends on !XEN
depends on CPU_SUP_AMD || CPU_SUP_INTEL
select FW_LOADER
---help---
--
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
Powered by blists - more mailing lists