linux-kernel - Re: [PATCH v3] x86/CPU/AMD: Prefix messages with x86/amd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <dd78c64d-fa29-4f26-ace0-7dccbf169555@kernel.org>
Date: Sat, 10 Jan 2026 07:39:35 -0600
From: "Mario Limonciello (AMD) (kernel.org)" <superm1@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: mario.limonciello@....com, tglx@...utronix.de, mingo@...hat.com,
 dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Yazen Ghannam <yazen.ghannam@....com>
Subject: Re: [PATCH v3] x86/CPU/AMD: Prefix messages with x86/amd



On 1/9/2026 1:45 PM, Borislav Petkov wrote:
> On Fri, Jan 09, 2026 at 01:33:47PM -0600, Mario Limonciello (AMD) wrote:
>> To clarify which messages come from arch/x86/kernel/cpu/amd.c add
>> a prefix to all messages instead of just the previous reset reason.
> 
> The usual question: why do we need this?
> 

Well originally the reason was that another message was being added in a 
series.  But the review of the series was deciding not to do it that 
way.  But this way any other future messages pick up the prefix already.

It's a trivial patch, but if you want to wait until another message 
comes around again we can hold off.