From: Paolo Bonzini <pbonzini@redhat.com>
To: Liu Ping Fan <qemulist@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, Alex Bligh <alex@alex.org.uk>
Subject: Re: [Qemu-devel] [PATCH v5 0/4] timers thread-safe stuff
Date: Mon, 07 Oct 2013 14:24:26 +0200 [thread overview]
Message-ID: <5252A7FA.2020107@redhat.com> (raw)
In-Reply-To: <1380090060-6764-1-git-send-email-pingfank@linux.vnet.ibm.com>
Stefan, will you pick this up next week or shall I?
I have patches for thread-safe icount almost ready to post, and I am not
sure through whom they are going to go.
Paolo
Il 25/09/2013 08:20, Liu Ping Fan ha scritto:
> v5:
> fine rename some variable in patch2&4.
> fix commit log for patch1&2
>
> v4:
> fix commit log for "protect timers_state's clock with seqlock" (Thanks for Alex)
>
> v3:
> 1. rename seqlock_read_check as seqlock_read_retry
> 2. Document timerlist were protected by BQL, and discard private lock around "qemu_event_wait(tl->ev)".
>
> v2:
> 1. fix comment in commit and code
> 2. fix race issue for qemu_clock_enable(foo,disable)
>
>
> Liu Ping Fan (2):
> timer: protect timers_state's clock with seqlock
> timer: make qemu_clock_enable sync between disable and timer's cb
>
> Paolo Bonzini (2):
> seqlock: introduce read-write seqlock
> qemu-thread: add QemuEvent
>
> cpus.c | 41 +++++++++++++---
> include/qemu/seqlock.h | 72 +++++++++++++++++++++++++++
> include/qemu/thread-posix.h | 8 +++
> include/qemu/thread-win32.h | 4 ++
> include/qemu/thread.h | 7 +++
> include/qemu/timer.h | 8 +++
> qemu-timer.c | 21 +++++++-
> util/qemu-thread-posix.c | 116 ++++++++++++++++++++++++++++++++++++++++++++
> util/qemu-thread-win32.c | 26 ++++++++++
> 9 files changed, 294 insertions(+), 9 deletions(-)
> create mode 100644 include/qemu/seqlock.h
>
next prev parent reply other threads:[~2013-10-07 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 6:20 [Qemu-devel] [PATCH v5 0/4] timers thread-safe stuff Liu Ping Fan
2013-09-25 6:20 ` [Qemu-devel] [PATCH v5 1/4] seqlock: introduce read-write seqlock Liu Ping Fan
2013-09-25 7:30 ` Paolo Bonzini
2013-09-25 9:28 ` liu ping fan
2013-09-25 6:20 ` [Qemu-devel] [PATCH v5 2/4] timer: protect timers_state's clock with seqlock Liu Ping Fan
2013-09-25 6:20 ` [Qemu-devel] [PATCH v5 3/4] qemu-thread: add QemuEvent Liu Ping Fan
2013-09-25 9:29 ` liu ping fan
2013-09-25 6:21 ` [Qemu-devel] [PATCH v5 4/4] timer: make qemu_clock_enable sync between disable and timer's cb Liu Ping Fan
2013-10-07 12:24 ` Paolo Bonzini [this message]
2013-10-08 7:18 ` [Qemu-devel] [PATCH v5 0/4] timers thread-safe stuff Stefan Hajnoczi
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=5252A7FA.2020107@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex@alex.org.uk \
--cc=jan.kiszka@siemens.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemulist@gmail.com \
--cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.