[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2RPc7T0PCUubcjB@zn.tnic>
Date: Fri, 4 Nov 2022 00:32:03 +0100
From: Borislav Petkov <bp@...en8.de>
To: Ashok Raj <ashok.raj@...el.com>
Cc: Jithu Joseph <jithu.joseph@...el.com>, hdegoede@...hat.com,
markgross@...nel.org, tglx@...utronix.de, mingo@...hat.com,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
gregkh@...uxfoundation.org, tony.luck@...el.com,
linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org,
patches@...ts.linux.dev, ravi.v.shankar@...el.com,
thiago.macieira@...el.com, athenas.jimenez.gonzalez@...el.com
Subject: Re: [PATCH 07/14] x86/microcode/intel: Expose
microcode_sanity_check()
On Thu, Nov 03, 2022 at 12:25:32PM -0700, Ashok Raj wrote:
> CPU microcode has stayed the same for over 15 years roughly. Changing
> formats isn't something that's done lightly especially since there is cost
> of enabling in all OS's.
Yeah, because it has been that way for the last 15 years and that means
it'll not change in the future either. Yeah, right.
> Even if its only a few hundred lines of code, it seems odd to simply
> duplicate for the sake of fear of testing.
I don't think I ever said "fear" but rather that it would be real hard
to test. But it's not like you're reading my mails properly.
But don't worry about it. We'll change the microcode loader and if we
break the IFS thing in the process, then, oh well, sh*t happens.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists