[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250905104015.GBaLq-D343jvMEZ2KA@fat_crate.local>
Date: Fri, 5 Sep 2025 12:40:15 +0200
From: Borislav Petkov <bp@...en8.de>
To: Nathan Chancellor <nathan@...nel.org>
Cc: kernel test robot <oliver.sang@...el.com>,
Borislav Petkov <bp@...nel.org>, oe-lkp@...ts.linux.dev,
lkp@...el.com, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, X86 ML <x86@...nel.org>,
"Chang S. Bae" <chang.seok.bae@...el.com>,
Sohil Mehta <sohil.mehta@...el.com>,
Ryusuke Konishi <konishi.ryusuke@...il.com>,
linux-nilfs@...r.kernel.org
Subject: Re: [PATCH -v1 1/2] x86/microcode: Add microcode= cmdline parsing
On Thu, Sep 04, 2025 at 04:29:52PM -0700, Nathan Chancellor wrote:
> Does your QEMU boot via UEFI? This configuration has
>
> # CONFIG_EFI is not set
>
> so if I try to boot QEMU via OVMF, I get:
>
> BdsDxe: failed to load Boot0002 "UEFI Non-Block Boot Device" from VenMedia(1428F772-B64A-441E-B8C3-9EBDD7F893C7): Not Found
> BdsDxe: No bootable option or device was found.
> BdsDxe: Press any key to enter the Boot Manager Menu.
>
> Turning on CONFIG_EFI and CONFIG_EFI_STUB is enough for me to boot this
> configuration.
Yeah, I'm blindly following the testing instructions because I'm being
a guinea pig for the testing folks. :-)
Looks like those instructions need massaging.
> Looks like this configuration has
>
> CONFIG_LTO_CLANG_FULL=y
>
> so that's not too surprising :) turning that off or making it
>
> CONFIG_LTO_CLANG_THIN=y
>
> should be much quicker.
Yeah, I hear there might be some more room for improvements in parallelizing
more of the LTO work but I dunno - just rumours :-P
> I ran 200 boots using our simple Buildroot initrd and QEMU wrapper
> script [1] and saw no issues, however...
Yeah, that's a nicely debugged issue - I think you should simply send a proper
patch.
Thanks!
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists