From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, famz@redhat.com, fred.konrad@greensocs.com
Subject: [Qemu-devel] [PATCH v2 0/9] RCUification of the memory API, part 2
Date: Tue, 3 Feb 2015 13:52:19 +0100 [thread overview]
Message-ID: <1422967948-3261-1-git-send-email-pbonzini@redhat.com> (raw)
Part 2 converts ram_list to RCU. It is enough of a base for Stefan's
work on thread-safe migration bitmaps. TCG folks, please review.
Parts 3 (posted today) and 3.5 (to be done) will separate removal and
reclamation of device data. Part 4 will switch KVM MMIO and PIO to
unlocked lookup and convert a single device to unlocked access.
v1->v2: add comment in cpu_reload_memory_map [Fam]
do not remove ram_list mutex [Fam]
some improvements to test-rcu-list
Mike Day (4):
rcu: introduce RCU-enabled QLIST
cosmetic changes preparing for the following patches
exec: convert ram_list to QLIST
Convert ram_list to RCU
Paolo Bonzini (5):
exec: introduce cpu_reload_memory_map
exec: make iotlb RCU-friendly
exec: RCUify AddressSpaceDispatch
exec: protect mru_block with RCU
rcu: prod call_rcu thread when calling synchronize_rcu
arch_init.c | 70 ++++++----
cpu-exec.c | 33 +++++
cpus.c | 2 +-
cputlb.c | 13 +-
exec.c | 294 ++++++++++++++++++++++++++++-------------
hw/9pfs/virtio-9p-synth.c | 2 +-
hw/i386/intel_iommu.c | 3 +
hw/pci-host/apb.c | 1 +
hw/ppc/spapr_iommu.c | 1 +
include/exec/cpu-all.h | 13 +-
include/exec/cputlb.h | 2 +-
include/exec/exec-all.h | 5 +-
include/qemu/queue.h | 11 --
include/qemu/rcu_queue.h | 134 +++++++++++++++++++
include/qom/cpu.h | 1 +
scripts/dump-guest-memory.py | 8 +-
softmmu_template.h | 4 +-
tests/Makefile | 5 +-
tests/test-rcu-list.c | 306 +++++++++++++++++++++++++++++++++++++++++++
util/rcu.c | 8 +-
20 files changed, 767 insertions(+), 149 deletions(-)
create mode 100644 include/qemu/rcu_queue.h
create mode 100644 tests/test-rcu-list.c
--
1.8.3.1
next reply other threads:[~2015-02-03 12:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 12:52 Paolo Bonzini [this message]
2015-02-03 12:52 ` [Qemu-devel] [PATCH 1/9] exec: introduce cpu_reload_memory_map Paolo Bonzini
2015-02-04 1:46 ` Fam Zheng
2015-02-03 12:52 ` [Qemu-devel] [PATCH 2/9] exec: make iotlb RCU-friendly Paolo Bonzini
2015-02-04 2:31 ` Fam Zheng
2015-02-03 12:52 ` [Qemu-devel] [PATCH 3/9] exec: RCUify AddressSpaceDispatch Paolo Bonzini
2015-02-04 2:56 ` Fam Zheng
2015-02-03 12:52 ` [Qemu-devel] [PATCH 4/9] rcu: introduce RCU-enabled QLIST Paolo Bonzini
2015-02-04 3:42 ` Fam Zheng
2015-02-04 12:46 ` Paolo Bonzini
2015-02-05 2:03 ` Fam Zheng
2015-02-03 12:52 ` [Qemu-devel] [PATCH 5/9] exec: protect mru_block with RCU Paolo Bonzini
2015-02-05 6:23 ` Fam Zheng
2015-02-05 8:37 ` Paolo Bonzini
2015-02-05 9:30 ` Fam Zheng
2015-02-03 12:52 ` [Qemu-devel] [PATCH 6/9] cosmetic changes preparing for the following patches Paolo Bonzini
2015-02-04 3:10 ` Fam Zheng
2015-02-04 12:51 ` Paolo Bonzini
2015-02-03 12:52 ` [Qemu-devel] [PATCH 7/9] rcu: prod call_rcu thread when calling synchronize_rcu Paolo Bonzini
2015-02-04 3:13 ` Fam Zheng
2015-02-03 12:52 ` [Qemu-devel] [PATCH 8/9] exec: convert ram_list to QLIST Paolo Bonzini
2015-02-03 12:52 ` [Qemu-devel] [PATCH 9/9] Convert ram_list to RCU 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=1422967948-3261-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=fred.konrad@greensocs.com \
--cc=peter.maydell@linaro.org \
--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).