Maxime Schmitt

I haven't looked at the details, but from what I understood is that each MIG instance **should** show up as a separate a handle (device in `nvtop`). Since I haven't...

All right. I have a good and a bad news: - The good: I updated the code to use the latest NVML API functions to retrieve Nvidia GPUs info. -...

While I agree that such library would be useful, I think that the current license would not be a good match for such library.

I'll update the NVML support to call the newest API function versions. It may help with this problem and with GPU MIG/virtualization modes.

If I had access to such card I could try and add support if there is a way to discover these GPUs. If it's not registering through the drm driver...

Since asahi is running on a Linux kernel, what you should really be using is the regular Linux build. Although we don't currently have a support for the driver on...

I think that I can do something really simple: close all the device handles for the GPUs that are not marked to be monitored. (you can choose which GPU to...

Hello, Nvtop extracts the PCIe bus from the device using libudev and does not rely on pp_dpm_pcie ([code](https://github.com/Syllo/nvtop/blob/487858b1120f4a3ed05e14ca4b8944f5964251d9/src/device_discovery_linux.c#L320C16-L320C16)). The code walks the PCIe bus from the device up to the...

Hello, What version of `nvtop` are you using? If you have one of the latest version you have a menu through `F2` where you can de-select the GPUs you don't...

Hello, I suggest opening a ticket on the forum/bug tracker of the distribution that you are using. I don't do the packaging of `nvtop` for distributions so I don't have...