Received: by 10.223.185.116 with SMTP id b49csp3819038wrg; Tue, 13 Feb 2018 08:13:26 -0800 (PST) X-Google-Smtp-Source: AH8x225F6CiKBd4LtuhK2dsmWVri+pZbLXNekbpDmcKjqzVcH/fJ/vZtsbIFSjp6cnfF6Y138m+i X-Received: by 2002:a17:902:b417:: with SMTP id x23-v6mr1583205plr.339.1518538406066; Tue, 13 Feb 2018 08:13:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518538406; cv=none; d=google.com; s=arc-20160816; b=gvM61McU6sU4SwiDzzDRNYRm1GQe8loU+yKLaYtzb41nFub8W/lPBgvdMSGPkO0OJy pZPG8TdvKD/Fi6q3B+4pDrZDQ8YDPGTHHviUaYXFX3A+RrF2IIudi8Ai0M1zUVVBnp/b 2L1+3k50usNOIQ45WJgsZXoK1DeyNXODCTc/wHIV0eta6o4FVlZ30e5MS3nZdu47dtR1 vqzbgC0NF794sOXAsV0eZ+wV55qNd8SiHoZiVDZWiNmqossiN3SkkxwCArYoSjeRWuRw LgltGbAwTDeL2qMBXN2k1ijczsARaQxjsy2OvWqTb35V4u5nyMWgYVHtazSjWtGiMDqP 7PZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=USE8wB5LRW9g1aLJ5yE6B1UEOZYYjzpl8ABd75AiRww=; b=nYxmEGuJwy32bQCOxrjbhNTOWfnjpknTSClSrBxxOzfA8zjG4C3NJp0bmg11DXjPWf 1h88nGqMQ6oYTUHZhdqDvMSczbnAqLnGqDKZM/HV9f2Du7rQFveJtv8zdwU2C3CUuiiG +45ZACt7YePcA87zZ7xEEVS744XdY4sveMo1LvoRnz5sTysNuxwNfqw2/Dm7O6OIdI17 bUqe/r1hAA8Dtz0EYub/ZQrO5/bN2whv3lw8QdEg7XkwZgtpWEc+PXubBMTnU3U3tXBj +QFhKBEim6Qh/Wd5SSkhrHvGLMT0D5hrCUuyCl4pGtkByb+7VoxEp+fb/Is5n2pZx1oB WsJQ== 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 n10-v6si1123146plp.698.2018.02.13.08.13.11; Tue, 13 Feb 2018 08:13:26 -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 S934615AbeBMQL2 (ORCPT + 99 others); Tue, 13 Feb 2018 11:11:28 -0500 Received: from mx2.suse.de ([195.135.220.15]:37875 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934405AbeBMQL1 (ORCPT ); Tue, 13 Feb 2018 11:11:27 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id BDF41AF5B; Tue, 13 Feb 2018 16:11:25 +0000 (UTC) Date: Tue, 13 Feb 2018 17:10:55 +0100 From: Borislav Petkov To: Thomas Gleixner Cc: Andi Kleen , Arjan van de Ven , Greg Kroah-Hartman , Nick Lowe , linux-kernel@vger.kernel.org, stable@vger.kernel.org, David Woodhouse , Dave Hansen , gnomes@lxorguk.ukuu.org.uk, ashok.raj@intel.com, karahmed@amazon.de, torvalds@linux-foundation.org, peterz@infradead.org, 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 Message-ID: <20180213161055.GD12578@pd.tnic> References: <20180209133931.211869118@linuxfoundation.org> <20180209133934.259299920@linuxfoundation.org> <20180213150007.GJ26982@kroah.com> <20180213155603.GK10945@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 13, 2018 at 05:02:59PM +0100, Thomas Gleixner wrote: > 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. It looks to me like Nick wants 4.9 to test X86_BUG_CPU_MELTDOWN in kaiser_check_boottime_disable() not X86_VENDOR_AMD. I.e., the auto disable should pay attention to the CPUs in the table like upstream. 4.9 got the kaiser backports which explains the difference. IMHO, of course. -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --