From: tu bo <tubo@linux.vnet.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: famz@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/6] virtio: refactor host notifiers
Date: Thu, 31 Mar 2016 13:47:46 +0800 [thread overview]
Message-ID: <56FCBA02.6080304@linux.vnet.ibm.com> (raw)
In-Reply-To: <56FAACFD.90101@de.ibm.com>
Hi Christian:
I got the same crash with qemu master + assertion patch + "[PATCH 0/6]
virtio: refactor host notifiers" + Paolo's fix,
(gdb) bt
#0 blk_aio_read_entry (opaque=0x0) at block/block-backend.c:916
#1 0x000002aa2e8e88fe in coroutine_trampoline (i0=<optimized out>,
i1=-1677703696) at util/coroutine-ucontext.c:78
#2 0x000003ffa85d150a in __makecontext_ret () from /lib64/libc.so.6
On 03/30/2016 12:27 AM, Christian Borntraeger wrote:
> On 03/29/2016 03:50 PM, Paolo Bonzini wrote:
>>
>>
>> On 29/03/2016 13:45, Cornelia Huck wrote:
>>>>> Hi Tu Bo,
>>>>>
>>>>> please always include the assertion patch at
>>>>> https://lists.gnu.org/archive/html/qemu-block/2016-03/msg00546.html in
>>>>> your tests. Can you include the backtrace from all threads with that patch?
>>>>>
>>>> thanks for your reminder about the assertion patch. Here is the
>>>> backtrace with qemu master + assertion patch + "[PATCH 0/6] virtio:
>>>> refactor host notifiers",
>>>
>>> FWIW, I've been running this in a reboot loop for the last 2 1/2 hours.
>>> Could you perhaps share your command line?
>>
>> From code inspection, the following is also necessary or at least a
>> good idea:
>>
>> diff --git a/hw/block/dataplane/virtio-blk.c b/hw/block/dataplane/virtio-blk.c
>> index 6fb29e3..7fa8477 100644
>> --- a/hw/block/dataplane/virtio-blk.c
>> +++ b/hw/block/dataplane/virtio-blk.c
>> @@ -258,7 +258,7 @@ void virtio_blk_data_plane_stop(VirtIOBlockDataPlane *s)
>> aio_context_acquire(s->ctx);
>>
>> /* Stop notifications for new requests from guest */
>> - virtio_queue_aio_set_host_notifier_handler(s->vq, s->ctx, false, false);
>> + virtio_queue_aio_set_host_notifier_handler(s->vq, s->ctx, true, false);
>>
>> /* Drain and switch bs back to the QEMU main loop */
>> blk_set_aio_context(s->conf->conf.blk, qemu_get_aio_context());
>>
>
> Right. Tu Bo, you seem to have the best testcase for this.
> Does your setup runs fine with this on top?
>
> CHristian
>
next prev parent reply other threads:[~2016-03-31 5:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 16:15 [Qemu-devel] [PATCH 0/6] virtio: refactor host notifiers Cornelia Huck
2016-03-24 16:15 ` [Qemu-devel] [PATCH 1/6] virtio-bus: common ioeventfd infrastructure Cornelia Huck
2016-03-24 16:15 ` [Qemu-devel] [PATCH 2/6] virtio-bus: have callers tolerate new host notifier api Cornelia Huck
2016-03-24 16:15 ` [Qemu-devel] [PATCH 3/6] virtio-ccw: convert to ioeventfd callbacks Cornelia Huck
2016-03-24 16:15 ` [Qemu-devel] [PATCH 4/6] virtio-pci: " Cornelia Huck
2016-03-24 16:15 ` [Qemu-devel] [PATCH 5/6] virtio-mmio: " Cornelia Huck
2016-03-24 16:15 ` [Qemu-devel] [PATCH 6/6] virtio-bus: remove old set_host_notifier callback Cornelia Huck
2016-03-24 17:06 ` [Qemu-devel] [PATCH 0/6] virtio: refactor host notifiers Paolo Bonzini
2016-03-29 8:18 ` Cornelia Huck
2016-03-29 9:15 ` Paolo Bonzini
2016-03-25 9:52 ` Fam Zheng
2016-03-28 3:55 ` TU BO
2016-03-28 18:11 ` Paolo Bonzini
2016-03-29 9:14 ` tu bo
2016-03-29 11:45 ` Cornelia Huck
2016-03-29 13:50 ` Paolo Bonzini
2016-03-29 16:27 ` Christian Borntraeger
2016-03-31 2:37 ` tu bo
2016-03-31 5:47 ` tu bo [this message]
2016-03-29 11:54 ` Christian Borntraeger
2016-03-31 2:47 ` tu bo
2016-03-29 13:23 ` Christian Borntraeger
2016-03-29 13:38 ` Michael S. Tsirkin
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=56FCBA02.6080304@linux.vnet.ibm.com \
--to=tubo@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=famz@redhat.com \
--cc=mst@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).