From: <Erin_Tsao@wistron.com>
To: <mj@ucw.cz>
Cc: <linux-pci@vger.kernel.org>
Subject: RE: Issue about PCI physical slot fetch incorrect number
Date: Mon, 26 Aug 2024 09:05:21 +0000 [thread overview]
Message-ID: <706e4367f1724a9cad739a1b88618791@wistron.com> (raw)
In-Reply-To: <mj+md-20240823.185024.10254.nikam@ucw.cz>
Hi Martin,
Thanks for helping me forwarding the mail.
Hope to have good news from them.
Wish you have a good day!
BR,
Erin
-----Original Message-----
From: Martin Mareš <mj@ucw.cz>
Sent: Saturday, August 24, 2024 2:52 AM
To: Erin Tsao/WHQ/Wistron <Erin_Tsao@wistron.com>
Cc: Linux-PCI Mailing List <linux-pci@vger.kernel.org>
Subject: Re: Issue about PCI physical slot fetch incorrect number
Hi!
> This is Erin from Taiwan. I have a question about physical slot number.
> Currently we are working on the PCIE slot number assigning by PCIE switch. In the PCIe slot assignment process, the slot numbers are assigned to bridges first, and then the end devices fetch the slot ID from the bridge in the upper layer.
>
> I have observed that under our PCIE switch, GPUs will create a bridge before reaching the end device. If GPUs also fetch the slot ID from the upper bridge layer, they may retrieve incorrect values.
>
> Our GPU will get the physical slot number with number “0”, and show the slot number “0”、”0-1” , etc.
> May I ask
>
> 1. Why GPU will fetch the slot number “0”? Is the slot number assigned to GPU related to any register? Or can we set any bit to fetch the right number?
> 2. Is there any possible for us not to show the physical slot number of GPU?
>
> I have checked with the code on the git, unfortunately I didn’t obtain any answer.
> It will really be helpful to get the response from you.
> Hope to hear from you soon, thanks in advance.
It's a long long time since I was the maintainer of the PCI layer in the kernel. Now I maintain just the PCI utilities which display whatever the kernel tells them.
I am forwarding your question to the linux-pci mailing list where it hopefully finds a better audience.
Martin
---------------------------------------------------------------------------------------------------------------------------------------------------------------
This email contains confidential or legally privileged information and is for the sole use of its intended recipient.
Any unauthorized review, use, copying or distribution of this email or the content of this email is strictly prohibited.
If you are not the intended recipient, you may reply to the sender and should delete this e-mail immediately.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
prev parent reply other threads:[~2024-08-26 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a600fc09c06d4ca28b045668ad1e63cb@wistron.com>
2024-08-23 18:51 ` Issue about PCI physical slot fetch incorrect number Martin Mareš
2024-08-23 21:03 ` Bjorn Helgaas
2024-08-26 8:27 ` Erin_Tsao
2024-08-29 16:35 ` Bjorn Helgaas
2024-09-06 2:04 ` Erin_Tsao
2024-09-18 14:09 ` Bjorn Helgaas
2024-08-26 9:05 ` Erin_Tsao [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=706e4367f1724a9cad739a1b88618791@wistron.com \
--to=erin_tsao@wistron.com \
--cc=linux-pci@vger.kernel.org \
--cc=mj@ucw.cz \
/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