qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] rcu: missing thread registration
Date: Mon, 13 Jul 2015 13:31:02 +0200	[thread overview]
Message-ID: <1436787065-25095-1-git-send-email-pbonzini@redhat.com> (raw)

Patch 2 fixes the problem, whereby threads were not being registered
but still happily used RCU.  Patch 1 simplifies the registration by
making rcu_unregister_thread automatic.  Patch 3 avoids having the
same bug in the future.

Paolo

Paolo Bonzini (3):
  rcu: automatically unregister threads when they exit
  rcu: actually register threads that have RCU read-side critical
    sections
  rcu: detect missing rcu_register_thread()

 cpus.c                |  6 ++++++
 include/qemu/rcu.h    |  4 +++-
 iothread.c            |  3 +++
 migration/migration.c |  3 +++
 tests/rcutorture.c    | 10 ----------
 tests/test-rcu-list.c |  2 ++
 util/rcu.c            | 30 ++++++++++++++++++++++++++++--
 7 files changed, 45 insertions(+), 13 deletions(-)

-- 
2.4.3

             reply	other threads:[~2015-07-13 11:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 11:31 Paolo Bonzini [this message]
2015-07-13 11:31 ` [Qemu-devel] [PATCH 1/3] rcu: automatically unregister threads when they exit Paolo Bonzini
2015-07-13 11:31 ` [Qemu-devel] [PATCH 2/3] rcu: actually register threads that have RCU read-side critical sections Paolo Bonzini
2015-07-13 11:31 ` [Qemu-devel] [PATCH 3/3] rcu: detect missing rcu_register_thread() Paolo Bonzini
2015-07-14  3:36 ` [Qemu-devel] [PATCH 0/3] rcu: missing thread registration Fam Zheng

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=1436787065-25095-1-git-send-email-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).