[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240627220040.1897cde7@jacob-builder>
Date: Thu, 27 Jun 2024 22:00:40 -0700
From: Jacob Pan <jacob.jun.pan@...ux.intel.com>
To: Sohil Mehta <sohil.mehta@...el.com>
Cc: Xin Li <xin@...or.com>, "X86 Kernel" <x86@...nel.org>, LKML
<linux-kernel@...r.kernel.org>, "Thomas Gleixner" <tglx@...utronix.de>,
Dave Hansen <dave.hansen@...el.com>, "H. Peter Anvin" <hpa@...or.com>, Ingo
Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
<linux-perf-users@...r.kernel.org>, Peter Zijlstra <peterz@...radead.org>,
Andi Kleen <andi.kleen@...el.com>, Xin Li <xin3.li@...el.com>,
jacob.jun.pan@...ux.intel.com
Subject: Re: [PATCH v2 1/6] x86/irq: Add enumeration of NMI source reporting
CPU feature
On Fri, 21 Jun 2024 16:00:47 -0700, Sohil Mehta <sohil.mehta@...el.com>
wrote:
> >> +config X86_NMI_SOURCE
> >
> > Lets reuse X86_FRED instead of adding another hard config option. See
> > below.
> >
>
> I mostly agree with the suggestion here but there seems to be a bit of
> confusion regarding feature availability and feature activation.
>
> Availability and activation of X86_FEATURE_NMI_SOURCE depends on FRED
> but not the other way around.
>
> In other words, CONFIG_X86_NMI_SOURCE would only be useful if someone
> wants to disable NMI_SOURCE even if both X86_FEATURE_FRED and
> X86_FEATURE_NMI_SOURCE are available on a platform.
>
> This seems unlikely to me. Reusing CONFIG_X86_FRED seems reasonable.
agreed, will remove CONFIG_X86_NMI_SOURCE
Thanks,
Jacob
Powered by blists - more mailing lists