I see about the access now, but did you even look at the patch? Because what the patch does isn't even exposed to common drm code, such as the preferred domain and visible VRAM placement, so it can't be in fdinfo right now.
Or do you even know what fdinfo contains? Because it contains nothing useful. It only has VRAM and GTT usage, which we already have in the INFO ioctl, so it has nothing that we need. We mainly need the eviction information and visible VRAM information now. Everything else is a bonus. Also, it's undesirable to open and parse a text file if we can just call an ioctl. So do you want me to move it into amdgpu_vm.c? Because you could have just said: Let's move it into amdgpu_vm.c. :) Thanks, Marek On Tue, Jan 3, 2023 at 3:33 AM Christian König < ckoenig.leichtzumer...@gmail.com> wrote: > 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.leichtzumer...@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.ol...@amd.com> >> >> The patch is attached. >> >> Marek >> >> >> >
