qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/6] virtio: handle non contigious s/g entries
Date: Wed, 28 Oct 2015 13:30:59 +0100	[thread overview]
Message-ID: <20151028133059.4188383f@nial.brq.redhat.com> (raw)
In-Reply-To: <20151027134918-mutt-send-email-mst@redhat.com>

On Tue, 27 Oct 2015 13:51:20 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Tue, Oct 27, 2015 at 10:47:54AM +0200, Michael S. Tsirkin wrote:
> > TL;DR:
> > This fixes virtio in a way transparent to guest.
> > We should now be able to revert commits aa8580cd and df0acded19ec which worked
> > around it in a way that's not transparent.
> 
> I didn't check dataplane BTW. Igor? Stefan?
verified that series fixes virtio-[blk|scsi|net], all of them
hit at least one descriptor(indirect) that crosses DIMM boundary
and QEMU survived it.

However as Stefan has said virtio-blk with dataplane enabled hangs
guest instead of QEMU crashing and QEMU prints following error:

"Failed to map descriptor addr 0x1045eb000 len 106496"

I've used following CLI:
qemu-system-x86_64 -enable-kvm -enable-kvm  -m 128M,slots=250,maxmem=32G  -drive if=none,id=hd,file=rhel72.img,cache=none,aio=native,format=raw -device virtio-blk,drive=hd,scsi=off,config-wce=off,x-data-plane=on `for i in $(seq 0 15); do echo -n "-object memory-backend-ram,id=m$i,size=10M -device pc-dimm,id=dimm$i,memdev=m$i "; done`

it hangs at boot time or on executing 'dd if=/dev/vda of=/dev/null bs 32M'

  parent reply	other threads:[~2015-10-28 12:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27  8:47 [Qemu-devel] [PATCH 0/6] virtio: handle non contigious s/g entries Michael S. Tsirkin
2015-10-27  8:47 ` [Qemu-devel] [PATCH 1/6] virtio: introduce virtio_map Michael S. Tsirkin
2015-10-27 16:13   ` Stefan Hajnoczi
2015-10-27 18:38     ` Michael S. Tsirkin
2015-10-27 16:19   ` Stefan Hajnoczi
2015-10-27 18:34     ` Michael S. Tsirkin
2015-10-28 11:37       ` Stefan Hajnoczi
2015-10-28 12:16   ` Igor Mammedov
2015-10-28 13:11   ` Igor Mammedov
2015-10-27  8:47 ` [Qemu-devel] [PATCH 2/6] virtio: switch to virtio_map Michael S. Tsirkin
2015-10-28 13:02   ` Igor Mammedov
2015-10-27  8:48 ` [Qemu-devel] [PATCH 3/6] virtio-blk: convert to virtqueue_map Michael S. Tsirkin
2015-10-28 13:02   ` Igor Mammedov
2015-10-27  8:48 ` [Qemu-devel] [PATCH 4/6] virtio-serial: convert to virtio_map Michael S. Tsirkin
2015-10-28 13:03   ` Igor Mammedov
2015-10-27  8:48 ` [Qemu-devel] [PATCH 5/6] virtio-scsi: convert to virtqueue_map Michael S. Tsirkin
2015-10-28 13:03   ` Igor Mammedov
2015-10-27  8:48 ` [Qemu-devel] [PATCH 6/6] virtio: drop virtqueue_map_sg Michael S. Tsirkin
2015-10-28 13:04   ` Igor Mammedov
2015-10-27  8:50 ` [Qemu-devel] [PATCH 0/6] virtio: handle non contigious s/g entries Michael S. Tsirkin
2015-10-27 11:51 ` Michael S. Tsirkin
2015-10-27 16:24   ` Stefan Hajnoczi
2015-10-28 12:30   ` Igor Mammedov [this message]
2015-10-27 12:06 ` Cornelia Huck

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=20151028133059.4188383f@nial.brq.redhat.com \
    --to=imammedo@redhat.com \
    --cc=mst@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).