From: Sebastian Ott <sebott@redhat.com>
To: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
"Michael S . Tsirkin" <mst@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, Zhenyu Zhang <zhenyzha@redhat.com>
Subject: Re: [PATCH v2] pci: ensure valid link status bits for downstream ports
Date: Tue, 17 Dec 2024 16:52:57 +0100 (CET) [thread overview]
Message-ID: <6a741fa5-8e6f-1c11-9879-378bbbd56c75@redhat.com> (raw)
In-Reply-To: <20241203072809.3431fe80.alex.williamson@redhat.com>
Hi,
On Tue, 3 Dec 2024, Alex Williamson wrote:
> On Tue, 3 Dec 2024 13:19:28 +0100
> Sebastian Ott <sebott@redhat.com> wrote:
>
>> PCI hotplug for downstream endpoints on arm fails because Linux'
>> PCIe hotplug driver doesn't like the QEMU provided LNKSTA:
>>
>> pcieport 0000:08:01.0: pciehp: Slot(2): Card present
>> pcieport 0000:08:01.0: pciehp: Slot(2): Link Up
>> pcieport 0000:08:01.0: pciehp: Slot(2): Cannot train link: status 0x2000
>>
>> There's 2 cases where LNKSTA isn't setup properly:
>> * the downstream device has no express capability
>> * max link width of the bridge is 0
>>
>> Move the sanity checks added via 88c869198aa63
>> ("pci: Sanity test minimum downstream LNKSTA") outside of the
>> branch to make sure downstream ports always have a valid LNKSTA.
>>
>> Signed-off-by: Sebastian Ott <sebott@redhat.com>
>> Tested-by: Zhenyu Zhang <zhenyzha@redhat.com>
>> ---
>> hw/pci/pcie.c | 12 ++++++++----
>> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> Reviewed-by: Alex Williamson <alex.williamson@redhat.com>
Can someone pick this up for the next qemu release?
Thanks,
Sebastian
next prev parent reply other threads:[~2024-12-17 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 12:19 [PATCH v2] pci: ensure valid link status bits for downstream ports Sebastian Ott
2024-12-03 14:28 ` Alex Williamson
2024-12-17 15:52 ` Sebastian Ott [this message]
2025-01-07 16:48 ` Sebastian Ott
2025-01-17 6:21 ` Michael Tokarev
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=6a741fa5-8e6f-1c11-9879-378bbbd56c75@redhat.com \
--to=sebott@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhenyzha@redhat.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).