From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] KVM: selftests: Introduce vcpu_arch_put_guest()
Date: Mon, 29 Apr 2024 13:45:23 -0700 [thread overview]
Message-ID: <171442342393.161664.6093030957550923677.b4-ty@google.com> (raw)
In-Reply-To: <20240314185459.2439072-1-seanjc@google.com>
On Thu, 14 Mar 2024 11:54:53 -0700, Sean Christopherson wrote:
> The end goal of this series is to add a regression test for commit
> 910c57dfa4d1 ("KVM: x86: Mark target gfn of emulated atomic instruction
> as dirty"), *without* polluting the common dirty_log_test.c code with
> gory x86 details.
>
> The regression test requires forcing KVM to emulate a guest atomic RMW
> access, which is done via a magic instruction prefix/opcode that is
> guarded by an off-by-default KVM module param.
>
> [...]
Applied to kvm-x86 selftests_utils, thanks!
[1/5] KVM: selftests: Provide a global pseudo-RNG instance for all tests
https://github.com/kvm-x86/linux/commit/cb6c6914788f
[2/5] KVM: selftests: Provide an API for getting a random bool from an RNG
https://github.com/kvm-x86/linux/commit/73369acd9fbd
[3/5] KVM: selftests: Add global snapshot of kvm_is_forced_emulation_enabled()
https://github.com/kvm-x86/linux/commit/e1ff11525d3c
[4/5] KVM: selftests: Add vcpu_arch_put_guest() to do writes from guest code
https://github.com/kvm-x86/linux/commit/2f2bc6af6aa8
[5/5] KVM: selftests: Randomly force emulation on x86 writes from guest code
https://github.com/kvm-x86/linux/commit/87aa264cd89d
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2024-04-29 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 18:54 [PATCH 0/5] KVM: selftests: Introduce vcpu_arch_put_guest() Sean Christopherson
2024-03-14 18:54 ` [PATCH 1/5] KVM: selftests: Provide a global pseudo-RNG instance for all tests Sean Christopherson
2024-03-14 18:54 ` [PATCH 2/5] KVM: selftests: Provide an API for getting a random bool from an RNG Sean Christopherson
2024-03-14 18:54 ` [PATCH 3/5] KVM: selftests: Add global snapshot of kvm_is_forced_emulation_enabled() Sean Christopherson
2024-03-14 18:54 ` [PATCH 4/5] KVM: selftests: Add vcpu_arch_put_guest() to do writes from guest code Sean Christopherson
2024-03-14 18:54 ` [PATCH 5/5] KVM: selftests: Randomly force emulation on x86 " Sean Christopherson
2024-04-29 20:45 ` Sean Christopherson [this message]
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=171442342393.161664.6093030957550923677.b4-ty@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).