From: Ramesh Errabolu <Ramesh.Errabolu@amd.com>
To: <logang@deltatee.com>
Cc: <linux-pci@vger.kernel.org>, <ramesh.errabolu@gmail.com>
Subject: Understanding P2P DMA related errors
Date: Wed, 5 Oct 2022 21:56:53 -0500 [thread overview]
Message-ID: <20221006025653.3519854-1-Ramesh.Errabolu@amd.com> (raw)
In-Reply-To: <5d3b257a-c125-fdd6-e29f-229e54679f45@deltatee.com>
Logan,
You are right about AMD devices connecting to buses [0000:16] and [0000:64].
However I am unable to understand as to how you extend that to mean they
belong to Intel 0x09A2.
Per my understanding I am expecting Root Complex enumerated as a device,
with various other devices hanging off one or more ports/buses. In the
PCIe device tree, I don't see that.
I see the [domain::bus] as the root of the AMD device. Furthermore I see
Intel devices 0x09A2 hanging off the same domain::bus. I will take your
word, but the way the root complex is reported could be less confusing.
If I could make a request, it will be very helpfulf for folks who don't
dabble in this area with a simple cheat sheet plus write explaining with
examples the various root complexes and the variou end-points hanging off
of them.
Let me know if I could help in this effort.
Regards,
Ramesh
next prev parent reply other threads:[~2022-10-06 2:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFGSPrzM_pRZ-JEWimKYDPzv76t_Nw2Q6od19S_3dzbG_0-bDA@mail.gmail.com>
2022-10-04 23:44 ` Understanding P2P DMA related errors Logan Gunthorpe
[not found] ` <CAFGSPrz2ym5oEot9gLi3Z38PWS5A_wCFM4OWk36U_RazDMR67A@mail.gmail.com>
2022-10-05 15:54 ` Logan Gunthorpe
2022-10-05 17:09 ` Bjorn Helgaas
2022-10-06 2:56 ` Ramesh Errabolu [this message]
2022-10-06 15:26 ` Logan Gunthorpe
2022-10-06 19:33 ` Ramesh Errabolu
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=20221006025653.3519854-1-Ramesh.Errabolu@amd.com \
--to=ramesh.errabolu@amd.com \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=ramesh.errabolu@gmail.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