The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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,
	 Wu Fei <wu.fei9@sanechips.com.cn>, Wu Fei <atwufei@163.com>
Subject: Re: [PATCH] KVM: selftests: Randomize dirty_log_test's delay before reaping the bitmap
Date: Wed, 27 May 2026 11:10:18 -0700	[thread overview]
Message-ID: <177990523920.4120987.9255714954792808956.b4-ty@google.com> (raw)
In-Reply-To: <20260522170230.3518669-1-seanjc@google.com>

On Fri, 22 May 2026 10:02:30 -0700, Sean Christopherson wrote:
> In the dirty log test, randomize the delay before the initial call to get
> the dirty log bitmap for a given iteration, so that the amount of memory
> dirtied by the guest varies from iteration to iteration, and so that the
> user can effectively control the duration (by increasing the interval).
> 
> Always waiting 1ms effectively hides a KVM RISC-V bug as the test reaps the
> dirty bitmap before the guest has a chance to trigger the problematic flow
> in KVM.
> 
> [...]

Applied to kvm-x86 selftests, thanks!

[1/1] KVM: selftests: Randomize dirty_log_test's delay before reaping the bitmap
      https://github.com/kvm-x86/linux/commit/4e0fdd9b0d7d

--
https://github.com/kvm-x86/linux/tree/next

      reply	other threads:[~2026-05-27 18:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 17:02 [PATCH] KVM: selftests: Randomize dirty_log_test's delay before reaping the bitmap Sean Christopherson
2026-05-27 18: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=177990523920.4120987.9255714954792808956.b4-ty@google.com \
    --to=seanjc@google.com \
    --cc=atwufei@163.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=wu.fei9@sanechips.com.cn \
    /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