From: Jan Kiszka <jan.kiszka@siemens.com>
To: Liu Ping Fan <qemulist@gmail.com>
Cc: Alex Bligh <alex@alex.org.uk>,
Paolo Bonzini <pbonzini@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 1/4] seqlock: introduce read-write seqlock
Date: Mon, 23 Sep 2013 08:21:01 +0200 [thread overview]
Message-ID: <523FDDCD.6050407@siemens.com> (raw)
In-Reply-To: <1379837479-8419-2-git-send-email-pingfank@linux.vnet.ibm.com>
On 2013-09-22 10:11, Liu Ping Fan wrote:
> This lets the read-side access run outside the BQL.
In fact, not only BQL. Didn't the original commit provide a changlog
about the content of this patch? Otherwise, briefly describe use cases
and maybe the typical invocation pattern.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>From says you, signed-off only Paolo - this is inconsistent.
Jan
> ---
> include/qemu/seqlock.h | 72 ++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 72 insertions(+)
> create mode 100644 include/qemu/seqlock.h
>
> diff --git a/include/qemu/seqlock.h b/include/qemu/seqlock.h
> new file mode 100644
> index 0000000..3ff118a
> --- /dev/null
> +++ b/include/qemu/seqlock.h
> @@ -0,0 +1,72 @@
> +/*
> + * Seqlock implementation for QEMU
> + *
> + * Copyright Red Hat, Inc. 2013
> + *
> + * Author:
> + * Paolo Bonzini <pbonzini@redhat.com>
> + *
> + * This work is licensed under the terms of the GNU GPL, version 2 or later.
> + * See the COPYING file in the top-level directory.
> + *
> + */
> +#ifndef QEMU_SEQLOCK_H
> +#define QEMU_SEQLOCK_H 1
> +
> +#include <qemu/atomic.h>
> +#include <qemu/thread.h>
> +
> +typedef struct QemuSeqLock QemuSeqLock;
> +
> +struct QemuSeqLock {
> + QemuMutex *mutex;
> + unsigned sequence;
> +};
> +
> +static inline void seqlock_init(QemuSeqLock *sl, QemuMutex *mutex)
> +{
> + sl->mutex = mutex;
> + sl->sequence = 0;
> +}
> +
> +/* Lock out other writers and update the count. */
> +static inline void seqlock_write_lock(QemuSeqLock *sl)
> +{
> + if (sl->mutex) {
> + qemu_mutex_lock(sl->mutex);
> + }
> + ++sl->sequence;
> +
> + /* Write sequence before updating other fields. */
> + smp_wmb();
> +}
> +
> +static inline void seqlock_write_unlock(QemuSeqLock *sl)
> +{
> + /* Write other fields before finalizing sequence. */
> + smp_wmb();
> +
> + ++sl->sequence;
> + if (sl->mutex) {
> + qemu_mutex_unlock(sl->mutex);
> + }
> +}
> +
> +static inline unsigned seqlock_read_begin(QemuSeqLock *sl)
> +{
> + /* Always fail if a write is in progress. */
> + unsigned ret = sl->sequence & ~1;
> +
> + /* Read sequence before reading other fields. */
> + smp_rmb();
> + return ret;
> +}
> +
> +static int seqlock_read_retry(const QemuSeqLock *sl, unsigned start)
> +{
> + /* Read other fields before reading final sequence. */
> + smp_rmb();
> + return unlikely(sl->sequence != start);
> +}
> +
> +#endif
>
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-09-23 6:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 8:11 [Qemu-devel] [PATCH v4 0/4] timers thread-safe stuff Liu Ping Fan
2013-09-22 8:11 ` [Qemu-devel] [PATCH v4 1/4] seqlock: introduce read-write seqlock Liu Ping Fan
2013-09-23 6:21 ` Jan Kiszka [this message]
2013-09-24 5:33 ` liu ping fan
2013-09-24 8:13 ` Paolo Bonzini
2013-09-22 8:11 ` Liu Ping Fan
2013-09-22 8:11 ` [Qemu-devel] [PATCH v4 2/4] timer: protect timers_state's clock with seqlock Liu Ping Fan
2013-09-23 6:21 ` Jan Kiszka
2013-09-24 6:15 ` liu ping fan
2013-09-22 8:11 ` [Qemu-devel] [PATCH v4 3/4] qemu-thread: add QemuEvent Liu Ping Fan
2013-09-23 6:23 ` Jan Kiszka
2013-09-22 8:11 ` [Qemu-devel] [PATCH v4 4/4] timer: make qemu_clock_enable sync between disable and timer's cb Liu Ping Fan
2013-09-23 6:26 ` Jan Kiszka
2013-09-24 5:40 ` liu ping fan
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=523FDDCD.6050407@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alex@alex.org.uk \
--cc=kwolf@redhat.com \
--cc=pbonzini@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.