From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: "Marek Olšák" <maraeo@gmail.com>
Cc: amd-gfx mailing list <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/amdgpu: return the PCIe gen and lanes from the INFO
Date: Tue, 3 Jan 2023 09:31:26 +0100 [thread overview]
Message-ID: <35304b1e-98a7-d342-9f1b-50f07b45cf98@gmail.com> (raw)
In-Reply-To: <CAAxE2A5pBqOkny15tSRCWn_UW8=TTE=zYPChBZofZCrHZoQbww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
Sure they can, those files are accessible to everyone.
The massive advantage is that this is standard for all PCIe devices, so
it should work vendor independent.
Christian.
Am 02.01.23 um 18:55 schrieb Marek Olšák:
> Userspace drivers can't access sysfs.
>
> Marek
>
> On Mon, Jan 2, 2023, 10:54 Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>
> That stuff is already available as current_link_speed and
> current_link_width in sysfs.
>
> I'm a bit reluctant duplicating this information in the IOCTL
> interface.
>
> Christian.
>
> Am 30.12.22 um 23:07 schrieb Marek Olšák:
>> For computing PCIe bandwidth in userspace and troubleshooting PCIe
>> bandwidth issues.
>>
>> For example, my Navi21 has been limited to PCIe gen 1 and this is
>> the first time I noticed it after 2 years.
>>
>> Note that this intentionally fills a hole and padding
>> in drm_amdgpu_info_device.
>>
>> Signed-off-by: Marek Olšák <marek.olsak@amd.com>
>>
>> The patch is attached.
>>
>> Marek
>>
>
[-- Attachment #2: Type: text/html, Size: 2813 bytes --]
next prev parent reply other threads:[~2023-01-03 8:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 22:07 [PATCH 1/2] drm/amdgpu: return the PCIe gen and lanes from the INFO Marek Olšák
2023-01-02 15:54 ` Christian König
2023-01-02 17:55 ` Marek Olšák
2023-01-03 8:31 ` Christian König [this message]
2023-01-03 22:41 ` Marek Olšák
2023-01-04 11:50 ` Lazar, Lijo
2023-01-04 14:13 ` Marek Olšák
2023-01-04 14:18 ` Lazar, Lijo
2023-01-04 15:10 ` Marek Olšák
2023-01-04 15:33 ` Lazar, Lijo
2023-01-04 20:17 ` Marek Olšák
2023-01-11 20:48 ` Alex Deucher
2023-01-11 20:50 ` Alex Deucher
2023-01-12 2:39 ` Marek Olšák
2023-01-12 11:46 ` Christian König
2023-01-12 11:50 ` Christian König
2023-01-12 16:43 ` Alex Deucher
2023-01-13 21:01 ` Marek Olšák
2023-01-13 21:20 ` Alex Deucher
2023-01-13 23:33 ` Marek Olšák
2023-01-13 23:38 ` Marek Olšák
2023-01-16 11:31 ` Christian König
2023-01-17 19:21 ` Alex Deucher
2023-01-04 14:15 ` Alex Deucher
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=35304b1e-98a7-d342-9f1b-50f07b45cf98@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=maraeo@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