Received: by 10.223.176.5 with SMTP id f5csp217014wra; Tue, 30 Jan 2018 10:20:59 -0800 (PST) X-Google-Smtp-Source: AH8x225AslhKTJN31BmRAtPecIjLT/DrgQfkCwKQ3WKh3tDgwWk5TG12pDmjIv900NGk4vBUI9Ir X-Received: by 10.99.116.88 with SMTP id e24mr23972328pgn.279.1517336459078; Tue, 30 Jan 2018 10:20:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517336459; cv=none; d=google.com; s=arc-20160816; b=QE8EzCFuTbzeXaoqwpqTsjGzGmo0CmR6ailQ3WYNQ7Os2JnH4L6iIFp0/rHFknoNbb A1/ldRHJTJIzzYo3yBsVO9EdUuH4bbErIsxlPttdOd5SnJ5SS4MM31tGHfeOyFye0dev vwRoiyAKJBSJozBbZIsuVODBx1WyS6jQPZeMtfPtNFPq0XLOKXvrlGiA2l8tEPyrPN6o WeAeYjhzys+oK5v3pB+HMMbE+cjmOxtQAkie2ZBZIrlhQ+8XiJFzxJuhPBL+IETd0mZE 9KUZcH2LCdTrwS+oII0rC0FcfxCSUEBUdAKmnk/OGrOyRf4n8u1TAqZSxr/en8GiDCl7 wWhg== 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=uJRN7vMmx7D3CWoPSGJshdeL3OGgLWhmGj1WQnrHGYw=; b=qWvbr3dn+46dC3jscJz9oQ7IrrxrqpH8IuKMkKz8ngsGLZFB3K80lmOil0gFiFN/xp aYNYitS4NwLuoKneodDGHdF2g6Uyc9+04wJgyA96fPrcafpRpogs42PsucSxM1yKw6/x MvFIRIX+lMf46weWFUousGHd5q/AcBMD+m1pcP14OvbYsJ5mU1wH26WTZdOFzIJe7/UH ZyAOsIMv2NIH/IrYZ3KF7hAN1x0sQueaqJ8uSDA4zRn0y31LN/qtIi1F2+EiBQuYSDJ1 YrNHZxbUwi3h9jC8SqUDB5fvtYxaZL8iX2qBt58Roigd9vk6dcykBy7AkQ+v24BTADU+ lj4g== 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 y128si1978434pfy.110.2018.01.30.10.20.44; Tue, 30 Jan 2018 10:20:59 -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 S1752062AbeA3RpY (ORCPT + 99 others); Tue, 30 Jan 2018 12:45:24 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:44957 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751668AbeA3RpX (ORCPT ); Tue, 30 Jan 2018 12:45:23 -0500 Received: from hsi-kbw-5-158-153-52.hsi19.kabel-badenwuerttemberg.de ([5.158.153.52] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1egZvS-0001ZF-60; Tue, 30 Jan 2018 18:42:30 +0100 Date: Tue, 30 Jan 2018 18:45:19 +0100 (CET) From: Thomas Gleixner To: David Woodhouse cc: Jim Mattson , Mihai Carabas , Paolo Bonzini , LKML , kvm list , =?ISO-8859-2?Q?Radim_Kr=E8m=E1=F8?= , Liran Alon , Anthony Liguori , Tom Lendacky , Borislav Petkov , the arch/x86 maintainers , Konrad Rzeszutek Wilk Subject: Re: [9/8] KVM: x86: limit MSR_IA32_SPEC_CTRL access based on CPUID availability In-Reply-To: <1517332457.18619.132.camel@infradead.org> Message-ID: References: <20180109120311.27565-10-pbonzini@redhat.com> <6dc02278-7004-1794-3705-69c8cad86be4@oracle.com> <1517332457.18619.132.camel@infradead.org> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) 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, 30 Jan 2018, David Woodhouse wrote: > On Tue, 2018-01-30 at 08:57 -0800, Jim Mattson wrote: > > It's really hard to tell which patches are being proposed for which > > repositories, but assuming that everything else is correct, I don't > > think your condition is adequate. What if the physical CPU and the > > virtual CPU both have CPUID.(EAX=7H,ECX=0):EDX[26], but only the > > physical CPU has CPUID.(EAX=7H,ECX=0):EDX[27]? If the guest has write > > access to MSR_IA32_SPEC_CTRL, it can set MSR_IA32_SPEC_CTRL[1] > > (STIBP), even though setting that bit in the guest should raise #GP. > > Everything we're talking about here is for tip/x86/pti. Which I note > has just updated to be 4.15-based, although I thought it was going to > stay on 4.14 for now. So I've updated my tree at > http://git.infradead.org/linux-retpoline.git/shortlog/refs/heads/ibpb > accordingly. Yes, we tried to stay on 4.14 base but this started to created nasty merge conflicts for no value. Merging in v4.15 turned out to resolve those issues while still serving as the feed branch for Gregs stable work. For the time being we try to make stable backporting at least for 4.14/15 as painless as possible. Thanks, tglx