From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Xiaoyao Li <xiaoyao.li@intel.com>
Subject: Re: [PATCH v3 0/2] KVM: VMX: Unionize vcpu_vmx.exit_reason
Date: Tue, 21 Apr 2020 18:19:15 +0200 [thread overview]
Message-ID: <bcf9cbba-6cce-f10b-da94-232403a3f7f6@redhat.com> (raw)
In-Reply-To: <20200421075328.14458-1-sean.j.christopherson@intel.com>
On 21/04/20 09:53, Sean Christopherson wrote:
> Minor fixup patch for a mishandled conflict between the vmcs.INTR_INFO
> caching series and the union series, plus the actual unionization patch
> rebased onto kvm/queue, commit 604e8bba0dc5 ("KVM: Remove redundant ...").
>
> Sean Christopherson (2):
> KVM: nVMX: Drop a redundant call to vmx_get_intr_info()
> KVM: VMX: Convert vcpu_vmx.exit_reason to a union
>
> arch/x86/kvm/vmx/nested.c | 39 ++++++++++++++---------
> arch/x86/kvm/vmx/vmx.c | 65 ++++++++++++++++++++-------------------
> arch/x86/kvm/vmx/vmx.h | 25 ++++++++++++++-
> 3 files changed, 83 insertions(+), 46 deletions(-)
>
Thanks, I queued patch 1. I am not too enthusiastic about patch 2, but
when SGX comes around it may be a better idea.
Paolo
next prev parent reply other threads:[~2020-04-21 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 7:53 [PATCH v3 0/2] KVM: VMX: Unionize vcpu_vmx.exit_reason Sean Christopherson
2020-04-21 7:53 ` [PATCH v3 1/2] KVM: nVMX: Drop a redundant call to vmx_get_intr_info() Sean Christopherson
2020-04-21 7:53 ` [PATCH v3 2/2] KVM: VMX: Convert vcpu_vmx.exit_reason to a union Sean Christopherson
2020-04-21 16:19 ` Paolo Bonzini [this message]
2020-04-21 17:01 ` [PATCH v3 0/2] KVM: VMX: Unionize vcpu_vmx.exit_reason Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bcf9cbba-6cce-f10b-da94-232403a3f7f6@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=xiaoyao.li@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).