kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: Andrew Jones <drjones@redhat.com>,
	peterx@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
	Sean Christopherson <seanjc@google.com>
Subject: [PATCH v3 0/2] KVM: selftests: fix races in dirty log test
Date: Sat, 17 Apr 2021 10:36:00 -0400	[thread overview]
Message-ID: <20210417143602.215059-1-peterx@redhat.com> (raw)

Please consider overtake the previous v2 [1] of this patch which is a single
patch, also please find more information in the commit message of each patch.

I kept the versioning since it solves the same problem, but mostly rewritten.

I've run a few hours of below workloads in parallel to test this patch:

  (1) while :; do taskset -c 1 ./dirty_log_test; done
  (2) taskset -c 1 bash -c "while :; do :; done"

Review comments are greatly welcomed.

Thanks,

[1] https://lore.kernel.org/lkml/20210413213641.23742-1-peterx@redhat.com/

Peter Xu (2):
  KVM: selftests: Sync data verify of dirty logging with guest sync
  KVM: selftests: Wait for vcpu thread before signal setup

 tools/testing/selftests/kvm/dirty_log_test.c | 68 +++++++++++++++++---
 1 file changed, 58 insertions(+), 10 deletions(-)

-- 
2.26.2



             reply	other threads:[~2021-04-17 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17 14:36 Peter Xu [this message]
2021-04-17 14:36 ` [PATCH v3 1/2] KVM: selftests: Sync data verify of dirty logging with guest sync Peter Xu
2021-04-18 12:43   ` Peter Xu
2021-04-20  8:07     ` Paolo Bonzini
2021-04-20 13:10       ` Peter Xu
2021-04-20 14:07         ` Paolo Bonzini
2021-04-17 14:36 ` [PATCH v3 2/2] KVM: selftests: Wait for vcpu thread before signal setup Peter Xu
2021-04-20  8:14   ` Paolo Bonzini

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=20210417143602.215059-1-peterx@redhat.com \
    --to=peterx@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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 NNTP newsgroup(s).