[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250830092514.GAaLLDepwTQpZG5KnR@fat_crate.local>
Date: Sat, 30 Aug 2025 11:25:14 +0200
From: Borislav Petkov <bp@...en8.de>
To: Sohil Mehta <sohil.mehta@...el.com>
Cc: Borislav Petkov <bp@...nel.org>, X86 ML <x86@...nel.org>,
"Chang S. Bae" <chang.seok.bae@...el.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -v1 2/2] x86/microcode: Add microcode loader debugging
functionality
On Fri, Aug 29, 2025 at 04:25:13PM -0700, Sohil Mehta wrote:
> My only concern is someone could easily enable it by mistake. It might
> lead to unnecessary reports and debug. Maybe we print a scary dmesg log
> whenever CONFIG_MICROCODE_DBG is enabled? That would be easy to spot in
> reports, and hopefully it would deter folks from enabling it unnecessarily.
When that happens, we'll add the cmdline switch as an additional precaution
but I'm not worried - we look .configs on bug reports.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists