Re: [PATCH] x86/microcode/intel: Panic on partial microcode update

[Maciej W. Rozycki]

On Mon, 27 Jul 2026, Nikolay Borisov wrote:

> >   We aim not to set a policy either, but at this point we have become aware
> > the CPU is in a bad state, so I think at the very least there needs to be
> > a way for the site manager to configure handling according to their needs,
> > and I think it should be killing the system by default.
> 
> For people who care that much about this, they likely are running huge fleets
> and already have daemons/agents(sic) which are monitoring dmesg and are taking
> actions accordingly. So that use case is not lost.

 But do they keep up to date databases of possible messages to match so as 
to act accordingly?  I think there is a need to communicate the severity 
of the situation somehow; cf. 
<https://lore.kernel.org/r/alpine.DEB.2.21.2607282230170.14485@xxxxxxxxxxxxxxxxx/>.

  Maciej