From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: "Quan, Evan" <Evan.Quan@amd.com>,
Maxime Schmitt <maxime.schmitt91@gmail.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
mike.zhou@amd.com
Subject: Re: [Question/Bug?] Why does the sysfs current_link_speed report a different value than pp_dpm_pcie
Date: Mon, 9 May 2022 15:33:41 +0530 [thread overview]
Message-ID: <45ae8180-ff4b-232f-e548-e6d0235763f3@amd.com> (raw)
In-Reply-To: <DM6PR12MB2619BFF30502D3EE717A0422E4C69@DM6PR12MB2619.namprd12.prod.outlook.com>
+Mike
On 5/9/2022 8:17 AM, Quan, Evan wrote:
> [AMD Official Use Only - General]
>
> *From:* amd-gfx <amd-gfx-bounces@lists.freedesktop.org> *On Behalf Of
> *Maxime Schmitt
> *Sent:* Wednesday, April 6, 2022 1:40 AM
> *To:* amd-gfx@lists.freedesktop.org
> *Subject:* [Question/Bug?] Why does the sysfs current_link_speed report
> a different value than pp_dpm_pcie
>
> Hello,
>
> On my system the sysfs file "current_link_speed" is reporting "16.0 GT/s
> PCIe".
>
> The GPU has support for PCIe gen 4 (AMD Radeon RX 6800 XT).
>
> However neither the CPU (AMD Ryzen 7 1700X) nor the motherboard have
> support for PCIe gen 4.
>
> The file "pp_dpm_pcie" returns the following:
>
> 0: 2.5GT/s, x1 310Mhz
> 1: 8.0GT/s, x16 619Mhz *
>
> Which is correct.
>
> Is this the expected behavior?
>
> */[Quan, Evan] “pp_dpm_pcie” is reporting the correct link speed. You
> can trust that./*
>
> */While “current_link_speed” seems reporting the link speed the card is
> capable of. Not sure whether that fits design./*
>
> */@Deucher, Alexander <mailto:Alexander.Deucher@amd.com> Any comments
> for the output of sysfs file “current_link_speed”?/*
>
In our architecture, GFX endpoint is not directly connected to
CPU/Chipset PCIE. We have upstream/downstream bridges in between
CPU/Chipset <-> || US Port <-> DS Port <-> GFX EP||
The actual speed will be reflected in the US port connected to the
CPU/chipset port or pp_dpm_pcie node as it shows the speed reported by
power management firmware.
Thanks,
Lijo
> *//*
>
> */BR/*
>
> */Evan/*
>
> I am asking because I recently added AMDGPU support to a monitoring tool
> I maintain (nvtop) and I don't know where to get the information from.
>
> Cheers,
>
> Maxime
>
prev parent reply other threads:[~2022-05-09 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 17:39 [Question/Bug?] Why does the sysfs current_link_speed report a different value than pp_dpm_pcie Maxime Schmitt
2022-05-09 2:47 ` Quan, Evan
2022-05-09 10:03 ` Lazar, Lijo [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=45ae8180-ff4b-232f-e548-e6d0235763f3@amd.com \
--to=lijo.lazar@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Evan.Quan@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=maxime.schmitt91@gmail.com \
--cc=mike.zhou@amd.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