From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gregory Haskins <ghaskins@novell.com>, avi@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
avi@redhat.com, mtosatti@redhat.com, paulmck@linux.vnet.ibm.com,
markmc@redhat.com
Subject: [PATCHv5 0/6] kvm: locking and API rework for iosignalfd
Date: Mon, 29 Jun 2009 22:23:58 +0300 [thread overview]
Message-ID: <20090629192358.GA27464@redhat.com> (raw)
This series switches kvm_io_device to slots_lock from kvm->lock mutex,
and uses that to rework io bus API. This takes less locks on data path,
and uses less lines of code. These changes will also be useful to serve
as basis for Greg's iosignalfd work.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
This works for me, but please review carefully.
Changes since v4:
Typo fix
Changes since v3:
Fix bug noticed by Marcelo
Switch pit creation to slots_lock
Add unlocked variant for bus changes: in use by pit
More documentation
Changes since v2:
I have split the patch and reworked along the lines suggested by Avi.
Michael S. Tsirkin (6):
kvm: document locking for kvm_io_device_ops
kvm: switch coalesced mmio changes to slots_lock
kvm: switch pit creation to slots_lock
kvm: convert bus to slots_lock
kvm: remove in_range from io devices
kvm: document lock nesting rule
arch/ia64/kvm/kvm-ia64.c | 28 +++--------
arch/x86/kvm/i8254.c | 54 +++++++++++----------
arch/x86/kvm/i8259.c | 22 +++++----
arch/x86/kvm/lapic.c | 44 ++++++++---------
arch/x86/kvm/x86.c | 114 +++++++++++++-------------------------------
include/linux/kvm_host.h | 11 +++-
virt/kvm/coalesced_mmio.c | 28 +++++------
virt/kvm/ioapic.c | 24 +++++----
virt/kvm/iodev.h | 42 +++++++---------
virt/kvm/kvm_main.c | 38 +++++++++++----
10 files changed, 183 insertions(+), 222 deletions(-)
next reply other threads:[~2009-06-29 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 19:23 Michael S. Tsirkin [this message]
2009-07-01 8:10 ` [PATCHv5 0/6] kvm: locking and API rework for iosignalfd Avi Kivity
2009-07-01 11:59 ` Gregory Haskins
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=20090629192358.GA27464@redhat.com \
--to=mst@redhat.com \
--cc=avi@redhat.com \
--cc=ghaskins@novell.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mtosatti@redhat.com \
--cc=paulmck@linux.vnet.ibm.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