From: Sean Christopherson <seanjc@google.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Krish Sadhukhan <krish.sadhukhan@oracle.com>
Subject: Re: [PATCH v3] KVM/x86: Move definition of __ex to x86.h
Date: Mon, 28 Dec 2020 15:54:42 -0800 [thread overview]
Message-ID: <X+pwQrLgVcMg0x3M@google.com> (raw)
In-Reply-To: <20201221194800.46962-1-ubizjak@gmail.com>
On Mon, Dec 21, 2020, Uros Bizjak wrote:
> Merge __kvm_handle_fault_on_reboot with its sole user
> and move the definition of __ex to a common include to be
> shared between VMX and SVM.
>
> v2: Rebase to the latest kvm/queue.
>
> v3: Incorporate changes from review comments.
The v2, v3, ... vN patch history should go below the '---' so that it doesn't
need to be manually stripped when applying.
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Sean Christopherson <seanjc@google.com>
> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> Reviewed-by: Krish Sadhukhan <krish.sadhukhan@oracle.com>
> ---
vN stuff down here
> arch/x86/include/asm/kvm_host.h | 25 -------------------------
> arch/x86/kvm/svm/sev.c | 2 --
> arch/x86/kvm/svm/svm.c | 2 --
> arch/x86/kvm/vmx/vmx.c | 4 +---
> arch/x86/kvm/vmx/vmx_ops.h | 4 +---
> arch/x86/kvm/x86.h | 24 ++++++++++++++++++++++++
> 6 files changed, 26 insertions(+), 35 deletions(-)
Reviewed-by: Sean Christopherson <seanjc@google.com>
next prev parent reply other threads:[~2020-12-28 23:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 19:48 [PATCH v3] KVM/x86: Move definition of __ex to x86.h Uros Bizjak
2020-12-21 22:00 ` Krish Sadhukhan
2020-12-21 22:10 ` Uros Bizjak
2020-12-21 23:05 ` Sean Christopherson
2020-12-28 23:54 ` Sean Christopherson [this message]
2020-12-29 22:14 ` 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=X+pwQrLgVcMg0x3M@google.com \
--to=seanjc@google.com \
--cc=krish.sadhukhan@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=ubizjak@gmail.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