From: Harsh Prateek Bora <harsh@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: stefanha@gmail.com, aneesh.kumar@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH 0/2] Introduce QemuRWLock
Date: Mon, 3 Oct 2011 16:53:12 +0530 [thread overview]
Message-ID: <1317640994-16559-1-git-send-email-harsh@linux.vnet.ibm.com> (raw)
SynthFS uses rwlocks, which raise the need of a generic QemuRWLock APIs.
This patchset introduces the same making necessary changes to relevant code.
Harsh Prateek Bora (2):
Introduce QemuRWLock
Use qemu_rwlock_* interface instead of pthread_rwlock_*
hw/9pfs/virtio-9p-synth.c | 23 ++++++++++-------------
qemu-thread-posix.c | 26 ++++++++++++++++++++++++++
qemu-thread-posix.h | 4 ++++
qemu-thread.h | 6 ++++++
4 files changed, 46 insertions(+), 13 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-10-03 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 11:23 Harsh Prateek Bora [this message]
2011-10-03 11:23 ` [Qemu-devel] [PATCH 1/2] Introduce QemuRWLock Harsh Prateek Bora
2011-10-03 11:23 ` [Qemu-devel] [PATCH 2/2] Use qemu_rwlock_* interface instead of pthread_rwlock_* Harsh Prateek Bora
2011-10-03 12:16 ` [Qemu-devel] [PATCH 0/2] Introduce QemuRWLock Jan Kiszka
2011-10-03 17:30 ` Aneesh Kumar K.V
2011-10-03 17:50 ` Jan Kiszka
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=1317640994-16559-1-git-send-email-harsh@linux.vnet.ibm.com \
--to=harsh@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).