From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: mdroth@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH 0/3] run RCU callbacks within the iothread mutex, fix PCI hotplug
Date: Wed, 11 Feb 2015 18:14:29 +0100 [thread overview]
Message-ID: <1423674872-10676-1-git-send-email-pbonzini@redhat.com> (raw)
Patch 1 avoids that RCU callbacks are delayed forever if there's
scarcity of them, which is bad because qemu_opts_del will be called in
a RCU callbacks.
Patches 2 avoids complications due to instance_finalize callbacks that
are not thread-safe. It's a big hammer and it is not handsome, but I
gave up on making VFIO list manipulations thread-safe.
Patch 3 avoids a use-after-free when freeing address spaces.
These patches survived several hundred hotplug cycles, with MALLOC_PERTURB_
and G_SLICE=always-malloc on.
Paolo
Paolo Bonzini (3):
rcu: do not let RCU callbacks pile up indefinitely
rcu: run RCU callbacks under the BQL
memory: keep the owner of the AddressSpace alive until
do_address_space_destroy
memory.c | 5 +++++
tests/Makefile | 2 +-
util/rcu.c | 19 +++++++++++++------
3 files changed, 19 insertions(+), 7 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-02-11 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 17:14 Paolo Bonzini [this message]
2015-02-11 17:14 ` [Qemu-devel] [PATCH 1/3] rcu: do not let RCU callbacks pile up indefinitely Paolo Bonzini
2015-02-11 17:30 ` Paolo Bonzini
2015-02-12 9:05 ` Fam Zheng
2015-02-11 17:14 ` [Qemu-devel] [PATCH 2/3] rcu: run RCU callbacks under the BQL Paolo Bonzini
2015-02-11 20:26 ` Michael Roth
2015-02-11 20:39 ` Paolo Bonzini
2015-02-11 17:14 ` [Qemu-devel] [PATCH 3/3] memory: keep the owner of the AddressSpace alive until do_address_space_destroy Paolo Bonzini
2015-02-11 20:33 ` Michael Roth
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=1423674872-10676-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=mdroth@linux.vnet.ibm.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).