Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp1144005ybp; Wed, 9 Oct 2019 09:24:13 -0700 (PDT) X-Google-Smtp-Source: APXvYqzckbuFIV55Ro5u3av9Mg4ZUOAXZph7ppsGjw1yHMlRwe2mpuCJj1PUjxoF6nucIeiBgwQz X-Received: by 2002:a17:906:52d0:: with SMTP id w16mr3682923ejn.206.1570638253503; Wed, 09 Oct 2019 09:24:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570638253; cv=none; d=google.com; s=arc-20160816; b=xdX753ALhdJrHRAU/B3Kow1Y9o6359xvfnee/1l/GNuCEmOsrf+rajjtX/1hw++ii2 PlmBv3RSFaadRTEAyVY0aikBofeO3x+3GBWnWNivlzqlC2S+qNub0jcHp9PqLAI5VyqU aFFgkMifFpBgEd3o5xvxRsBa3Xo4SUSO71zNBUb1D2OlbikYJsqDR3xzk0OJown1J6xz XMAuvcDWPq3UIJsl8aGObv8nX17YLuJSFoFXYRxwjpWxZAk2Y0GJHYPhFWA3tMhP5vmN TDRdDazQ6uGVlGlYa90K7ySI9lIyDA79NO22Z8OxhOWBCVuonYSZN/0GaxXsKUxL7+SV AsPA== 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-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=wn1D2w8oF5+nCZQuyo14y5xDhJLrLnOzpCSNo1ilhWo=; b=d1zq2/Y1nzOT/9Y2qG6HZN7cJA1Cf37aNpGO0FfNVQw3h89z5UmUyhvqvLVMmsswH0 JZVicbC1aftXruuvHZSP/84/VXXk3FgQTZQXUJe5Im9i2wuA0TKihwpbT3pV25QHJdac Cc3QIYmWQhqGGHbXiTdqZZWmtc70l0Tw9jCcqbPXAvkmldhcvnuD4U8QAoN2muhwgCLz RBhwu5Qgf/we/mPcD9zShIocWWxxr/EKazuBbfuK8jLKs/RWJiaPyAxqmukYrKFeY7ab P3n4C2gEItLrnvycm1YAkEFFOK9SNMmunuaQOmJz5hU07Y7i+jJOQN8d/LDMROfFKneh TdDQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id rk14si1442343ejb.24.2019.10.09.09.23.49; Wed, 09 Oct 2019 09:24:13 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731817AbfJIQWd (ORCPT + 99 others); Wed, 9 Oct 2019 12:22:33 -0400 Received: from mga01.intel.com ([192.55.52.88]:17049 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731478AbfJIQWc (ORCPT ); Wed, 9 Oct 2019 12:22:32 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Oct 2019 09:22:31 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.67,276,1566889200"; d="scan'208";a="198055825" Received: from sjchrist-coffee.jf.intel.com (HELO linux.intel.com) ([10.54.74.41]) by orsmga006.jf.intel.com with ESMTP; 09 Oct 2019 09:22:31 -0700 Date: Wed, 9 Oct 2019 09:22:31 -0700 From: Sean Christopherson To: Paolo Bonzini Cc: Vitaly Kuznetsov , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Jim Mattson Subject: Re: [PATCH] selftests: kvm: fix sync_regs_test with newer gccs Message-ID: <20191009162230.GA31986@linux.intel.com> References: <20191008180808.14181-1-vkuznets@redhat.com> <20191008183634.GF14020@linux.intel.com> <87d0f6yzd3.fsf@vitty.brq.redhat.com> <5b1b95e5-4836-ab55-fe4d-e9cc78a7a95e@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5b1b95e5-4836-ab55-fe4d-e9cc78a7a95e@redhat.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 09, 2019 at 01:11:24PM +0200, Paolo Bonzini wrote: > On 09/10/19 12:42, Vitaly Kuznetsov wrote: > > Paolo Bonzini writes: > >> There is no practical difference with Vitaly's patch. The first > >> _vcpu_run has no pre-/post-conditions on the value of %rbx: > > > > I think what Sean was suggesting is to prevent GCC from inserting > > anything (and thus clobbering RBX) between the call to guest_call() and > > the beginning of 'asm volatile' block by calling *inside* 'asm volatile' > > block instead. > > Yes, but there is no way that clobbering RBX will break the test, > because RBX is not initialized until after the first _vcpu_run succeeds. Ah, nice, wasn't aware of that.