<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Sure they can, those files are accessible to everyone.<br>
<br>
The massive advantage is that this is standard for all PCIe devices,
so it should work vendor independent.<br>
<br>
Christian.<br>
<br>
<div class="moz-cite-prefix">Am 02.01.23 um 18:55 schrieb Marek
Olšák:<br>
</div>
<blockquote type="cite"
cite="mid:CAAxE2A5pBqOkny15tSRCWn_UW8=TTE=zYPChBZofZCrHZoQbww@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Userspace drivers can't access sysfs.
<div dir="auto"><br>
</div>
<div dir="auto">Marek</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Jan 2, 2023, 10:54
Christian König <<a
href="mailto:ckoenig.leichtzumerken@gmail.com"
moz-do-not-send="true" class="moz-txt-link-freetext">ckoenig.leichtzumerken@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> That stuff is already available as current_link_speed
and current_link_width in sysfs.<br>
<br>
I'm a bit reluctant duplicating this information in the
IOCTL interface.<br>
<br>
Christian. <br>
<br>
<div>Am 30.12.22 um 23:07 schrieb Marek Olšák:<br>
</div>
<blockquote type="cite">
<div dir="ltr">For computing PCIe bandwidth in userspace
and troubleshooting PCIe<br>
bandwidth issues.<br>
<br>
For example, my Navi21 has been limited to PCIe gen 1
and this is<br>
the first time I noticed it after 2 years.<br>
<br>
Note that this intentionally fills a hole and padding<br>
in drm_amdgpu_info_device.<br>
<br>
<div>Signed-off-by: Marek Olšák <<a
href="mailto:marek.olsak@amd.com" target="_blank"
rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">marek.olsak@amd.com</a>></div>
<div><br>
</div>
<div>The patch is attached.</div>
<div><br>
</div>
<div>Marek<br>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>