qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Liu Ping Fan <pingfank@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Alex Bligh <alex@alex.org.uk>,
	Paolo Bonzini <pbonzini@redhat.com>,
	MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Subject: [Qemu-devel] [PATCH 0/4]: timers thread-safe stuff
Date: Mon,  5 Aug 2013 15:33:22 +0800	[thread overview]
Message-ID: <1375688006-16780-1-git-send-email-pingfank@linux.vnet.ibm.com> (raw)

The patches has been rebased onto Alex's [RFC] [PATCHv5 00/16] aio / timers: Add AioContext timers and use ppoll
     permalink.gmane.org/gmane.comp.emulators.qemu/226333

For some other complied error issue, I can not finish compiling, will fix it later.

Changes since last version:
 1. drop the overlap partition and leave only thread-safe stuff
 2. For timers_state, since currently, only vm_clock can be read outside BQL.
    There is no protection with ticks(since the protection will cost more in read_tsc path).
 3. use light weight QemuEvent to re-implement the qemu_clock_enable(foo,false)


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                      |  36 +++++++++++---
 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        |   1 +
 qemu-timer.c                |  11 +++++
 util/qemu-thread-posix.c    | 116 ++++++++++++++++++++++++++++++++++++++++++++
 util/qemu-thread-win32.c    |  26 ++++++++++
 9 files changed, 274 insertions(+), 7 deletions(-)
 create mode 100644 include/qemu/seqlock.h

-- 
1.8.1.4

             reply	other threads:[~2013-08-05  7:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05  7:33 Liu Ping Fan [this message]
2013-08-05  7:33 ` [Qemu-devel] [PATCH 1/4] seqlock: introduce read-write seqlock Liu Ping Fan
2013-08-05  7:33 ` [Qemu-devel] [PATCH 2/4] timer: protect timers_state's clock with seqlock Liu Ping Fan
2013-08-05 13:29   ` Paolo Bonzini
2013-08-06  5:58     ` liu ping fan
2013-08-06  7:31       ` Paolo Bonzini
2013-08-06  9:30   ` Stefan Hajnoczi
2013-08-07  5:46     ` liu ping fan
2013-08-05  7:33 ` [Qemu-devel] [PATCH 3/4] qemu-thread: add QemuEvent Liu Ping Fan
2013-08-05  7:33 ` [Qemu-devel] [PATCH 4/4] timer: make qemu_clock_enable sync between disable and timer's cb Liu Ping Fan
2013-08-05 10:53   ` Paolo Bonzini
2013-08-05 10:00 ` [Qemu-devel] [PATCH 0/4]: timers thread-safe stuff Alex Bligh
2013-08-06  5:37   ` liu ping fan
2013-08-06  6:14     ` 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=1375688006-16780-1-git-send-email-pingfank@linux.vnet.ibm.com \
    --to=pingfank@linux.vnet.ibm.com \
    --cc=alex@alex.org.uk \
    --cc=jan.kiszka@siemens.com \
    --cc=kwolf@redhat.com \
    --cc=morita.kazutaka@lab.ntt.co.jp \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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 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).