All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 6/7] virtio-blk: Unify {non-, }dataplane's request handlings
Date: Tue, 01 Jul 2014 13:29:36 +0200	[thread overview]
Message-ID: <53B29BA0.4080603@redhat.com> (raw)
In-Reply-To: <1402986730-25642-7-git-send-email-famz@redhat.com>

On 17.06.2014 08:32, Fam Zheng wrote:
> This drops request handling code from dataplane, and uses code from
> hw/block/virtio-blk.c.
>
> It starts to use multiwrite as non-dataplane does.
>
> Dataplane sets VirtIOBlock.complete_request to vring version, and calls
> into non-dataplane's process handling. In complete_request_early,
> qiov.size is added to vring push length, because it's also called in rw
> completion now.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
>   hw/block/dataplane/virtio-blk.c | 183 +++++-----------------------------------
>   1 file changed, 19 insertions(+), 164 deletions(-)

Is it intended that qemu segfaults after this commit with x-data-plane=on?

$ ./qemu-img create -f qcow2 test.qcow2 64M
$ x86_64-softmmu/qemu-system-x86_64 -drive 
if=none,file=test.qcow2,id=drv0 -device 
virtio-blk-pci,drive=drv0,x-data-plane=on
[1]    4604 segmentation fault  x86_64-softmmu/qemu-system-x86_64 -drive 
if=none,file=test.qcow2,id=drv0

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd75ff700 (LWP 5217)]
0x00005555556373af in virtio_blk_rw_complete (opaque=0x5555565ff5e0, 
ret=0) at hw/block/virtio-blk.c:99
99          bdrv_acct_done(req->dev->bs, &req->acct);
(gdb) print req
$1 = (VirtIOBlockReq *) 0x5555565ff5e0
(gdb) print req->dev
$2 = (VirtIOBlock *) 0x0
(gdb) bt
#0  0x00005555556373af in virtio_blk_rw_complete (opaque=0x5555565ff5e0, 
ret=0) at hw/block/virtio-blk.c:99
#1  0x0000555555840ebe in bdrv_co_em_bh (opaque=0x5555566152d0) at 
block.c:4675
#2  0x000055555583de77 in aio_bh_poll (ctx=ctx@entry=0x5555563a8150) at 
async.c:81
#3  0x000055555584b7a7 in aio_poll (ctx=0x5555563a8150, 
blocking=blocking@entry=true) at aio-posix.c:188
#4  0x00005555556e520e in iothread_run (opaque=0x5555563a7fd8) at 
iothread.c:41
#5  0x00007ffff42ba124 in start_thread () from /usr/lib/libpthread.so.0
#6  0x00007ffff16d14bd in clone () from /usr/lib/libc.so.6

Max

  reply	other threads:[~2014-07-01 11:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17  6:32 [Qemu-devel] [PATCH v2 0/7] virtio-blk: Unify request handling of dataplane Fam Zheng
2014-06-17  6:32 ` [Qemu-devel] [PATCH v2 1/7] block: make bdrv_query_stats() static Fam Zheng
2014-06-17  6:32 ` [Qemu-devel] [PATCH v2 2/7] block: acquire AioContext in qmp_query_blockstats() Fam Zheng
2014-06-17  6:32 ` [Qemu-devel] [PATCH v2 3/7] virtio-blk: Make request completion function virtual Fam Zheng
2014-06-17  6:32 ` [Qemu-devel] [PATCH v2 4/7] virtio-blk: Export request handling functions to dataplane Fam Zheng
2014-06-17  6:32 ` [Qemu-devel] [PATCH v2 5/7] virtio-blk: Schedule BH in the right context Fam Zheng
2014-06-17  6:32 ` [Qemu-devel] [PATCH v2 6/7] virtio-blk: Unify {non-, }dataplane's request handlings Fam Zheng
2014-07-01 11:29   ` Max Reitz [this message]
2014-07-01 13:22     ` Stefan Hajnoczi
2014-06-17  6:32 ` [Qemu-devel] [PATCH v2 7/7] virtio-blk: Rename complete_request_early to complete_request_vring Fam Zheng
2014-06-17  8:53 ` [Qemu-devel] [PATCH v2 0/7] virtio-blk: Unify request handling of dataplane Paolo Bonzini
2014-06-27 16:01 ` Stefan Hajnoczi
2014-06-27 16:21   ` Kevin Wolf

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=53B29BA0.4080603@redhat.com \
    --to=mreitz@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.