[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231122115826.GAZV3s4krKXI002KQ0@fat_crate.local>
Date: Wed, 22 Nov 2023 12:58:26 +0100
From: Borislav Petkov <bp@...en8.de>
To: Linux regressions mailing list <regressions@...ts.linux.dev>
Cc: lukas.bulwahn@...il.com, dave.hansen@...ux.intel.com,
hpa@...or.com, kernel-janitors@...r.kernel.org,
linux-kernel@...r.kernel.org, mingo@...hat.com, tglx@...utronix.de,
x86@...nel.org
Subject: Re: [regression] microcode files missing in initramfs imgages from
dracut (was Re: [PATCH] x86: Clean up remaining references to
CONFIG_MICROCODE_AMD)
On Wed, Nov 22, 2023 at 10:15:42AM +0100, Linux regression tracking (Thorsten Leemhuis) wrote:
> [1] unless you fiddle with things obviously internal; not sure if this
> case would qualify for him, but somehow I doubt it -- but I might be
> wrong there.
Well, think about it - by that logic, if CONFIG_* items are an ABI, we
will never ever be able to change any of them. Now that would be awful.
> Any progress on this?
We're thinking...
We might need an official scheme of stating what any given kernel image
supports for use by external tools which need it.
> BTW: I see that this could help preventing problems like the current one
> to happen in the far future. But how would that help the current
> situation (e.g. users that have an old dracut and updated the kernel
> without updating dracut)?
Update dracut too?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists