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,
Yosry Ahmed <yosry.ahmed@linux.dev>
Subject: Re: [PATCH v5] KVM: selftests: Test READ=>WRITE dirty logging behavior for shadow MMU
Date: Tue, 3 Feb 2026 16:10:25 -0800 [thread overview]
Message-ID: <177016376262.575354.15783428739984459015.b4-ty@google.com> (raw)
In-Reply-To: <20260115172154.709024-1-seanjc@google.com>
On Thu, 15 Jan 2026 09:21:54 -0800, Sean Christopherson wrote:
> Update the nested dirty log test to validate KVM's handling of READ faults
> when dirty logging is enabled. Specifically, set the Dirty bit in the
> guest PTEs used to map L2 GPAs, so that KVM will create writable SPTEs
> when handling L2 read faults. When handling read faults in the shadow MMU,
> KVM opportunistically creates a writable SPTE if the mapping can be
> writable *and* the gPTE is dirty (or doesn't support the Dirty bit), i.e.
> if KVM doesn't need to intercept writes in order to emulate Dirty-bit
> updates.
>
> [...]
Applied to kvm-x86 selftests, without the duplicate sync (hopefully). Thanks
for the reviews!
[1/1] KVM: selftests: Test READ=>WRITE dirty logging behavior for shadow MMU
https://github.com/kvm-x86/linux/commit/a91cc4824660
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2026-02-04 0:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 17:21 Sean Christopherson
2026-01-15 22:21 ` Yosry Ahmed
2026-01-15 23:46 ` Sean Christopherson
2026-02-04 0:10 ` 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=177016376262.575354.15783428739984459015.b4-ty@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=yosry.ahmed@linux.dev \
/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
all inboxes | Powered by JetHome®