From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Alex Williamson <alex.williamson@redhat.com>, qemu-devel@nongnu.org
Cc: Jens Freimann <jfreimann@redhat.com>, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] pci: Sanity test minimum downstream LNKSTA
Date: Wed, 20 Feb 2019 11:10:22 +0200 [thread overview]
Message-ID: <f94524a1-8f11-f4df-19e7-8626ad34e98d@gmail.com> (raw)
In-Reply-To: <155060310248.19547.14979269067689441201.stgit@gimli.home>
On 2/19/19 9:06 PM, Alex Williamson wrote:
> The entire link status register for SR-IOV VFs is defined as RsvdZ,
> reads simply return zero. Usually this is nothing more than lspci
> reporting inconsequentially broken values:
>
> LnkSta: Speed unknown, Width x0, ...
>
> However, now that we're using the downstream endpoint link status to
> fill in the value at the parent downstream port, invalid values become
> a problem. In particular, the PCIe hotplug driver in Linux looks for
> a valid negotiated link width and will fail to enumerate hot-added
> downstream endpoints without non-zero value here, ex:
>
> pciehp 0000:00:02.0:pcie004: Slot(0): Attention button pressed
> pciehp 0000:00:02.0:pcie004: Slot(0) Powering on due to button press
> pciehp 0000:00:02.0:pcie004: Slot(0): Card present
> pciehp 0000:00:02.0:pcie004: Slot(0): Link Up
> pciehp 0000:00:02.0:pcie004: link training error: status 0x2000
> pciehp 0000:00:02.0:pcie004: Failed to check link status
>
> Resolve by using minimum width and speed values for the downstream
> port link status when the endpoint fails to provide valid values.
> Long term, we may want to implement emulation in the vfio-pci host
> driver to suppliment this field with the PF value as the SR-IOV spec
> seems to allow, but the solution here is compatible should that be
> implemented later.
>
> Fixes: 727b48661f75 ("pci: Sync PCIe downstream port LNKSTA on read")
> Reported-by: Jens Freimann <jfreimann@redhat.com>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
> hw/pci/pcie.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/hw/pci/pcie.c b/hw/pci/pcie.c
> index 3f7c36609313..3618d6ab2e1a 100644
> --- a/hw/pci/pcie.c
> +++ b/hw/pci/pcie.c
> @@ -834,9 +834,12 @@ void pcie_add_capability(PCIDevice *dev,
> /*
> * Sync the PCIe Link Status negotiated speed and width of a bridge with the
> * downstream device. If downstream device is not present, re-write with the
> - * Link Capability fields. Limit width and speed to bridge capabilities for
> - * compatibility. Use config_read to access the downstream device since it
> - * could be an assigned device with volatile link information.
> + * Link Capability fields. If downstream device reports invalid width or
> + * speed, replace with minimum values (LnkSta fields are RsvdZ on VFs but such
> + * values interfere with PCIe native hotplug detecting new devices). Limit
> + * width and speed to bridge capabilities for compatibility. Use config_read
> + * to access the downstream device since it could be an assigned device with
> + * volatile link information.
> */
> void pcie_sync_bridge_lnk(PCIDevice *bridge_dev)
> {
> @@ -856,11 +859,15 @@ void pcie_sync_bridge_lnk(PCIDevice *bridge_dev)
> if ((lnksta & PCI_EXP_LNKSTA_NLW) > (lnkcap & PCI_EXP_LNKCAP_MLW)) {
> lnksta &= ~PCI_EXP_LNKSTA_NLW;
> lnksta |= lnkcap & PCI_EXP_LNKCAP_MLW;
> + } else if (!(lnksta & PCI_EXP_LNKSTA_NLW)) {
> + lnksta |= QEMU_PCI_EXP_LNKSTA_NLW(QEMU_PCI_EXP_LNK_X1);
> }
>
> if ((lnksta & PCI_EXP_LNKSTA_CLS) > (lnkcap & PCI_EXP_LNKCAP_SLS)) {
> lnksta &= ~PCI_EXP_LNKSTA_CLS;
> lnksta |= lnkcap & PCI_EXP_LNKCAP_SLS;
> + } else if (!(lnksta & PCI_EXP_LNKSTA_CLS)) {
> + lnksta |= QEMU_PCI_EXP_LNKSTA_CLS(QEMU_PCI_EXP_LNK_2_5GT);
> }
> }
>
>
Reviewed-by: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Thanks,
Marcel
prev parent reply other threads:[~2019-02-20 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 19:06 [Qemu-devel] [PATCH] pci: Sanity test minimum downstream LNKSTA Alex Williamson
2019-02-19 21:31 ` Jens Freimann
2019-02-20 9:10 ` Marcel Apfelbaum [this message]
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=f94524a1-8f11-f4df-19e7-8626ad34e98d@gmail.com \
--to=marcel.apfelbaum@gmail.com \
--cc=alex.williamson@redhat.com \
--cc=jfreimann@redhat.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).