From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Jason Wang" <jasowang@redhat.com>,
"Sriram Yagnaraman" <sriram.yagnaraman@ericsson.com>,
"Keith Busch" <kbusch@kernel.org>,
"Klaus Jensen" <its@irrelevant.dk>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Yui Washizu <yui.washidu@gmail.com>,
Akihiko Odaki <akihiko.odaki@daynix.com>
Subject: [PATCH for-9.2 v7 7/9] virtio-net: Implement SR-IOV VF
Date: Tue, 13 Aug 2024 15:37:06 +0900 [thread overview]
Message-ID: <20240813-sriov-v7-7-8515e3774df7@daynix.com> (raw)
In-Reply-To: <20240813-sriov-v7-0-8515e3774df7@daynix.com>
A virtio-net device can be added as a SR-IOV VF to another virtio-pci
device that will be the PF.
Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
---
hw/virtio/virtio-net-pci.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/virtio/virtio-net-pci.c b/hw/virtio/virtio-net-pci.c
index e03543a70a75..dba4987d6e04 100644
--- a/hw/virtio/virtio-net-pci.c
+++ b/hw/virtio/virtio-net-pci.c
@@ -75,6 +75,7 @@ static void virtio_net_pci_class_init(ObjectClass *klass, void *data)
k->device_id = PCI_DEVICE_ID_VIRTIO_NET;
k->revision = VIRTIO_PCI_ABI_VERSION;
k->class_id = PCI_CLASS_NETWORK_ETHERNET;
+ k->sriov_vf_user_creatable = true;
set_bit(DEVICE_CATEGORY_NETWORK, dc->categories);
device_class_set_props(dc, virtio_net_properties);
vpciklass->realize = virtio_net_pci_realize;
--
2.46.0
next prev parent reply other threads:[~2024-08-13 6:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 6:36 [PATCH for-9.2 v7 0/9] virtio-net: add support for SR-IOV emulation Akihiko Odaki
2024-08-13 6:37 ` [PATCH for-9.2 v7 1/9] hw/pci: Do not add ROM BAR for SR-IOV VF Akihiko Odaki
2024-08-13 6:37 ` [PATCH for-9.2 v7 2/9] hw/pci: Fix SR-IOV VF number calculation Akihiko Odaki
2024-08-13 6:37 ` [PATCH for-9.2 v7 3/9] pcie_sriov: Ensure PF and VF are mutually exclusive Akihiko Odaki
2024-08-13 6:37 ` [PATCH for-9.2 v7 4/9] pcie_sriov: Check PCI Express for SR-IOV PF Akihiko Odaki
2024-08-13 6:37 ` [PATCH for-9.2 v7 5/9] pcie_sriov: Allow user to create SR-IOV device Akihiko Odaki
2024-08-13 6:37 ` [PATCH for-9.2 v7 6/9] virtio-pci: Implement SR-IOV PF Akihiko Odaki
2024-08-13 6:37 ` Akihiko Odaki [this message]
2024-08-13 6:37 ` [PATCH for-9.2 v7 8/9] docs: Document composable SR-IOV device Akihiko Odaki
2024-08-13 6:37 ` [PATCH for-9.2 v7 9/9] pcie_sriov: Make a PCI device with user-created VF ARI-capable Akihiko Odaki
2024-08-21 10:18 ` [PATCH for-9.2 v7 0/9] virtio-net: add support for SR-IOV emulation Yui Washizu
2024-08-23 5:06 ` Akihiko Odaki
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=20240813-sriov-v7-7-8515e3774df7@daynix.com \
--to=akihiko.odaki@daynix.com \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=eduardo@habkost.net \
--cc=its@irrelevant.dk \
--cc=jasowang@redhat.com \
--cc=kbusch@kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sriram.yagnaraman@ericsson.com \
--cc=yui.washidu@gmail.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).