qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Asias He <asias@redhat.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Nicholas Bellinger <nab@linux-iscsi.org>,
	virtualization@lists.linux-foundation.org,
	target-devel@vger.kernel.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V2 WIP 0/2] vhost-scsi: new device supporting the tcm_vhost Linux kernel module
Date: Thu, 14 Mar 2013 12:25:14 +0800	[thread overview]
Message-ID: <20130314042514.GA28504@hj.localdomain> (raw)
In-Reply-To: <1363069782-10735-1-git-send-email-asias@redhat.com>

On Tue, Mar 12, 2013 at 02:29:40PM +0800, Asias He wrote:
> This is on top of Paolo and Nick's work.
> 
> Current status:
> Works now (guest boots fine, no hang any more) with seabios's virtio-scsi disabled.
> Rebased to latest qemu.org/master
> Change details are in commit log.
> 
> TODO:
> Make seabios happy.

Some updates:

In seabios, src/virtio-scsi.c:virtio_scsi_cmd()

    vring_kick(ioaddr, vq, 1);
    /* Wait for reply */
    while (!vring_more_used(vq))  ------------>>> we hang here
        usleep(5);

In tcm_vhost:
we got: vhost_get_vq_desc: head: -14, out: 0 in: 81216

The vring buffer provided by seabios is not correct?

> Paolo Bonzini (2):
>   virtio-scsi: create VirtIOSCSICommon
>   vhost-scsi: new device supporting the tcm_vhost Linux kernel module
> 
>  hw/Makefile.objs           |   5 +-
>  hw/s390x/s390-virtio-bus.c |  35 +++++++
>  hw/vhost-scsi.c            | 242 +++++++++++++++++++++++++++++++++++++++++++++
>  hw/vhost-scsi.h            |  64 ++++++++++++
>  hw/virtio-pci.c            |  59 +++++++++++
>  hw/virtio-scsi.c           | 199 +++++++++----------------------------
>  hw/virtio-scsi.h           | 129 ++++++++++++++++++++++++
>  include/qemu/osdep.h       |   4 +
>  8 files changed, 586 insertions(+), 151 deletions(-)
>  create mode 100644 hw/vhost-scsi.c
>  create mode 100644 hw/vhost-scsi.h
> 
> -- 
> 1.8.1.4
> 

-- 
Asias

  parent reply	other threads:[~2013-03-14  4:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12  6:29 [Qemu-devel] [PATCH V2 WIP 0/2] vhost-scsi: new device supporting the tcm_vhost Linux kernel module Asias He
2013-03-12  6:29 ` [Qemu-devel] [PATCH V2 WIP 1/2] virtio-scsi: create VirtIOSCSICommon Asias He
2013-03-12  6:29 ` [Qemu-devel] [PATCH V2 WIP 2/2] vhost-scsi: new device supporting the tcm_vhost Linux kernel module Asias He
2013-03-12  8:20   ` Stefan Hajnoczi
2013-03-13  2:49     ` Asias He
2013-03-14  4:25 ` Asias He [this message]
2013-03-14  9:25   ` [Qemu-devel] [PATCH V2 WIP 0/2] " Asias He
2013-03-14  9:46     ` Michael S. Tsirkin
2013-03-14 10:00       ` Paolo Bonzini
2013-03-14 10:21         ` Michael S. Tsirkin
2013-03-15  0:58         ` Asias He
2013-03-15  0:55       ` Asias He

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=20130314042514.GA28504@hj.localdomain \
    --to=asias@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=nab@linux-iscsi.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    --cc=stefanha@redhat.com \
    --cc=target-devel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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).