From: Sean Christopherson <seanjc@google.com>
To: David Edmondson <david.edmondson@oracle.com>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
x86@kernel.org, Joerg Roedel <joro@8bytes.org>,
Ingo Molnar <mingo@redhat.com>,
kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Jim Mattson <jmattson@google.com>, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Wanpeng Li <wanpengli@tencent.com>,
David Matlack <dmatlack@google.com>
Subject: Re: [PATCH v6 1/4] KVM: x86: Clarify the kvm_run.emulation_failure structure layout
Date: Tue, 12 Oct 2021 23:45:43 +0000 [thread overview]
Message-ID: <YWYeJ9TtfRwBk/5D@google.com> (raw)
In-Reply-To: <20210920103737.2696756-2-david.edmondson@oracle.com>
On Mon, Sep 20, 2021, David Edmondson wrote:
> Until more flags for kvm_run.emulation_failure flags are defined, it
> is undetermined whether new payload elements corresponding to those
> flags will be additive or alternative. As a hint to userspace that an
> alternative is possible, wrap the current payload elements in a union.
>
> Suggested-by: Sean Christopherson <seanjc@google.com>
> Signed-off-by: David Edmondson <david.edmondson@oracle.com>
> ---
To complete the set... :-)
Reviewed-by: Sean Christopherson <seanjc@google.com>
next prev parent reply other threads:[~2021-10-12 23:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 10:37 [PATCH v6 0/4] KVM: x86: Convey the exit reason, etc. to user-space on emulation failure David Edmondson
2021-09-20 10:37 ` [PATCH v6 1/4] KVM: x86: Clarify the kvm_run.emulation_failure structure layout David Edmondson
2021-10-12 23:45 ` Sean Christopherson [this message]
2021-10-13 9:29 ` David Edmondson
2021-10-22 15:24 ` Paolo Bonzini
2021-09-20 10:37 ` [PATCH v6 2/4] KVM: x86: Get exit_reason as part of kvm_x86_ops.get_exit_info David Edmondson
2021-09-20 10:37 ` [PATCH v6 3/4] KVM: x86: On emulation failure, convey the exit reason, etc. to userspace David Edmondson
2021-09-20 10:37 ` [PATCH v6 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=YWYeJ9TtfRwBk/5D@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=david.edmondson@oracle.com \
--cc=dmatlack@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox