From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: kvm list <kvm@vger.kernel.org>
Cc: "Sean Christopherson" <sean.j.christopherson@intel.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Joerg Roedel" <joro@8bytes.org>, "Jon Doron" <arilou@gmail.com>,
"Liran Alon" <liran.alon@oracle.com>,
"Jim Mattson" <jmattson@google.com>
Subject: Re: [PATCH] KVM: x86: nVMX: allow RSM to restore VMXE CR4 flag
Date: Tue, 09 Apr 2019 10:21:16 +0200 [thread overview]
Message-ID: <871s2bio77.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <CALMp9eQPwFy5GvjDbE9wQQYEDdYfHzEwm6n1XZgQ_hCuk9vp+Q@mail.gmail.com>
Jim Mattson <jmattson@google.com> writes:
> On Thu, Mar 28, 2019 at 1:56 AM Vitaly Kuznetsov <vkuznets@redhat.com> wrote:
>
>> P.S. We probably need a kvm-unit-tests or selftests test as
>> Hyper-V+secureboot is the only known way to test this atm.
>
> Yes, please! And the requirement for providing tests of new features
> should be applied universally, rather than ad hoc.
FWIW, I have a working proof-of-concept test for KVM selftests doing
SMI/RSM. I'm going to clean it up, enhance a bit, maybe add something to
state_test and send out (unless someone beats me up to it, of course :-)
--
Vitaly
next prev parent reply other threads:[~2019-04-09 8:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 13:07 [PATCH] KVM: x86: nVMX: allow RSM to restore VMXE CR4 flag Vitaly Kuznetsov
2019-03-26 13:11 ` Liran Alon
2019-03-26 13:48 ` Vitaly Kuznetsov
2019-03-26 15:02 ` Liran Alon
2019-03-27 10:08 ` Vitaly Kuznetsov
[not found] ` <20190327192946.19128-1-sean.j.christopherson@intel.com>
[not found] ` <87va03ml7n.fsf@vitty.brq.redhat.com>
[not found] ` <CALMp9eQPwFy5GvjDbE9wQQYEDdYfHzEwm6n1XZgQ_hCuk9vp+Q@mail.gmail.com>
2019-04-09 8:21 ` Vitaly Kuznetsov [this message]
2019-04-09 16:31 ` Paolo Bonzini
2019-04-10 9:38 ` [RFC] selftests: kvm: add a selftest for SMM Vitaly Kuznetsov
2019-04-10 10:10 ` Paolo Bonzini
2019-04-10 10:32 ` Vitaly Kuznetsov
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=871s2bio77.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=arilou@gmail.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@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 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.