From: "Michael S. Tsirkin" <mst@redhat.com>
To: Julia Suvorova <jusual@redhat.com>
Cc: Ani Sinha <anisinha@redhat.com>,
qemu-devel@nongnu.org,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
imammedo@redhat.com
Subject: Re: [PATCH v2 5/5] hw/pci: ensure PCIE devices are plugged into only slot 0 of PCIE port
Date: Sun, 25 Jun 2023 17:11:37 -0400 [thread overview]
Message-ID: <20230625171058-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAMDeoFUAaRhN_hRHmTDfu6dWyiz_dNEhCJt9jQTVzeNSTbwuAg@mail.gmail.com>
On Fri, Jun 23, 2023 at 04:57:20PM +0200, Julia Suvorova wrote:
> On Thu, Jun 22, 2023 at 7:48 PM Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > On Thu, Jun 22, 2023 at 05:46:40PM +0200, Julia Suvorova wrote:
> > > On Thu, Jun 22, 2023 at 12:34 PM Ani Sinha <anisinha@redhat.com> wrote:
> > > >
> > > > PCI Express ports only have one slot, so PCI Express devices can only be
> > > > plugged into slot 0 on a PCIE port. Enforce it.
> > > >
> > > > CC: jusual@redhat.com
> > > > CC: imammedo@redhat.com
> > > > Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2128929
> > > > Signed-off-by: Ani Sinha <anisinha@redhat.com>
> > > > ---
> > > > hw/pci/pci.c | 6 ++++++
> > > > 1 file changed, 6 insertions(+)
> > > >
> > > > diff --git a/hw/pci/pci.c b/hw/pci/pci.c
> > > > index bf38905b7d..5f25ab9f5e 100644
> > > > --- a/hw/pci/pci.c
> > > > +++ b/hw/pci/pci.c
> > > > @@ -64,6 +64,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),
> > > > @@ -1189,6 +1190,11 @@ static PCIDevice *do_pci_register_device(PCIDevice *pci_dev,
> > > > name);
> > > >
> > > > return NULL;
> > > > + } else if (pcie_has_upstream_port(pci_dev) && PCI_SLOT(devfn)) {
> > > > + error_setg(errp, "PCI: slot %d is not valid for %s,"
> > > > + " PCI express devices can only be plugged into slot 0.",
> > >
> > > This is not technically correct, because downstream ports and root
> > > ports are also PCIe devices, and they can have different slots under
> > > upstream ports and RC. But this error will never be shown for them, so
> > > it seems fine.
> >
> > Hmm. Confusing users is not nice ... I agree this might
> > make people think they can not use root ports in slot !=0 either.
> >
> > Would you add "with an upstream port"?
> > E.g. "PCI Express devices with an upstream port" ?
>
> This whole upstream port conditioning is quite confusing.
> How about "%parent device% only allows plugging into slot 0"?
>
> Best regards, Julia Suvorova.
Good idea!
> > >
> > > Reviewed-by: Julia Suvorova <jusual@redhat.com>
> > >
> > >
> > >
> > >
> > > > + PCI_SLOT(devfn), name);
> > > > + return NULL;
> > > > }
> > > >
> > > > pci_dev->devfn = devfn;
> > > > --
> > > > 2.39.1
> > > >
> >
next prev parent reply other threads:[~2023-06-25 21:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 10:32 [PATCH v2 0/5] test and QEMU fixes to ensure proper PCIE device usage Ani Sinha
2023-06-22 10:32 ` [PATCH v2 1/5] tests/acpi: allow changes in DSDT.noacpihp table blob Ani Sinha
2023-06-22 10:32 ` [PATCH v2 2/5] tests/acpi/bios-tables-test: use the correct slot on the pcie-root-port Ani Sinha
2023-06-22 10:32 ` [PATCH v2 3/5] tests/acpi/bios-tables-test: update acpi blob q35/DSDT.noacpihp Ani Sinha
2023-06-22 10:32 ` [PATCH v2 4/5] tests/qtest/hd-geo-test: fix test by removing unnecessary pcie-root-port Ani Sinha
2023-06-26 11:15 ` Igor Mammedov
2023-06-26 11:31 ` Ani Sinha
2023-06-26 12:10 ` Igor Mammedov
2023-06-22 10:32 ` [PATCH v2 5/5] hw/pci: ensure PCIE devices are plugged into only slot 0 of PCIE port Ani Sinha
2023-06-22 15:46 ` Julia Suvorova
2023-06-22 17:48 ` Michael S. Tsirkin
2023-06-23 14:57 ` Julia Suvorova
2023-06-25 21:11 ` Michael S. Tsirkin [this message]
2023-06-26 7:49 ` 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=20230625171058-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=anisinha@redhat.com \
--cc=imammedo@redhat.com \
--cc=jusual@redhat.com \
--cc=marcel.apfelbaum@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.