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
Subject: Re: [PATCH] KVM: VMX: Use accessor to read vmcs.INTR_INFO when handling exception
Date: Mon, 27 Apr 2020 21:09:40 +0200 [thread overview]
Message-ID: <3bad600c-71e6-c094-59a4-f82144adddb4@redhat.com> (raw)
In-Reply-To: <20200427173241.GJ14870@linux.intel.com>
On 27/04/20 19:32, Sean Christopherson wrote:
> No, I missed this case in the original patch, and the other fix was for
> incorrect sizing of an exit_qual variable.
Nevermind, I applied it twice and I got an "Already applied" message on
the second invocation.
next prev parent reply other threads:[~2020-04-27 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 17:18 [PATCH] KVM: VMX: Use accessor to read vmcs.INTR_INFO when handling exception Sean Christopherson
2020-04-27 17:28 ` Paolo Bonzini
2020-04-27 17:32 ` Sean Christopherson
2020-04-27 19:09 ` Paolo Bonzini [this message]
2020-04-27 17:31 ` 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=3bad600c-71e6-c094-59a4-f82144adddb4@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 \
/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).