public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Avi Kivity <avi@redhat.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	virtualization@lists.linux-foundation.org,
	Anthony Liguori <anthony@codemonkey.ws>,
	kvm@vger.kernel.org
Subject: Re: [PATCH RFC 0/8] virtio: add guest MSI-X support
Date: Mon, 27 Apr 2009 20:19:17 +0300	[thread overview]
Message-ID: <20090427171917.GC2276@redhat.com> (raw)
In-Reply-To: <200904271859.53190.borntraeger@de.ibm.com>

On Mon, Apr 27, 2009 at 06:59:52PM +0200, Christian Borntraeger wrote:
> Am Monday 27 April 2009 17:39:36 schrieb Michael S. Tsirkin:
> > So we'll probably need to rename request_vqs to request_vectors,
> > but we probably still need the driver to pass the number of
> > vectors it wants to the transport. Right?
> 
> This might be a stupid idea, but would something like the following
> be sufficient for you?

Yes.

> Index: linux-2.6/drivers/net/virtio_net.c
> ===================================================================
> --- linux-2.6.orig/drivers/net/virtio_net.c
> +++ linux-2.6/drivers/net/virtio_net.c
> @@ -1021,6 +1021,7 @@ static unsigned int features[] = {
>  static struct virtio_driver virtio_net = {
>         .feature_table = features,
>         .feature_table_size = ARRAY_SIZE(features),
> +       .num_vq_max = 3,
>         .driver.name =  KBUILD_MODNAME,
>         .driver.owner = THIS_MODULE,
>         .id_table =     id_table,
> Index: linux-2.6/include/linux/virtio.h
> ===================================================================
> --- linux-2.6.orig/include/linux/virtio.h
> +++ linux-2.6/include/linux/virtio.h
> @@ -110,6 +110,7 @@ struct virtio_driver {
>         const struct virtio_device_id *id_table;
>         const unsigned int *feature_table;
>         unsigned int feature_table_size;
> +       unsigned int num_vq_max;
>         int (*probe)(struct virtio_device *dev);
>         void (*remove)(struct virtio_device *dev);
>         void (*config_changed)(struct virtio_device *dev);

Good idea.

-- 
MST

  reply	other threads:[~2009-04-27 17:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 12:31 [PATCH RFC 0/8] virtio: add guest MSI-X support Michael S. Tsirkin
2009-04-27 14:00 ` Christian Borntraeger
2009-04-27 14:32   ` Michael S. Tsirkin
2009-04-27 15:37     ` Christian Borntraeger
2009-04-27 17:17       ` Michael S. Tsirkin
2009-04-27 15:06   ` Avi Kivity
2009-04-27 15:39     ` Michael S. Tsirkin
2009-04-27 16:59       ` Christian Borntraeger
2009-04-27 17:19         ` Michael S. Tsirkin [this message]
2009-04-28  6:47       ` Avi Kivity
2009-04-28 17:41         ` Michael S. Tsirkin
2009-04-28 17:51           ` Avi Kivity
2009-04-28 18:02             ` Michael S. Tsirkin
2009-04-28 19:56               ` Anthony Liguori
2009-04-28 21:01                 ` Michael S. Tsirkin
2009-05-04  9:21               ` Avi Kivity
2009-05-04 11:54                 ` Michael S. Tsirkin
2009-05-04 11:57                   ` Avi Kivity
2009-04-27 14:39 ` Anthony Liguori
2009-04-27 17:42   ` 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=20090427171917.GC2276@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --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