From: "Denis V. Lunev" <den@openvz.org>
To: quintela@redhat.com
Cc: Amit Shah <amit.shah@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/4] migration: add missed aio_context_acquire into HMP snapshot code
Date: Wed, 28 Oct 2015 18:57:01 +0300 [thread overview]
Message-ID: <5630F04D.5060309@openvz.org> (raw)
In-Reply-To: <871tcf80t5.fsf@neno.neno>
On 10/28/2015 06:33 PM, Juan Quintela wrote:
> "Denis V. Lunev" <den@openvz.org> wrote:
>> aio_context should be locked in the similar way as was done in QMP
>> snapshot creation in the other case there are a lot of possible
>> troubles if native AIO mode is enabled for disk.
>>
>> - the command can hang (HMP thread) with missed wakeup (the operation is
>> actually complete)
>> io_submit
>> ioq_submit
>> laio_submit
>> raw_aio_submit
>> raw_aio_readv
>> bdrv_co_io_em
>> bdrv_co_readv_em
>> bdrv_aligned_preadv
>> bdrv_co_do_preadv
>> bdrv_co_do_readv
>> bdrv_co_readv
>> qcow2_co_readv
>> bdrv_aligned_preadv
>> bdrv_co_do_pwritev
>> bdrv_rw_co_entry
>>
>> - QEMU can assert in coroutine re-enter
>> __GI_abort
>> qemu_coroutine_enter
>> bdrv_co_io_em_complete
>> qemu_laio_process_completion
>> qemu_laio_completion_bh
>> aio_bh_poll
>> aio_dispatch
>> aio_poll
>> iothread_run
>>
>> qemu_fopen_bdrv and bdrv_fclose are used in real snapshot operations only
>> along with block drivers. This change should influence only HMP snapshot
>> operations.
>>
>> AioContext lock is reqursive. Thus nested locking should not be a problem.
>>
>> Signed-off-by: Denis V. Lunev <den@openvz.org>
>> CC: Stefan Hajnoczi <stefanha@redhat.com>
>> CC: Paolo Bonzini <pbonzini@redhat.com>
>> CC: Juan Quintela <quintela@redhat.com>
>> CC: Amit Shah <amit.shah@redhat.com>
> Reviewed-by: Juan Quintela <quintela@redhat.com>
>
> Should this one go through the block layer? I guess that the block
> layer, but otherwise, I will get it.
let's wait opinion from Stefan :)
Either way would be good to me, but I want to have
previous patches from the set committed too. They
should be definitely flow through block tree thus
block tree would be better.
Anyway, I can retry the process with patches 1-3
if you'll get 4 through your queue.
Den
next prev parent reply other threads:[~2015-10-28 15:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 15:01 [Qemu-devel] [PATCH v3 0/4] dataplane snapshot fixes Denis V. Lunev
2015-10-28 15:01 ` [Qemu-devel] [PATCH 1/4] fifolock: create rfifolock_is_locked helper Denis V. Lunev
2015-10-30 15:41 ` Stefan Hajnoczi
2015-10-30 20:30 ` Denis V. Lunev
2015-11-02 13:10 ` Stefan Hajnoczi
2015-11-01 13:55 ` Denis V. Lunev
2015-11-02 13:12 ` Stefan Hajnoczi
2015-11-02 13:39 ` Denis V. Lunev
2015-11-02 13:55 ` Paolo Bonzini
2015-11-02 14:02 ` Denis V. Lunev
2015-10-28 15:01 ` [Qemu-devel] [PATCH 2/4] aio_context: create aio_context_is_locked helper Denis V. Lunev
2015-10-30 15:42 ` Stefan Hajnoczi
2015-10-28 15:01 ` [Qemu-devel] [PATCH 3/4] io: add locking constraints check into bdrv_drain to ensure locking Denis V. Lunev
2015-10-30 15:43 ` Stefan Hajnoczi
2015-10-28 15:01 ` [Qemu-devel] [PATCH 4/4] migration: add missed aio_context_acquire into HMP snapshot code Denis V. Lunev
2015-10-28 15:33 ` Juan Quintela
2015-10-28 15:57 ` Denis V. Lunev [this message]
2015-10-30 15:52 ` Stefan Hajnoczi
2015-11-03 14:48 ` Juan Quintela
2015-11-03 15:30 ` Stefan Hajnoczi
2015-11-03 15:36 ` Denis V. Lunev
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=5630F04D.5060309@openvz.org \
--to=den@openvz.org \
--cc=amit.shah@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=quintela@redhat.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 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).