From: Piotr Zarycki <piotr.zarycki@gmail.com>
To: seanjc@google.com, pbonzini@redhat.com
Cc: vkuznets@redhat.com, shuah@kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: selftests: hyperv_features: test write of 1 to HV_X64_MSR_RESET
Date: Sat, 23 May 2026 13:30:19 +0200 [thread overview]
Message-ID: <ahGPQDJCT1aW7vVY@arch-piotr> (raw)
In-Reply-To: <20260523111857.195396-1-piotr.zarycki@gmail.com>
Hi,
After receiving KVM_SYSTEM_EVENT_RESET the test simply advances to the
next stage without resetting the vCPU. Is verifying
KVM_SYSTEM_EVENT_RESET is delivered sufficient?
Thanks,
Piotr
next prev parent reply other threads:[~2026-05-23 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 11:18 [PATCH] KVM: selftests: hyperv_features: test write of 1 to HV_X64_MSR_RESET Piotr Zarycki
2026-05-23 11:30 ` Piotr Zarycki [this message]
2026-05-25 12:26 ` Vitaly Kuznetsov
2026-05-27 18:10 ` 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=ahGPQDJCT1aW7vVY@arch-piotr \
--to=piotr.zarycki@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=vkuznets@redhat.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