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 1/4] seqlock: introduce read-write seqlock
Date: Wed, 25 Sep 2013 09:30:11 +0200 [thread overview]
Message-ID: <52429103.40002@redhat.com> (raw)
In-Reply-To: <1380090060-6764-2-git-send-email-pingfank@linux.vnet.ibm.com>
Il 25/09/2013 08:20, Liu Ping Fan ha scritto:
> From: Paolo Bonzini <pbonzini@redhat.com>
>
> Seqlock implementation for QEMU. Usage idiom
>
> reader:
> do{
> start = seqlock_read_begin()
>
> }while(seqlock_read_try(start))
>
> writer:
> seqlock_write_lock()
> ...
> seqlock_write_unlock()
>
> initialization:
> seqlock_init(QemuSeqLock *sl, QemuMutex *mutex)
> where mutex could be NULL if the caller will provide extra lock
> protection for seqlock_write_lock.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
You need to include your own signoff in addition to mine, here and in
patch 3.
Just reply to the two patches with the Signed-off-by line, whoever
applies can pick it up.
Paolo
next prev parent reply other threads:[~2013-09-25 7:30 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 [this message]
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 ` [Qemu-devel] [PATCH v5 0/4] timers thread-safe stuff Paolo Bonzini
2013-10-08 7:18 ` 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=52429103.40002@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.