linux-kernel - Re: [PATCH v6 4/9] x86/nmi: Assign and register NMI-source vectors

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: <232ab16f-218f-4c33-9a6c-1652eea9d444@intel.com>
Date: Tue, 3 Jun 2025 15:33:34 -0700
From: Sohil Mehta <sohil.mehta@...el.com>
To: Dave Hansen <dave.hansen@...el.com>, <x86@...nel.org>,
	<linux-kernel@...r.kernel.org>
CC: Xin Li <xin@...or.com>, "H . Peter Anvin" <hpa@...or.com>, Andy Lutomirski
	<luto@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar
	<mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, Dave Hansen
	<dave.hansen@...ux.intel.com>, Peter Zijlstra <peterz@...radead.org>, "Sean
 Christopherson" <seanjc@...gle.com>, Adrian Hunter <adrian.hunter@...el.com>,
	Kan Liang <kan.liang@...ux.intel.com>, Tony Luck <tony.luck@...el.com>,
	"Zhang Rui" <rui.zhang@...el.com>, Steven Rostedt <rostedt@...dmis.org>,
	"Andrew Cooper" <andrew.cooper3@...rix.com>, "Kirill A . Shutemov"
	<kirill.shutemov@...ux.intel.com>, Jacob Pan <jacob.pan@...ux.microsoft.com>,
	Andi Kleen <ak@...ux.intel.com>, Kai Huang <kai.huang@...el.com>, "Sandipan
 Das" <sandipan.das@....com>, <linux-perf-users@...r.kernel.org>,
	<linux-edac@...r.kernel.org>, <kvm@...r.kernel.org>,
	<linux-pm@...r.kernel.org>, <linux-trace-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 4/9] x86/nmi: Assign and register NMI-source vectors

On 6/3/2025 2:54 PM, Dave Hansen wrote:
> On 6/3/25 13:22, Sohil Mehta wrote:
>> With an enum, it's harder to figure out the exact sources when let's say
>> the source bitmap is printed as 0x0090.
> 
> Uhh, then don't print a bitmap. ;)
> 

Ah! Didn't look at it that way.

> /proc/cpuinfo doesn't print out CPUID leaves, it prints out bits mapped
> to strings.
> 

Hasn't that caused more pains than gains :p But, point taken, I'll give
it a shot.

> Look at the kmalloc trace points:
> 
>             Xorg-4589    [003] ..... 1568557.823993: kmalloc: ...
> gfp_flags=GFP_KERNEL
>             Xorg-4589    [003] ..... 1568557.823993: kmalloc: ...
> gfp_flags=GFP_KERNEL
> 
> gfp_flags are a bitmap, yet they're mapped out with strings and symbolic
> names.