Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp8572207ybl; Thu, 16 Jan 2020 19:55:43 -0800 (PST) X-Google-Smtp-Source: APXvYqzph1ASAbE223My5phiknFKHgOElDkF0GuSnCa2OVarvj+zG+m2fQNEG4mRSrm+SBaaZg8l X-Received: by 2002:aca:6545:: with SMTP id j5mr2086587oiw.60.1579233342737; Thu, 16 Jan 2020 19:55:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579233342; cv=none; d=google.com; s=arc-20160816; b=SlZQ2sLSh//ImXs5C9KC9dgJgWYit8zjm1FmVoIjPZHxnGjg4MMcc2uEuEUQk98KzJ aHQuNh1EQUWBOC5a/eNZP2Gz5ExB1Xny/5YL1KkLHAheHaPU6smztFQ/xPfp/qpimnkD R7daB6Ab36gwzAGKcOWk0/LrFv+vIPJMyLKibrSpd+OtZGX5YqKYWQdsP5Fze/2sUSB+ a2TIvO1ml+AmhtrsOVQsENsDwD1Clz51eJ8aeswVL/UtviicYazrLiHbeWbR73ImA3Fc fpnejFTwQrfPsaGjO8U0eQ485p3LKv1dSVULIE6mB7Pdu6bzn4VgLAZYHVzhOVTJGW15 ccEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=ccsONjpc8L/CYgTSyd56LYwEaCgnucyYgeID0wiYgdQ=; b=phzYohzfXo8dY5k2Ddzju0rVt4wpzcDk1YSqXcxlCewu6dZJi5BGEfqaB8Z2Q5bI9a 3aBrFqfa549qJlfQsz0CDLRKmKxx7NO/0z1OaVqel40Lo2m43iXez7H0uyb+qLncxm2f A6mUQ0ekel5H5LKGXuw7k+vo56eP6KbWO4yX78lymocSq64knCgDVgGN8kX8b3YjdXUP ADwm5+4TLv0Lgyh8ANv6kp2kTw9AayxwS7epD2TdUCOiea+jkHlo68o12VEqg9r2EdEo bpApDgF6Q2ewfAaDh016C/M3uwTVVE1+QuEq4304E+Z8EDu9LBvLPHyfdPh0JgPNWcJS jw1g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l3si14991063otq.40.2020.01.16.19.55.31; Thu, 16 Jan 2020 19:55:42 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388259AbgAQB3v (ORCPT + 99 others); Thu, 16 Jan 2020 20:29:51 -0500 Received: from ZXSHCAS1.zhaoxin.com ([203.148.12.81]:54065 "EHLO ZXSHCAS1.zhaoxin.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1730070AbgAQB3t (ORCPT ); Thu, 16 Jan 2020 20:29:49 -0500 Received: from zxbjmbx1.zhaoxin.com (10.29.252.163) by ZXSHCAS1.zhaoxin.com (10.28.252.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1261.35; Fri, 17 Jan 2020 09:29:46 +0800 Received: from [10.32.64.11] (10.32.64.11) by zxbjmbx1.zhaoxin.com (10.29.252.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1261.35; Fri, 17 Jan 2020 09:29:39 +0800 Subject: Re: [PATCH] x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 To: Thomas Gleixner , , , , , , , , , , CC: , , , References: <1579146434-2668-1-git-send-email-TonyWWang-oc@zhaoxin.com> <87r1zzuy48.fsf@nanos.tec.linutronix.de> From: Tony W Wang-oc Message-ID: Date: Fri, 17 Jan 2020 09:29:45 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <87r1zzuy48.fsf@nanos.tec.linutronix.de> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.32.64.11] X-ClientProxiedBy: zxbjmbx1.zhaoxin.com (10.29.252.163) To zxbjmbx1.zhaoxin.com (10.29.252.163) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17/01/2020 01:09, Thomas Gleixner wrote: > Tony, > > Tony W Wang-oc 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