From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paul Brook <paul@codesourcery.com>, Avi Kivity <avi@redhat.com>,
qemu-devel@nongnu.org, Carsten Otte <cotte@de.ibm.com>,
kvm@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>,
virtualization@lists.linux-foundation.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Blue Swirl <blauwirbel@gmail.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Glauber Costa <glommer@redhat.com>
Subject: [Qemu-devel] [PATCHv5 11/13] qemu: request 3 vectors in virtio-net
Date: Thu, 18 Jun 2009 16:15:26 +0300 [thread overview]
Message-ID: <20090618131526.GL19092@redhat.com> (raw)
In-Reply-To: <cover.1245330293.git.mst@redhat.com>
Request up to 3 vectors in virtio-net. Actual bindings might supply
less.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
hw/virtio-net.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/virtio-net.c b/hw/virtio-net.c
index d584287..c8dabbe 100644
--- a/hw/virtio-net.c
+++ b/hw/virtio-net.c
@@ -709,6 +709,7 @@ VirtIODevice *virtio_net_init(DeviceState *dev)
n->mac_table.macs = qemu_mallocz(MAC_TABLE_ENTRIES * ETH_ALEN);
n->vlans = qemu_mallocz(MAX_VLAN >> 3);
+ n->vdev.nvectors = 3;
register_savevm("virtio-net", virtio_net_id++, VIRTIO_NET_VM_VERSION,
virtio_net_save, virtio_net_load, n);
--
1.6.2.2
next prev parent reply other threads:[~2009-06-18 13:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1245330293.git.mst@redhat.com>
2009-06-18 13:12 ` [Qemu-devel] [PATCHv5 01/13] qemu: make default_write_config use mask table Michael S. Tsirkin
2009-06-18 13:13 ` [Qemu-devel] [PATCHv5 02/13] qemu: capability bits in pci save/restore Michael S. Tsirkin
2009-06-18 13:13 ` [Qemu-devel] [PATCHv5 03/13] qemu: add routines to manage PCI capabilities Michael S. Tsirkin
2009-06-18 13:13 ` [Qemu-devel] [PATCHv5 04/13] qemu: helper routines for pci access Michael S. Tsirkin
2009-06-18 13:13 ` [Qemu-devel] [PATCHv5 05/13] qemu: MSI-X support functions Michael S. Tsirkin
2009-06-18 13:14 ` [Qemu-devel] [PATCHv5 06/13] qemu: add flag to disable MSI-X by default Michael S. Tsirkin
2009-06-18 13:14 ` [Qemu-devel] [PATCHv5 07/13] qemu: minimal MSI/MSI-X implementation for PC Michael S. Tsirkin
2009-06-18 13:14 ` [Qemu-devel] [PATCHv5 08/13] qemu: add support for resizing regions Michael S. Tsirkin
2009-06-18 16:32 ` Paul Brook
2009-06-18 16:44 ` Michael S. Tsirkin
2009-06-18 13:14 ` [Qemu-devel] [PATCHv5 09/13] qemu: virtio support for many interrupt vectors Michael S. Tsirkin
2009-06-18 13:15 ` [Qemu-devel] [PATCHv5 10/13] qemu: MSI-X support in virtio PCI Michael S. Tsirkin
2009-06-18 13:15 ` Michael S. Tsirkin [this message]
2009-06-18 13:15 ` [Qemu-devel] [PATCHv5 12/13] qemu: virtio save/load bindings Michael S. Tsirkin
2009-06-18 13:15 ` [Qemu-devel] [PATCHv5 13/13] qemu: add pci_get/set_byte 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=20090618131526.GL19092@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).