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;
Date:   Fri, 21 Sep 2018 18:25:45 +0200
From:   Greg KH <gregkh@linux-foundation.org>
To:     Paolo Bonzini <pbonzini@redhat.com>
Cc:     linux-kernel@vger.kernel.org, rkrcmar@redhat.com,
        kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM changes for Linux 4.19-rc5
Message-ID: <20180921162544.GA32325@kroah.com>
References: <1537538766-8252-1-git-send-email-pbonzini@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1537538766-8252-1-git-send-email-pbonzini@redhat.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Sep 21, 2018 at 04:06:06PM +0200, Paolo Bonzini wrote:
> Greg,
> 
> The following changes since commit 7876320f88802b22d4e2daf7eb027dd14175a0f8:
> 
>   Linux 4.19-rc4 (2018-09-16 11:52:37 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
> 
> for you to fetch changes up to 26b471c7e2f7befd0f59c35b257749ca57e0ed70:
> 
>   KVM: nVMX: Fix bad cleanup on error of get/set nested state IOCTLs (2018-09-20 18:54:08 +0200)
> 
> ----------------------------------------------------------------
> This pull request is slightly bigger than usual at this stage, but
> I swear I would have sent it the same to Linus!  The main cause for
> this is that I was on vacation until two weeks ago and it took a while
> to sort all the pending patches between 4.19 and 4.20, test them and
> so on.
> 
> It's mostly small bugfixes and cleanups, mostly around x86 nested
> virtualization.  One important change, not related to nested
> virtualization, is that the ability for the guest kernel to trap CPUID
> instructions (in Linux that's the ARCH_SET_CPUID arch_prctl) is now
> masked by default.  This is because the feature is detected through an
> MSR; a very bad idea that Intel seems to like more and more.  Some
> applications choke if the other fields of that MSR are not initialized
> as on real hardware, hence we have to disable the whole MSR by default,
> as was the case before Linux 4.12.

Now pulled, thanks.

greg k-h