From: Sean Christopherson <seanjc@google.com>
To: David Edmondson <dme@dme.org>
Cc: linux-kernel@vger.kernel.org, Wanpeng Li <wanpengli@tencent.com>,
Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
David Matlack <dmatlack@google.com>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jim Mattson <jmattson@google.com>,
David Edmondson <david.edmondson@oracle.com>
Subject: Re: [PATCH v5 2/4] KVM: x86: Get exit_reason as part of kvm_x86_ops.get_exit_info
Date: Thu, 16 Sep 2021 16:23:53 +0000 [thread overview]
Message-ID: <YUNvmbtmgRkhLguj@google.com> (raw)
In-Reply-To: <20210916083239.2168281-3-david.edmondson@oracle.com>
On Thu, Sep 16, 2021, David Edmondson wrote:
> Extend the get_exit_info static call to provide the reason for the VM
> exit. Modify relevant trace points to use this rather than extracting
> the reason in the caller.
>
> Signed-off-by: David Edmondson <david.edmondson@oracle.com>
> ---
With the From: / Author thing fixed,
Reviewed-by: Sean Christopherson <seanjc@google.com>
next prev parent reply other threads:[~2021-09-16 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 8:32 [PATCH v5 0/4] KVM: x86: Convey the exit reason, etc. to user-space on emulation failure David Edmondson
2021-09-16 8:32 ` [PATCH v5 1/4] KVM: x86: Clarify the kvm_run.emulation_failure structure layout David Edmondson
2021-09-16 16:20 ` Sean Christopherson
2021-09-16 17:52 ` Borislav Petkov
2021-09-16 8:32 ` [PATCH v5 2/4] KVM: x86: Get exit_reason as part of kvm_x86_ops.get_exit_info David Edmondson
2021-09-16 16:23 ` Sean Christopherson [this message]
2021-09-16 8:32 ` [PATCH v5 3/4] KVM: x86: On emulation failure, convey the exit reason, etc. to userspace David Edmondson
2021-09-16 16:33 ` Sean Christopherson
2021-09-16 8:32 ` [PATCH v5 4/4] KVM: x86: SGX must obey the KVM_INTERNAL_ERROR_EMULATION protocol David Edmondson
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=YUNvmbtmgRkhLguj@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=david.edmondson@oracle.com \
--cc=dmatlack@google.com \
--cc=dme@dme.org \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.