From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block: Don't acquire AioContext in hmp_qemu_io()
Date: Wed, 13 Dec 2017 11:41:05 +0100 [thread overview]
Message-ID: <20171213104105.GA3950@localhost.localdomain> (raw)
In-Reply-To: <20171212134800.21836-1-kwolf@redhat.com>
Am 12.12.2017 um 14:48 hat Kevin Wolf geschrieben:
> Commit 15afd94a047 added code to acquire and release the AioContext in
> qemuio_command(). This means that the lock is taken twice now in the
> call path from hmp_qemu_io(). This causes BDRV_POLL_WHILE() to hang for
> any requests issued to nodes in a non-mainloop AioContext.
>
> Dropping the first locking from hmp_qemu_io() fixes the problem.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Applied to block-next.
Kevin
prev parent reply other threads:[~2017-12-13 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 13:48 [Qemu-devel] [PATCH] block: Don't acquire AioContext in hmp_qemu_io() Kevin Wolf
2017-12-13 10:26 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-12-13 10:41 ` Kevin Wolf [this message]
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=20171213104105.GA3950@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).