From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Ping Fan Liu <pingfank@linux.vnet.ibm.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Alex Bligh <alex@alex.org.uk>
Subject: [Qemu-devel] [PATCH 0/2] qemu-timer: make qemu_timer_mod_ns() and qemu_timer_del() thread-safe
Date: Mon, 12 Aug 2013 14:49:27 +0200 [thread overview]
Message-ID: <1376311769-29811-1-git-send-email-stefanha@redhat.com> (raw)
These patches are based on Alex Bligh's v10 AioContext timers series.
The purpose of these patches is to eventually allow device models to set and
cancel timers without holding the global mutex. When the device model runs in
a vcpu thread and the iothread processes timers, the
QEMUTimerList->active_timers must be protected from concurrent access.
Patch 1 is a clean-up.
Patch 2 is the entire change needed to protect ->active_timers.
Stefan Hajnoczi (2):
qemu-timer: drop outdated signal safety comments
qemu-timer: make qemu_timer_mod_ns() and qemu_timer_del() thread-safe
include/qemu/timer.h | 17 +++++++++++++
qemu-timer.c | 70 ++++++++++++++++++++++++++++++++++++++--------------
2 files changed, 69 insertions(+), 18 deletions(-)
--
1.8.3.1
next reply other threads:[~2013-08-12 12:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 12:49 Stefan Hajnoczi [this message]
2013-08-12 12:49 ` [Qemu-devel] [PATCH 1/2] qemu-timer: drop outdated signal safety comments Stefan Hajnoczi
2013-08-12 13:15 ` Alex Bligh
2013-08-12 12:49 ` [Qemu-devel] [PATCH 2/2] qemu-timer: make qemu_timer_mod_ns() and qemu_timer_del() thread-safe Stefan Hajnoczi
2013-08-12 13:19 ` Alex Bligh
2013-08-15 0:05 ` liu ping fan
2013-08-15 8:01 ` Stefan Hajnoczi
2013-08-15 8:22 ` liu ping fan
2013-08-15 8:24 ` liu ping fan
2013-08-15 12:00 ` Stefan Hajnoczi
2013-08-19 12:15 ` Paolo Bonzini
2013-08-15 8:43 ` Alex Bligh
2013-08-19 12:12 ` Paolo Bonzini
2013-08-12 20:31 ` [Qemu-devel] [PATCH 0/2] " Benoît Canet
2013-08-12 21:20 ` Alex Bligh
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=1376311769-29811-1-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=alex@alex.org.uk \
--cc=pbonzini@redhat.com \
--cc=pingfank@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).