From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: Ani Sinha <anisinha@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Cc: jusual@redhat.com, imammedo@redhat.com
Subject: Re: [PATCH v7 5/6] hw/pci: ensure PCIE devices are plugged into only slot 0 of PCIE port
Date: Tue, 4 Jul 2023 20:54:45 +0900 [thread overview]
Message-ID: <7356dc51-588c-f2f8-22d9-c8193bae9309@daynix.com> (raw)
In-Reply-To: <20230704112555.5629-6-anisinha@redhat.com>
On 2023/07/04 20:25, Ani Sinha wrote:
> PCI Express ports only have one slot, so PCI Express devices can only be
> plugged into slot 0 on a PCIE port. Add a warning to let users know when the
> invalid configuration is used. We may enforce this more strongly later on once
> we get more clarity on whether we are introducing a bad regression for users
> currenly using the wrong configuration.
>
> The change has been tested to not break or alter behaviors of ARI capable
> devices by instantiating seven vfs on an emulated igb device (the maximum
> number of vfs the linux igb driver supports). The vfs instantiated correctly
> and are seen to have non-zero device/slot numbers in the conventional PCI BDF
> representation.
>
> CC: jusual@redhat.com
> CC: imammedo@redhat.com
> CC: mst@redhat.com
> CC: akihiko.odaki@daynix.com
>
> Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2128929
> Signed-off-by: Ani Sinha <anisinha@redhat.com>
> Reviewed-by: Julia Suvorova <jusual@redhat.com>
> ---
> hw/pci/pci.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/hw/pci/pci.c b/hw/pci/pci.c
> index e2eb4c3b4a..47517ba3db 100644
> --- a/hw/pci/pci.c
> +++ b/hw/pci/pci.c
> @@ -65,6 +65,7 @@ bool pci_available = true;
> static char *pcibus_get_dev_path(DeviceState *dev);
> static char *pcibus_get_fw_dev_path(DeviceState *dev);
> static void pcibus_reset(BusState *qbus);
> +static bool pcie_has_upstream_port(PCIDevice *dev);
>
> static Property pci_props[] = {
> DEFINE_PROP_PCI_DEVFN("addr", PCIDevice, devfn, -1),
> @@ -2121,6 +2122,20 @@ static void pci_qdev_realize(DeviceState *qdev, Error **errp)
> }
> }
>
> + /*
> + * With SRIOV and ARI, vfs can have non-zero slot in the conventional
> + * PCI interpretation as all five bits reserved for slot addresses are
> + * also used for function bits for the various vfs. Ignore that case.
You don't have to mention SR/IOV; it affects all ARI-capable devices. A
PF can also have non-zero slot number in the conventional interpretation
so you shouldn't call it vf either.
> + */
> + if (pci_is_express(pci_dev) &&
> + !pcie_find_capability(pci_dev, PCI_EXT_CAP_ID_ARI) &&
> + pcie_has_upstream_port(pci_dev) &&
> + PCI_SLOT(pci_dev->devfn)) {
> + warn_report("PCI: slot %d is not valid for %s,"
> + " parent device only allows plugging into slot 0.",
> + PCI_SLOT(pci_dev->devfn), pci_dev->name);
> + }
> +
> if (pci_dev->failover_pair_id) {
> if (!pci_bus_is_express(pci_get_bus(pci_dev))) {
> error_setg(errp, "failover primary device must be on "
next prev parent reply other threads:[~2023-07-04 11:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 11:25 [PATCH v7 0/6] test and QEMU fixes to ensure proper PCIE device usage Ani Sinha
2023-07-04 11:25 ` [PATCH v7 1/6] tests/acpi: allow changes in DSDT.noacpihp table blob Ani Sinha
2023-07-04 11:25 ` [PATCH v7 2/6] tests/acpi/bios-tables-test: use the correct slot on the pcie-root-port Ani Sinha
2023-07-04 11:25 ` [PATCH v7 3/6] tests/acpi/bios-tables-test: update acpi blob q35/DSDT.noacpihp Ani Sinha
2023-07-04 11:25 ` [PATCH v7 4/6] tests/qtest/hd-geo-test: fix incorrect pcie-root-port usage and simplify test Ani Sinha
2023-07-04 11:25 ` [PATCH v7 5/6] hw/pci: ensure PCIE devices are plugged into only slot 0 of PCIE port Ani Sinha
2023-07-04 11:38 ` Ani Sinha
2023-07-04 11:54 ` Akihiko Odaki [this message]
2023-07-04 11:59 ` Ani Sinha
2023-07-04 12:02 ` Akihiko Odaki
2023-07-04 12:08 ` Ani Sinha
2023-07-04 12:09 ` Akihiko Odaki
2023-07-04 12:28 ` Ani Sinha
2023-07-04 12:48 ` Igor Mammedov
2023-07-04 13:50 ` Ani Sinha
2023-07-04 14:28 ` Igor Mammedov
2023-07-04 15:07 ` Ani Sinha
2023-07-05 1:39 ` Akihiko Odaki
2023-07-05 5:43 ` Ani Sinha
2023-07-05 10:42 ` Akihiko Odaki
2023-07-04 11:25 ` [PATCH v7 6/6] hw/pci: add comment explaining the reason for checking function 0 in hotplug Ani Sinha
2023-07-04 12:15 ` Igor Mammedov
2023-07-04 12:31 ` Ani Sinha
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=7356dc51-588c-f2f8-22d9-c8193bae9309@daynix.com \
--to=akihiko.odaki@daynix.com \
--cc=anisinha@redhat.com \
--cc=imammedo@redhat.com \
--cc=jusual@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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).