From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/6] block: avoid recursive AioContext acquire in bdrv_inactivate_all()
Date: Wed, 13 Dec 2017 22:23:02 +0100 [thread overview]
Message-ID: <a376c41f-e8cb-2ea0-b464-d9ff3d52c395@redhat.com> (raw)
In-Reply-To: <20171207201320.19284-1-stefanha@redhat.com>
On 07/12/2017 21:13, Stefan Hajnoczi wrote:
> v2:
> * Added docs/devel/multiple-iothreads.txt doc update [Kevin]
> * Added qemu-iotests 203 test case [Kevin]
> * Added iothread_stop() race fix to make 203 reliable
>
> Patch 1 is Paolo's recursive locking removal in bdrv_inactivate_all(). This
> solve migration hangs and is the main point of the patch series.
>
> Patches 2-6 add a qemu-iotests test case and update the multiple-iothreads.txt
> documentation to discourage recursive AioContext locking.
>
> Based-on: <20171206144550.22295-1-stefanha@redhat.com>
>
> Paolo Bonzini (1):
> block: avoid recursive AioContext acquire in bdrv_inactivate_all()
>
> Stefan Hajnoczi (5):
> docs: mark nested AioContext locking as a legacy API
> blockdev: add x-blockdev-set-iothread force boolean
> iotests: add VM.add_object()
> iothread: fix iothread_stop() race condition
> qemu-iotests: add 203 savevm with IOThreads test
>
> docs/devel/multiple-iothreads.txt | 7 +++--
> qapi/block-core.json | 6 +++-
> include/sysemu/iothread.h | 3 +-
> block.c | 14 ++++++++--
> blockdev.c | 11 ++++----
> iothread.c | 20 +++++++++----
> tests/qemu-iotests/203 | 59 +++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/203.out | 6 ++++
> tests/qemu-iotests/group | 1 +
> tests/qemu-iotests/iotests.py | 5 ++++
> 10 files changed, 114 insertions(+), 18 deletions(-)
> create mode 100755 tests/qemu-iotests/203
> create mode 100644 tests/qemu-iotests/203.out
>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
aio_notify should also be put on the blacklist of things that have
slowly become bad ideas. :|
Paolo
next prev parent reply other threads:[~2017-12-13 21:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 20:13 [Qemu-devel] [PATCH v2 0/6] block: avoid recursive AioContext acquire in bdrv_inactivate_all() Stefan Hajnoczi
2017-12-07 20:13 ` [Qemu-devel] [PATCH v2 1/6] " Stefan Hajnoczi
2017-12-07 22:04 ` Eric Blake
2017-12-07 20:13 ` [Qemu-devel] [PATCH v2 2/6] docs: mark nested AioContext locking as a legacy API Stefan Hajnoczi
2017-12-07 22:34 ` Eric Blake
2017-12-07 20:13 ` [Qemu-devel] [PATCH v2 3/6] blockdev: add x-blockdev-set-iothread force boolean Stefan Hajnoczi
2017-12-07 22:38 ` Eric Blake
2017-12-07 20:13 ` [Qemu-devel] [PATCH v2 4/6] iotests: add VM.add_object() Stefan Hajnoczi
2017-12-07 22:39 ` Eric Blake
2017-12-07 20:13 ` [Qemu-devel] [PATCH v2 5/6] iothread: fix iothread_stop() race condition Stefan Hajnoczi
2017-12-07 22:42 ` Eric Blake
2017-12-07 20:13 ` [Qemu-devel] [PATCH v2 6/6] qemu-iotests: add 203 savevm with IOThreads test Stefan Hajnoczi
2017-12-07 22:46 ` Eric Blake
2017-12-13 21:23 ` Paolo Bonzini [this message]
2017-12-14 11:12 ` [Qemu-devel] [PATCH v2 0/6] block: avoid recursive AioContext acquire in bdrv_inactivate_all() 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=a376c41f-e8cb-2ea0-b464-d9ff3d52c395@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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).