From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 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: Sender: stable-owner@vger.kernel.org List-ID: 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) --