From: Anthony Liguori <aliguori@us.ibm.com>
To: dor.laor@qumranet.com
Cc: Rusty Russell <rusty@rustcorp.com.au>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 3/3] virtio block device
Date: Tue, 04 Dec 2007 18:12:26 -0600 [thread overview]
Message-ID: <4755ECEA.6060209@us.ibm.com> (raw)
In-Reply-To: <4755E810.4000106@qumranet.com>
Dor Laor wrote:
> Anthony Liguori wrote:
>
> Subject: [PATCH 3/3] virtio block device
> +
> +static void virtio_blk_handle_output(VirtIODevice *vdev, VirtQueue *vq)
> +{
> + VirtIOBlock *s = to_virtio_blk(vdev);
> + VirtQueueElement elem;
> + unsigned int count;
> +
> + while ((count = virtqueue_pop(vq, &elem)) != 0) {
> + struct virtio_blk_inhdr *in;
> + struct virtio_blk_outhdr *out;
> + unsigned int wlen;
> + off_t off;
> + int i;
> +
> + out = (void *)elem.out_sg[0].iov_base;
> + in = (void *)elem.in_sg[elem.in_num - 1].iov_base;
> + off = out->sector;
> +
> + if (out->type & VIRTIO_BLK_T_SCSI_CMD) {
> + wlen = sizeof(*in);
> + in->status = VIRTIO_BLK_S_UNSUPP;
> + } else if (out->type & VIRTIO_BLK_T_OUT) {
> + wlen = sizeof(*in);
> +
> + for (i = 1; i < elem.out_num; i++) {
> + bdrv_write(s->bs, off,
> + elem.out_sg[i].iov_base,
> + elem.out_sg[i].iov_len / 512);
> + off += elem.out_sg[i].iov_len / 512;
> + }
> +
> + in->status = VIRTIO_BLK_S_OK;
> + } else {
> + wlen = sizeof(*in);
> +
> + for (i = 0; i < elem.in_num - 1; i++) {
> + bdrv_read(s->bs, off,
> + elem.in_sg[i].iov_base,
> + elem.in_sg[i].iov_len / 512);
> + off += elem.in_sg[i].iov_len / 512;
> + wlen += elem.in_sg[i].iov_len;
> + }
> +
> + in->status = VIRTIO_BLK_S_OK;
> + }
> +
> + virtqueue_push(vq, &elem, wlen);
> + virtio_notify(vdev, vq);
> + }
>
>
>
> The notify here should also be outside the while loop.
>
Yeah, that's in the optimization patch.
> ===================================================================
> --- qemu.orig/sysemu.h 2007-12-04 13:51:49.000000000 -0600
> +++ qemu/sysemu.h 2007-12-04 14:18:57.000000000 -0600
> @@ -117,7 +117,7 @@
> #endif
>
> typedef enum {
> - IF_IDE, IF_SCSI, IF_FLOPPY, IF_PFLASH, IF_MTD, IF_SD
> + IF_IDE, IF_SCSI, IF_FLOPPY, IF_PFLASH, IF_MTD, IF_SD, IF_VIRTIO
> } BlockInterfaceType;
>
> typedef struct DriveInfo {
> Index: qemu/hw/pc.c
> ===================================================================
> --- qemu.orig/hw/pc.c 2007-12-04 13:51:49.000000000 -0600
> +++ qemu/hw/pc.c 2007-12-04 14:18:57.000000000 -0600
> @@ -1008,6 +1008,18 @@
> }
> }
> }
> +
> + /* Add virtio block devices */
> + if (pci_enabled) {
> + int index;
> + int unit_id = 0;
> +
> + while ((index = drive_get_index(IF_VIRTIO, 0, unit_id)) != -1) {
> + virtio_blk_init(pci_bus, 0x5002, 0x2258,
>
>
>
>
> The pci vendor id should be identical to the network (0x6900)
>
Indeed! That's for catching that.
Regards,
Anthony Liguori
> regards,
> Dor.
>
>
prev parent reply other threads:[~2007-12-05 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 21:54 [Qemu-devel] [PATCH 3/3] virtio block device Anthony Liguori
2007-12-04 23:51 ` [Qemu-devel] " Dor Laor
2007-12-05 0:12 ` Anthony Liguori [this message]
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=4755ECEA.6060209@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=dor.laor@qumranet.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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).