From: Peter Zijlstra <peterz@infradead.org>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
Tony Luck <tony.luck@intel.com>, Ashok Raj <ashok.raj@intel.com>,
Ravi V Shankar <ravi.v.shankar@intel.com>, x86 <x86@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/split_lock: Enumerate split lock feature on Sapphire Rapids
Date: Thu, 16 Jul 2020 21:50:10 +0200 [thread overview]
Message-ID: <20200716195010.GV10769@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200716193659.GA66451@romley-ivt3.sc.intel.com>
On Thu, Jul 16, 2020 at 12:37:00PM -0700, Fenghua Yu wrote:
> Hi, Thomas, Boris, Ingo,
>
> On Fri, Jun 26, 2020 at 02:55:34PM -0700, Fenghua Yu wrote:
> > Add Sapphire Rapids processor to CPU list to enumerate split lock
> > feature.
> >
> > Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
> > Reviewed-by: Tony Luck <tony.luck@intel.com>
> > ---
> > arch/x86/kernel/cpu/intel.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c
> > index c25a67a34bd3..dca069ad6671 100644
> > --- a/arch/x86/kernel/cpu/intel.c
> > +++ b/arch/x86/kernel/cpu/intel.c
> > @@ -1148,6 +1148,7 @@ static const struct x86_cpu_id split_lock_cpu_ids[] __initconst = {
> > X86_MATCH_INTEL_FAM6_MODEL(ATOM_TREMONT_L, 1),
> > X86_MATCH_INTEL_FAM6_MODEL(TIGERLAKE_L, 1),
> > X86_MATCH_INTEL_FAM6_MODEL(TIGERLAKE, 1),
> > + X86_MATCH_INTEL_FAM6_MODEL(SAPPHIRERAPIDS_X, 1),
> > {}
> > };
>
> Any comment on this patch?
The only comment I have is that us needing it is ludicrous :/ What's the
bloody point of having it 'enumerated' if you then still have to use FMS
lists.
There's nowhere near enough cursing in the comment that goes with that
list.
next prev parent reply other threads:[~2020-07-16 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 21:55 Fenghua Yu
2020-07-16 19:37 ` Fenghua Yu
2020-07-16 19:50 ` Peter Zijlstra [this message]
2020-07-16 19:53 ` Luck, Tony
2020-07-16 20:13 ` Fenghua Yu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200716195010.GV10769@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®