public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	peterx@redhat.com, Sean Christopherson <seanjc@google.com>,
	Andrew Jones <drjones@redhat.com>
Subject: [PATCH v4 0/2] KVM: selftests: fix races in dirty log test
Date: Tue, 20 Apr 2021 11:39:27 -0400	[thread overview]
Message-ID: <20210420153929.482810-1-peterx@redhat.com> (raw)

v4:
- add missing vcpu_handle_sync_stop() call in dirty ring test

The other solution of patch 2 is here [1]

I got another report that there seems to still be a race, but that one seems
extremely hard to trigger, even so far we don't know whether that could be
ARM-only.  Since current fix should make sense already and fix real problems,
IMHO we don't need to wait for that.

Paolo, I still kept the 2nd patch just for completeness, but feel free to
ignore the 2nd patch if you prefer the other version, and I'll follow your
preference.

Thanks!

[1] https://lore.kernel.org/kvm/20210420081614.684787-1-pbonzini@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 | 70 +++++++++++++++++---
 1 file changed, 59 insertions(+), 11 deletions(-)

-- 
2.26.2



             reply	other threads:[~2021-04-20 15:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 15:39 Peter Xu [this message]
2021-04-20 15:39 ` [PATCH v4 1/2] KVM: selftests: Sync data verify of dirty logging with guest sync Peter Xu
2021-04-20 15:39 ` [PATCH v4 2/2] KVM: selftests: Wait for vcpu thread before signal setup Peter Xu

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=20210420153929.482810-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