Received: by 10.223.176.5 with SMTP id f5csp1268838wra; Fri, 2 Feb 2018 14:20:58 -0800 (PST) X-Google-Smtp-Source: AH8x227xs8WdTYbQyr9an44MgcjoSnCrtyuufAuQGLePDac9eHkO2P/v2bJFIHTCRNIqjLkbj57w X-Received: by 10.98.27.208 with SMTP id b199mr2385129pfb.166.1517610058296; Fri, 02 Feb 2018 14:20:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517610058; cv=none; d=google.com; s=arc-20160816; b=xqsezSHLNaHJC9PJNuuO9buoVv4TG55/7eLjl36F7m2N4Oj2nRJtbnRHJ3Q31NZK3q CiujHCGDgifu0WceI/+6d6sDNllOWtf5c82BuuwDDD8lB3F3nYFFO6ILqnImuNo5TCAa f+R4s6UzzQW68zOZm1QzN5bshCam1mDJsTJ0TQkpt36sAQwMlKdDIbddNSS5fs3gSLr6 pssZFs2nqUHCrycfMZavezmDqalvGr1bxZdlANwyjXQJ8xgjEdRPYwPh0EbwWcUFdLNx NyY8lVILEh8jESH7n0MwPPvkmhfKJaCCelXoWRyMdLYZINrndLy1VGcoE64eJ214Bxoz 89LA== 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:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:arc-authentication-results; bh=waAsJN1P4brNpZ44IBloX9p5NhK+kS8d9aLA0E+SGy0=; b=xoxDAiDQglCVddeIttQy4HFRltwI+MR+OnnAxDbRbfMtQvWBR1W0cp31ng3VffRmUX AV3sqMou4bzMCvClFSTajNvGCz/kIfN3yfAlhGprq8wX5XShG0o9XzeK1L8zLHvFSvqR uLdO361s2Bs8xVHguxDAqkh/cesSyroq57KsMAEbFu2PKqJOXKYYl/wTJlf89j8fxpYo 3Owf8pwTs7E4NQPb5Ilm93G2HZUsBEOEaxrF3XG9csW097QbLW7eF/bXSU+K6akYJO+T 6vdT/anWG1Shpp8Siu9PwbJA8Ocb4sg88fHZvzfadQ2HdpiWX3lqPLhpoqIfJBscN15R sccg== 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 w15si2016113pgm.407.2018.02.02.14.20.42; Fri, 02 Feb 2018 14:20:57 -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 S1752721AbeBBUxz (ORCPT + 99 others); Fri, 2 Feb 2018 15:53:55 -0500 Received: from www.llwyncelyn.cymru ([82.70.14.225]:36914 "EHLO fuzix.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752690AbeBBUxt (ORCPT ); Fri, 2 Feb 2018 15:53:49 -0500 Received: from alans-desktop (82-70-14-226.dsl.in-addr.zen.co.uk [82.70.14.226]) by fuzix.org (8.15.2/8.15.2) with ESMTP id w12Kqxvt028102; Fri, 2 Feb 2018 20:52:59 GMT Date: Fri, 2 Feb 2018 20:52:58 +0000 From: Alan Cox To: Konrad Rzeszutek Wilk Cc: David Woodhouse , KarimAllah Ahmed , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org, Ashok Raj , Asit Mallick , Dave Hansen , Arjan Van De Ven , Tim Chen , Linus Torvalds , Andrea Arcangeli , Andi Kleen , Thomas Gleixner , Dan Williams , Jun Nakajima , Andy Lutomirski , Greg KH , Paolo Bonzini , Peter Zijlstra Subject: Re: [PATCH v6 2/5] KVM: x86: Add IBPB support Message-ID: <20180202205258.2819b14f@alans-desktop> In-Reply-To: <20180202202857.GI28192@char.us.oracle.com> References: <1517522386-18410-1-git-send-email-karahmed@amazon.de> <1517522386-18410-3-git-send-email-karahmed@amazon.de> <20180202174932.GR28192@char.us.oracle.com> <1517594544.31953.62.camel@infradead.org> <20180202195601.GD28192@char.us.oracle.com> <1517602575.31953.74.camel@infradead.org> <20180202202857.GI28192@char.us.oracle.com> Organization: Intel Corporation X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > No. The AMD feature bits give us more fine-grained support for exposing > > IBPB or IBRS alone, so we expose those bits on Intel too. > > But but.. that runs smack against the idea of exposing a platform that > is as close to emulating the real hardware as possible. Agreed, and it's asking for problems in the future if for example Intel or another non AMD vendor did ever use that leaf for something different. Now whether there ought to be an MSR range every vendor agrees is never implemented so software can use it is an interesting discussion. Alan