Received: by 10.223.185.116 with SMTP id b49csp3809387wrg; Tue, 13 Feb 2018 08:05:39 -0800 (PST) X-Google-Smtp-Source: AH8x2249SoNrldT/vEl/udWJ0LyE92TWyQJw0/V3aPJevqyC8zzbfWBXbi0LaJNEECkez9EK95Hj X-Received: by 10.98.138.129 with SMTP id o1mr1732585pfk.182.1518537939425; Tue, 13 Feb 2018 08:05:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518537939; cv=none; d=google.com; s=arc-20160816; b=dGIys0mdJpLOidzEDjmMaVO0TI1DeqCwmmt7jUDq0S6djnoiWLFVbrWs+aOuamc4aL 3O7jumxPgiNiAO9dFygkrROlcLVuTSts70KS4Urs9cLTHl65TEY1MVL3d2QCoR0mXEkn C3o+kpGjRjzHUupIv6NIMFE84Dj+zb6vsqxWqfu20yPX0yjcARaxQM7Szr83zTJGFfZf QMpiCpjFg8sVie/lnpJTkik7W91jcHCWrw+K71yVKhzlFAHlF8yxscW3viBYfABHzPyd +EN1GuxsP7PLqVLRJBFQcSWEOnZkAnGJfVQCGfPpKyvVJl9UKiqLC5ZP4+yZMJnSaaIv H0qg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=rYhJzo8S238S7gekwyfmHKqlqVBgnC1atyCz/zYzc24=; b=E7c5xf8PPIP/H7yiGNNah204oJYvsYrIs0h1DjrZTvWSg10Zb1zWXpJ91aXHEEuKRA VPzHVJnFSyYRIllzXYLK7f1LVhvNBsjFb3k4pwsfuUkvR0gnj+fG9hkIkZ260EWE0JZq f0jfg3PN1+NV8cmVF+wPj5UCrve/GF2CEsvzKPuQkk/zub2CvBsCxcHJF41v7nGtwzf0 K7tKf2ZURqhGxg0WdE1Hnxwdzpq9Sekb8CxpjZ7l636I/MkdczD7jFUmAoO1jSptPMqc ljl/eId1J/dzDU173YVeCLk+AEnAvb4y2QJyZtR6ek6iwz2axx7fY8HcN2PxiKPPevtd w1Ww== 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 p1-v6si5914056plb.479.2018.02.13.08.05.24; Tue, 13 Feb 2018 08:05:39 -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 S934623AbeBMQC4 (ORCPT + 99 others); Tue, 13 Feb 2018 11:02:56 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:50909 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933927AbeBMQCy (ORCPT ); Tue, 13 Feb 2018 11:02:54 -0500 Received: from hsi-kbw-5-158-153-52.hsi19.kabel-badenwuerttemberg.de ([5.158.153.52] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1elcza-0004jv-LE; Tue, 13 Feb 2018 16:59:38 +0100 Date: Tue, 13 Feb 2018 17:02:59 +0100 (CET) From: Thomas Gleixner To: Andi Kleen cc: Arjan van de Ven , Greg Kroah-Hartman , Nick Lowe , linux-kernel@vger.kernel.org, stable@vger.kernel.org, David Woodhouse , Borislav Petkov , Dave Hansen , gnomes@lxorguk.ukuu.org.uk, ashok.raj@intel.com, karahmed@amazon.de, torvalds@linux-foundation.org, peterz@infradead.org, Borislav Petkov , pbonzini@redhat.com, tim.c.chen@linux.intel.com Subject: Re: [PATCH 4.9 43/92] x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown In-Reply-To: <20180213155603.GK10945@tassilo.jf.intel.com> Message-ID: References: <20180209133931.211869118@linuxfoundation.org> <20180209133934.259299920@linuxfoundation.org> <20180213150007.GJ26982@kroah.com> <20180213155603.GK10945@tassilo.jf.intel.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 13 Feb 2018, Andi Kleen wrote: > On Tue, Feb 13, 2018 at 07:09:44AM -0800, Arjan van de Ven wrote: > > > > > > So, any hints on what you think should be the correct fix here? > > > > the patch sure looks correct to me, it now has a nice table for CPU IDs > > including all of AMD (and soon hopefully the existing Intel ones that are not exposed to meltdown) > > I don't think the table is nice, it's a white list that would need > to be maintained forever. No. The table is basically excluding families <=5 and a few individual ones. Anything newer than that should tell via ARCH_CAP_RDCL_NO and not need any entry. Thanks, tglx