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 2/2] drm/amdgpu: add AMDGPU_INFO_VM_STAT to return GPU VM
Date: Tue, 3 Jan 2023 09:33:07 +0100 [thread overview]
Message-ID: <1d0ddc01-b315-a5ff-f4cc-30b8aedfeb57@gmail.com> (raw)
In-Reply-To: <CAAxE2A487Ra9ropymBGZpXSt=Zz81cjf56p_7wq+tK4cDfn1sA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
Take a look at /proc/self/fdinfo/$fd.
The Intel guys made that vendor agnostic and are using it within their
IGT gpu top tool.
Christian.
Am 02.01.23 um 18:57 schrieb Marek Olšák:
> What are you talking about? Is fdinfo in sysfs? Userspace drivers
> can't access sysfs.
>
> Marek
>
> On Mon, Jan 2, 2023, 10:56 Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>
> Well first of all don't mess with the VM internals outside of the
> VM code.
>
> Then why would we want to expose this through the IOCTL interface?
> We already have this in the fdinfo.
>
> Christian.
>
> Am 30.12.22 um 23:07 schrieb Marek Olšák:
>> To give userspace a detailed view about its GPU memory usage and
>> evictions.
>> This will help performance investigations.
>>
>> Signed-off-by: Marek Olšák <marek.olsak@amd.com>
>>
>> The patch is attached.
>>
>> Marek
>
[-- Attachment #2: Type: text/html, Size: 2537 bytes --]
next prev parent reply other threads:[~2023-01-03 8:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 22:07 [PATCH 2/2] drm/amdgpu: add AMDGPU_INFO_VM_STAT to return GPU VM Marek Olšák
2022-12-30 22:10 ` Marek Olšák
2023-01-02 15:56 ` Christian König
2023-01-02 17:57 ` Marek Olšák
2023-01-03 8:33 ` Christian König [this message]
2023-01-03 23:08 ` Marek Olšák
2023-01-04 14:51 ` Christian König
2023-01-10 15:28 ` Marek Olšák
2023-01-10 16:23 ` Christian König
2023-01-10 16:55 ` Marek Olšák
2023-01-21 0:45 ` Marek Olšák
2023-01-23 9:31 ` Christian König
2023-01-24 7:37 ` Marek Olšák
2023-01-24 7:58 ` Christian König
2023-01-24 8:13 ` Marek Olšák
2023-01-24 8:27 ` Marek Olšák
2023-01-24 8:29 ` Christian König
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=1d0ddc01-b315-a5ff-f4cc-30b8aedfeb57@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