[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aBnMprnsFmPJDqaW@lx-t490>
Date: Tue, 6 May 2025 10:47:34 +0200
From: "Ahmed S. Darwish" <darwi@...utronix.de>
To: Ingo Molnar <mingo@...nel.org>
Cc: Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Cooper <andrew.cooper3@...rix.com>,
"H. Peter Anvin" <hpa@...or.com>,
John Ogness <john.ogness@...utronix.de>, x86@...nel.org,
x86-cpuid@...ts.linux.dev, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 13/26] x86/cpuid: Scan CPUID(0x2)
On Tue, 06 May 2025, Ingo Molnar wrote:
>
> Could we please emit a one-time syslog warning & diagnostic when we run
> across invalid or otherwise weird looking CPUID data, instead of just
> silently skipping and sanitizing it?
>
Sure; will do.
Thanks,
Ahmed
Powered by blists - more mailing lists