[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8035D788-0F60-48B8-8B98-DC352EC9AE62@zytor.com>
Date: Wed, 04 Jun 2025 08:41:25 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Sohil Mehta <sohil.mehta@...el.com>, Xin Li <xin@...or.com>,
x86@...nel.org, linux-kernel@...r.kernel.org
CC: 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 9/9] x86/nmi: Print source information with the unknown NMI console message
I think printing the bitmap is fine for unknown bits set... after all, you might have surprise vectors. Maybe a list would be cleaner by some definition, but we already print bitmaps all over the place. It is not critical as long as the information necessary for debugging is there. In fact, it is often better for the information to be compact so users don't get tempted to abbreviate a bug report.
Powered by blists - more mailing lists