mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tony W Wang-oc <TonyWWang-oc@zhaoxin.com>
To: Thomas Gleixner <tglx@linutronix.de>, <mingo@redhat.com>,
	<bp@alien8.de>, <hpa@zytor.com>, <x86@kernel.org>,
	<luto@kernel.org>, <pawan.kumar.gupta@linux.intel.com>,
	<peterz@infradead.org>, <fenghua.yu@intel.com>,
	<vineela.tummalapalli@intel.com>, <linux-kernel@vger.kernel.org>
Cc: <DavidWang@zhaoxin.com>, <CooperYan@zhaoxin.com>,
	<QiyuanWang@zhaoxin.com>, <HerryYang@zhaoxin.com>
Subject: Re: [PATCH] x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
Date: Fri, 17 Jan 2020 09:29:45 +0800	[thread overview]
Message-ID: <b61738fe-4a2f-db39-4740-8c4a4ee5d91d@zhaoxin.com> (raw)
In-Reply-To: <87r1zzuy48.fsf@nanos.tec.linutronix.de>



On 17/01/2020 01:09, Thomas Gleixner wrote:
> Tony,
> 
> Tony W Wang-oc <TonyWWang-oc@zhaoxin.com> writes:
> 
>> @@ -1023,6 +1023,7 @@ static void identify_cpu_without_cpuid(struct cpuinfo_x86 *c)
>>  #define MSBDS_ONLY		BIT(5)
>>  #define NO_SWAPGS		BIT(6)
>>  #define NO_ITLB_MULTIHIT	BIT(7)
>> +#define NO_SPECTRE_V2		BIT(8)
>>  
>>  #define VULNWL(_vendor, _family, _model, _whitelist)	\
>>  	{ X86_VENDOR_##_vendor, _family, _model, X86_FEATURE_ANY, _whitelist }
>> @@ -1084,6 +1085,10 @@ static const __initconst struct x86_cpu_id cpu_vuln_whitelist[] = {
>>  	/* FAMILY_ANY must be last, otherwise 0x0f - 0x12 matches won't work */
>>  	VULNWL_AMD(X86_FAMILY_ANY,	NO_MELTDOWN | NO_L1TF | NO_MDS | NO_SWAPGS | NO_ITLB_MULTIHIT),
>>  	VULNWL_HYGON(X86_FAMILY_ANY,	NO_MELTDOWN | NO_L1TF | NO_MDS | NO_SWAPGS | NO_ITLB_MULTIHIT),
>> +
>> +	/* Zhaoxin Family 7 */
>> +	VULNWL(CENTAUR,	7, X86_MODEL_ANY,	NO_SPECTRE_V2),
>> +	VULNWL(ZHAOXIN,	7, X86_MODEL_ANY,	NO_SPECTRE_V2),
>>  	{}
>>  };
>>  
>> @@ -1116,7 +1121,9 @@ static void __init cpu_set_bug_bits(struct cpuinfo_x86 *c)
>>  		return;
>>  
>>  	setup_force_cpu_bug(X86_BUG_SPECTRE_V1);
>> -	setup_force_cpu_bug(X86_BUG_SPECTRE_V2);
>> +
>> +	if (!cpu_matches(NO_SPECTRE_V2))
>> +		setup_force_cpu_bug(X86_BUG_SPECTRE_V2);
> 
> That's way better. But as you might have noticed yourself this conflicts
> with the other patch which excludes these machines from the SWAPGS bug.
> 
> Granted it's a trivial conflict, but maintainers are not there to mop up
> the mess others create. So the right thing here is to resend both
> patches as a patch series with the conflict properly resolved.
> 

Sorry for this conflict. Will resend these two patches as a patch set.

Sincerely
TonyWWang-oc

      parent reply	other threads:[~2020-01-17  1:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16  3:47 Tony W Wang-oc
2020-01-16 17:09 ` Thomas Gleixner
2020-01-16 18:07   ` Borislav Petkov
2020-01-17  1:32     ` Tony W Wang-oc
2020-01-17  1:29   ` Tony W Wang-oc [this message]

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=b61738fe-4a2f-db39-4740-8c4a4ee5d91d@zhaoxin.com \
    --to=tonywwang-oc@zhaoxin.com \
    --cc=CooperYan@zhaoxin.com \
    --cc=DavidWang@zhaoxin.com \
    --cc=HerryYang@zhaoxin.com \
    --cc=QiyuanWang@zhaoxin.com \
    --cc=bp@alien8.de \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=vineela.tummalapalli@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®