Received: by 10.223.176.46 with SMTP id f43csp1927738wra; Sun, 21 Jan 2018 07:27:41 -0800 (PST) X-Google-Smtp-Source: AH8x226OAOtWqsJ/lRL6QYQjSBW5rp5TMyCrKOdqBT4IlgnBvbTDEI8PxcePnjf/8qK2iEjkOsMq X-Received: by 2002:a17:902:7c95:: with SMTP id y21-v6mr2140893pll.70.1516548461114; Sun, 21 Jan 2018 07:27:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516548461; cv=none; d=google.com; s=arc-20160816; b=Yepelej9stXoCNnt6FijawPOktChNOKeFTIpH0lor0rfj8HeHnQF4p/05yWwa29WsJ hwkFqX8mj5vFnKCjR0PQYg8uxYB65cL6tOFKl556k6CdcwX0PE0f8/2qxMsM3eYrKrvk Xqx0PLSPMKZdS0/UKcVYhx6CHDlE4urt4YFgRjz7osLgkmeh7tvkxrKbbJY7vjN7TfaC uGc0H3NzkqlKsu329Y1m8FoEw/Ssb06zvwA5YLrGplJora6nPR0QMexAA4ydNWsh/go0 1Nl83lMW/dBHrYuxgR8RQrJQrK8kXFUDfcZt/g0GaGKAEH9sZFQnR8yw952jtjExxxri y/BQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:importance:content-transfer-encoding :mime-version:user-agent:cc:to:from:subject:date:references :in-reply-to:message-id:dkim-signature:arc-authentication-results; bh=03C3BrUxoPRvLCl54B6qXQe7ePQ5H5QQ7clqxC5nn0M=; b=qoFaldrgHIp715pGyZnraPtlHkwgGt2PsaWYw2d2FcuyA+OenKHT1hwyDF6VRQ5j31 1GgPKUL0jR02gSdrmE/3hzyXPzT9A9nMtibMe2mnjH+WLNSBPZxVijSNfAGD4PCUlSSR Kz7Z3yUjwJBUenv4LJ48SQCaWlooXURbWaYr9hQ3bxQSwml5o3lyIWrgTLM/oOBk/ASi kuYS1JUXGKp5nZuk8jluHSXfciA0tcLoURlX3egtnlsWV+RIm5D0Z1fj7iubZQJV93WB t3b+0THBIrCNaNXn+I94iaAiaGTbWnXICe2BTOCeFcMQKApWxTvk5PUjnGamK1vgBq/7 0KBQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=twosheds.20170209 header.b=LRNQGdzR; 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 5-v6si2619726plt.284.2018.01.21.07.26.49; Sun, 21 Jan 2018 07:27:41 -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; dkim=fail header.i=@infradead.org header.s=twosheds.20170209 header.b=LRNQGdzR; 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 S1750933AbeAUPZy (ORCPT + 99 others); Sun, 21 Jan 2018 10:25:54 -0500 Received: from twosheds.infradead.org ([90.155.92.209]:56008 "EHLO twosheds.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750748AbeAUPZx (ORCPT ); Sun, 21 Jan 2018 10:25:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=twosheds.20170209; h=Content-Transfer-Encoding: Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To: Message-ID:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=03C3BrUxoPRvLCl54B6qXQe7ePQ5H5QQ7clqxC5nn0M=; b=LRNQGdzRl+VUqWX2gGlGZOonu jlOeJLqu23xwKhHyzWHgg6tVVaYvUiSWWxaiaandmPIy3slEI1KAS9lpF7IHg1njM81HFll+M3ucj SpvmjBlIsJjlcF3u8L5iVHlKsRVhmbTs4H/gb52irgac4zcEzLZuuLV10D3OuCOliqUORGRmi2jGJ ZT9vABOPrmV78RzNgafjlXOkfuETVrTbWVAa0M8bXcXH4sgil1XPbH5fba0VkloXsSad/Q3U81yNz ejNvHaMlRtDa32+LsyQOYveZ++y1gGyP4IyPFMlEtc3h2jXJxkpHiZ8nOQZZD2MwVwSocXFisoOA3 DokQbzw2g==; Received: from localhost ([127.0.0.1] helo=twosheds.infradead.org) by twosheds.infradead.org with esmtp (Exim 4.89 #1 (Red Hat Linux)) id 1edHV3-0003Qc-JC; Sun, 21 Jan 2018 15:25:38 +0000 Received: from 86.142.97.146 (SquirrelMail authenticated user dwmw2) by twosheds.infradead.org with HTTP; Sun, 21 Jan 2018 15:25:38 -0000 Message-ID: <37cf9ba3941a51e8db27f9f4c21b5b7e.squirrel@twosheds.infradead.org> In-Reply-To: References: <1516476182-5153-1-git-send-email-karahmed@amazon.de> <1516476182-5153-6-git-send-email-karahmed@amazon.de> Date: Sun, 21 Jan 2018 15:25:38 -0000 Subject: Re: [RFC 05/10] x86/speculation: Add basic IBRS support infrastructure From: "David Woodhouse" To: "Thomas Gleixner" Cc: "KarimAllah Ahmed" , linux-kernel@vger.kernel.org, "Andi Kleen" , "Andrea Arcangeli" , "Andy Lutomirski" , "Arjan van de Ven" , "Ashok Raj" , "Asit Mallick" , "Borislav Petkov" , "Dan Williams" , "Dave Hansen" , "David Woodhouse" , "Greg Kroah-Hartman" , "H . Peter Anvin" , "Ingo Molnar" , "Janakarajan Natarajan" , "Joerg Roedel" , "Jun Nakajima" , "Laura Abbott" , "Linus Torvalds" , "Masami Hiramatsu" , "Paolo Bonzini" , "Peter Zijlstra" , =?utf-8?B?IlJhZGltIEtyxI1tw6HFmSI=?= , "Tim Chen" , "Tom Lendacky" , kvm@vger.kernel.org, x86@kernel.org User-Agent: SquirrelMail/1.4.22-21.fc27 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-SRS-Rewrite: SMTP reverse-path rewritten from by twosheds.infradead.org. See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Sat, 20 Jan 2018, KarimAllah Ahmed wrote: >> From: David Woodhouse >> >> Not functional yet; just add the handling for it in the Spectre v2 >> mitigation selection, and the X86_FEATURE_IBRS flag which will control >> the code to be added in later patches. >> >> Also take the #ifdef CONFIG_RETPOLINE from around the RSB-stuffing; IBRS >> mode will want that too. >> >> For now we are auto-selecting IBRS on Skylake. We will probably end up >> changing that but for now let's default to the safest option. >> >> XX: Do we want a microcode blacklist? > > Oh yes, we want a microcode blacklist. Ideally we refuse to load the > affected microcode in the first place and if its already loaded then at > least avoid to use the borked features. > > PR texts promising that Intel is committed to transparency in this matter > are not sufficient. Intel, please provide the facts, i.e. a proper list of > micro codes and affected SKUs, ASAP. Perhaps we could start with the list already published by VMware at https://kb.vmware.com/s/article/52345 -- dwmw2