From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 00/10] aio_context_acquire/release pushdown, part 1
Date: Fri, 13 Jan 2017 10:54:00 +0800 [thread overview]
Message-ID: <20170113025315.GA23020@lemon> (raw)
In-Reply-To: <20170112180800.21085-1-pbonzini@redhat.com>
On Thu, 01/12 19:07, Paolo Bonzini wrote:
> This is the first step of pushing down the AioContext lock. Bottom halves
> are already protected by their own lock, use it also for walking_bh
> and for the handlers list (including walking_handlers). The (lock,
> walking_foo) pair is wrapped into the QemuLockCnt primitive.
>
> The only difference from v3 is a smattering of tiny nice improvements
> to QemuLockCnt.
>
> Paolo
>
> v4->v5:
> remove stray tabs [patchew]
>
> v3->v4:
> Avoid useless atomic_mb_read in non-futex lockcnt [Stefan]
> Use atomic_read in qemu_lockcnt_count [Stefan]
> Tweak comment for qemu_lockcnt_cmpxchg_or_wait [Fam]
> Use if/else in qemu_lockcnt_dec_and_lock [Fam]
> Comment QEMU_LOCKCNT_STATE_* definitions [Fam]
Perfect!
Reviewed-by: Fam Zheng <famz@redhat.com>
next prev parent reply other threads:[~2017-01-13 2:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 18:07 [Qemu-devel] [PATCH v5 00/10] aio_context_acquire/release pushdown, part 1 Paolo Bonzini
2017-01-12 18:07 ` [Qemu-devel] [PATCH 01/10] aio: rename bh_lock to list_lock Paolo Bonzini
2017-01-12 18:07 ` [Qemu-devel] [PATCH 02/10] qemu-thread: introduce QemuLockCnt Paolo Bonzini
2017-01-12 18:07 ` [Qemu-devel] [PATCH 03/10] aio: make ctx->list_lock a QemuLockCnt, subsuming ctx->walking_bh Paolo Bonzini
2017-01-12 18:07 ` [Qemu-devel] [PATCH 04/10] qemu-thread: optimize QemuLockCnt with futexes on Linux Paolo Bonzini
2017-01-12 18:07 ` [Qemu-devel] [PATCH 05/10] aio-posix: split aio_dispatch_handlers out of aio_dispatch Paolo Bonzini
2017-01-12 18:07 ` [Qemu-devel] [PATCH 06/10] aio: tweak walking in dispatch phase Paolo Bonzini
2017-01-12 18:07 ` [Qemu-devel] [PATCH 07/10] aio-posix: remove walking_handlers, protecting AioHandler list with list_lock Paolo Bonzini
2017-01-12 18:07 ` [Qemu-devel] [PATCH 08/10] aio-win32: " Paolo Bonzini
2017-01-12 18:07 ` [Qemu-devel] [PATCH 09/10] aio: document locking Paolo Bonzini
2017-01-12 18:08 ` [Qemu-devel] [PATCH 10/10] async: optimize aio_bh_poll Paolo Bonzini
2017-01-13 2:54 ` Fam Zheng [this message]
2017-01-13 13:20 ` [Qemu-devel] [PATCH v5 00/10] aio_context_acquire/release pushdown, part 1 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=20170113025315.GA23020@lemon \
--to=famz@redhat.com \
--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).