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>,
"Pasha Tatashin" <pasha.tatashin@soleen.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, devel@daynix.com,
Yui Washizu <yui.washidu@gmail.com>,
Akihiko Odaki <akihiko.odaki@daynix.com>
Subject: [PATCH for-10.1 v9 4/9] pcie_sriov: Check PCI Express for SR-IOV PF
Date: Fri, 14 Mar 2025 15:14:53 +0900 [thread overview]
Message-ID: <20250314-sriov-v9-4-57dae8ae3ab5@daynix.com> (raw)
In-Reply-To: <20250314-sriov-v9-0-57dae8ae3ab5@daynix.com>
SR-IOV requires PCI Express.
Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
---
hw/pci/pcie_sriov.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/hw/pci/pcie_sriov.c b/hw/pci/pcie_sriov.c
index 109b2ebcccba..a5b546abe8bb 100644
--- a/hw/pci/pcie_sriov.c
+++ b/hw/pci/pcie_sriov.c
@@ -42,6 +42,11 @@ bool pcie_sriov_pf_init(PCIDevice *dev, uint16_t offset,
uint8_t *cfg = dev->config + offset;
uint8_t *wmask;
+ if (!pci_is_express(dev)) {
+ error_setg(errp, "PCI Express is required for SR-IOV PF");
+ return false;
+ }
+
if (pci_is_vf(dev)) {
error_setg(errp, "a device cannot be a SR-IOV PF and a VF at the same time");
return false;
--
2.48.1
next prev parent reply other threads:[~2025-03-14 6:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 6:14 [PATCH for-10.1 v9 0/9] virtio-net: add support for SR-IOV emulation Akihiko Odaki
2025-03-14 6:14 ` [PATCH for-10.1 v9 1/9] hw/pci: Do not add ROM BAR for SR-IOV VF Akihiko Odaki
2025-03-14 6:14 ` [PATCH for-10.1 v9 2/9] hw/pci: Fix SR-IOV VF number calculation Akihiko Odaki
2025-03-14 6:14 ` [PATCH for-10.1 v9 3/9] pcie_sriov: Ensure PF and VF are mutually exclusive Akihiko Odaki
2025-03-14 6:14 ` Akihiko Odaki [this message]
2025-03-14 6:14 ` [PATCH for-10.1 v9 5/9] pcie_sriov: Allow user to create SR-IOV device Akihiko Odaki
2025-03-14 6:14 ` [PATCH for-10.1 v9 6/9] virtio-pci: Implement SR-IOV PF Akihiko Odaki
2025-03-14 6:14 ` [PATCH for-10.1 v9 7/9] virtio-net: Implement SR-IOV VF Akihiko Odaki
2025-03-14 6:14 ` [PATCH for-10.1 v9 8/9] docs: Document composable SR-IOV device Akihiko Odaki
2025-03-14 6:14 ` [PATCH for-10.1 v9 9/9] pcie_sriov: Make a PCI device with user-created VF ARI-capable Akihiko Odaki
2025-03-21 4:34 ` [PATCH for-10.1 v9 0/9] virtio-net: add support for SR-IOV emulation Yui Washizu
2025-03-21 5:18 ` Akihiko Odaki
2025-03-21 5:38 ` Yui Washizu
2025-04-02 18:34 ` Pasha Tatashin
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=20250314-sriov-v9-4-57dae8ae3ab5@daynix.com \
--to=akihiko.odaki@daynix.com \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=devel@daynix.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=pasha.tatashin@soleen.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).