From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: jan.kiszka@siemens.com
Subject: [Qemu-devel] [PATCH for-2.4 0/9] KVM: Do I/O outside BQL whenever possible
Date: Thu, 18 Jun 2015 18:47:17 +0200 [thread overview]
Message-ID: <1434646046-27150-1-git-send-email-pbonzini@redhat.com> (raw)
This is the rebased and updated version of the patches I posted a
couple months ago (well before soft freeze :)).
This version introduces a qemu_mutex_iothread_locked() primitive
in order to avoid recursive locking of the BQL. The previous
attempts, which used functions such as address_space_rw_unlocked,
required the introduction of a multitude of *_unlocked functions
(e.g. address_space_ldl_unlocked or dma_buf_write_unlocked).
Note that adding unlocked access to TCG would require reverting
commit 3b64349 (memory: Replace io_mem_read/write with
memory_region_dispatch_read/write, 2015-04-26).
Paolo
Jan Kiszka (4):
memory: Add global-locking property to memory regions
memory: let address_space_rw/ld*/st* run outside the BQL
kvm: First step to push iothread lock out of inner run loop
kvm: Switch to unlocked PIO
Paolo Bonzini (5):
main-loop: use qemu_mutex_lock_iothread consistently and simplify it
main-loop: introduce qemu_mutex_iothread_locked
exec: pull qemu_flush_coalesced_mmio_buffer() into
address_space_rw/ld*/st*
acpi: mark PMTIMER as unlocked
kvm: Switch to unlocked MMIO
cpus.c | 22 +++++++++++----
exec.c | 69 ++++++++++++++++++++++++++++++++++++++++++++++++
hw/acpi/core.c | 1 +
include/exec/memory.h | 26 ++++++++++++++++++
include/qemu/main-loop.h | 10 +++++++
kvm-all.c | 10 +++++--
memory.c | 17 +++++++-----
stubs/iothread-lock.c | 5 ++++
target-i386/kvm.c | 18 +++++++++++++
target-mips/kvm.c | 4 +++
target-ppc/kvm.c | 4 +++
11 files changed, 173 insertions(+), 13 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-06-18 16:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 16:47 Paolo Bonzini [this message]
2015-06-18 16:47 ` [Qemu-devel] [PATCH 1/9] main-loop: use qemu_mutex_lock_iothread consistently Paolo Bonzini
2015-06-23 13:49 ` Frederic Konrad
2015-06-23 13:56 ` Paolo Bonzini
2015-06-23 14:18 ` Frederic Konrad
2015-06-18 16:47 ` [Qemu-devel] [PATCH 2/9] main-loop: introduce qemu_mutex_iothread_locked Paolo Bonzini
2015-06-23 8:48 ` Fam Zheng
2015-06-18 16:47 ` [Qemu-devel] [PATCH 3/9] memory: Add global-locking property to memory regions Paolo Bonzini
2015-06-23 8:51 ` Fam Zheng
2015-06-18 16:47 ` [Qemu-devel] [PATCH 4/9] exec: pull qemu_flush_coalesced_mmio_buffer() into address_space_rw/ld*/st* Paolo Bonzini
2015-06-23 9:05 ` Fam Zheng
2015-06-23 9:12 ` Paolo Bonzini
2015-06-18 16:47 ` [Qemu-devel] [PATCH 5/9] memory: let address_space_rw/ld*/st* run outside the BQL Paolo Bonzini
2015-06-24 16:56 ` Alex Bennée
2015-06-24 17:21 ` Paolo Bonzini
2015-06-24 18:50 ` Alex Bennée
2015-06-25 8:13 ` Paolo Bonzini
2015-06-18 16:47 ` [Qemu-devel] [PATCH 6/9] kvm: First step to push iothread lock out of inner run loop Paolo Bonzini
2015-06-18 18:19 ` Christian Borntraeger
2015-06-23 9:26 ` Fam Zheng
2015-06-23 9:29 ` Paolo Bonzini
2015-06-23 9:45 ` Fam Zheng
2015-06-23 9:49 ` Paolo Bonzini
2015-06-18 16:47 ` [Qemu-devel] [PATCH 7/9] kvm: Switch to unlocked PIO Paolo Bonzini
2015-06-18 16:47 ` [Qemu-devel] [PATCH 8/9] acpi: mark PMTIMER as unlocked Paolo Bonzini
2015-06-18 16:47 ` [Qemu-devel] [PATCH 9/9] kvm: Switch to unlocked MMIO 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=1434646046-27150-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=jan.kiszka@siemens.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).