Release 3.3.2

Bugfix

• Snapshot mode (-s) outputs valid JSON. Thanks @Steve-Tech

Additions

• Loop Snapshot mode (-l) prints snapshots in a loop fashion. Thanks @Steve-Tech
• Extra snapshot information - @Syllo
  • Processes
  • Encode/decode

Bugfix release 3.3.1

• Fix a regression that would miss-report available device memory of NVIDIA GPUs
• Integrate effective/efficiency usage within the GPU utilization metric

Release 3.3.0

New in this release

Target support

• Rockchip NPU - @feilongfl
• MetaX GPUs - @zhenyu-xu-metax
• Enflame GCU - @QShen3

Improvements

• More memory reporting in one-shot mode - @mintyleaf
• CTRL + L will reset the ncurses interface - @cipri-tom + @claude
• GPU and MEM have separate clock fields - @KaeLL
• Effective load metric, i.e., the percentage utilization weighted by the ratio (Current Power / Max Power) - @airvzxf

Fixes

• Fix assertion failure on processing the same client ID twice - @Andrew1326
• Application desktop metadata install paths and name - @michel-slm
• New PPA maintainer - @QuentiumYT
• Fixes for Mali GPU - @larunbe
• Power draw for Intel Battelmage - @Steve-Tech
• Unified memory usage reporting on Nvidia GPUs - @sbhavani
• AMDGPU integrated graphics accounts for both VRAM and GTT - @superm1

Misc

• Manpage update - @polluks
• Fix typos - @oxyzenQ

Release 3.2.0

New this release

• Intel XE driver support thanks to @Steve-Tech
  • Supports more metrics when CAP_PERFMON is given to nvtop. See the intel section of the README
• Broadcom V3D support (Raspberry Pi) thanks to @xiaohuirong
• Google TPU support thanks to @rdyro
• Interface hide process list with the -P option thanks to @ring-c
• On recent GPUs, the encode and decode engines are most likely shared, nvtop will now display "ENC/DEC" in the known cases.
• Nvtop can be installed from conda forge thanks to @matthewfeickert
• JSON snapshot option -s thanks to @jwilkins88

Bugfix and improvements

• Improved Intel i915 support by @Steve-Tech
• More portable AppImage thanks to @Samueru-sama
• Various back-end bugfixes
• FreeBSD compilation fixes by @ocochard

A huge thanks to all the contributors 🎉

Release 3.1.0

Added support for the following hardware accelerators/GPUs:

• More Adreno GPUs thanks to the panfrost linux driver
• Mac GPUs (tested on M1 and M2 by the community)
• Huawei Ascend accelerators

Bugfixes and improvements:

• Don't call handlers for GPUs that are marked as not to be monitored
• Fix crash when the configuration file path could not be discovered through user environment variables (XDG_HOME etc)

Release 3.0.2

Bugfixes:

• AMGDPU: GPUs other than id 0 should now be correctly monitored. Thanks to @CabbageSong
• Fixed a bug in GPU selection logic through the F2 menu where the wrong GPUs would still be displayed. Thanks to @cfwen for pointing me in the right direction

Improvemenrs:

• Support for ADRENO GPUs through the msm driver. Thanks @Sonicadvance1 and @robclark
• Better AMDGPU device name query for newer GPUs thanks to @amdsc21 and @paklui.
• "hjkl" directional keys. Thanks @Euro20179

Release 3.0.1

Bugfix:

• Other process than nvtop would end up hidden instead of nvtop itself.
• AMDGPU processes that use graphical and compute resources within the same DRM context would erroneously only report compute usage.

Release 3.0.0

New for this version:

• Intel GPU support
  • Partial for this release due to pending kernel patches. See the Intel section of the README for more information
    • Works (any): dectect GPU with name and clock speed
    • Works on Linux kernel >= 5.19: GPU usage, encode/decode usage, processes running on GPU.
    • Not supported yet: Memory (GPU and processes), Memory clock, fan, power, RX/TX data exchange rate.
  • Uses libsystemd (requires sd-device) or libudev (on systems without systemd or sd-device) to detect the devices and extract some GPU metrics
• Support for detecting integrated graphic cards (Intel and AMD)
• A new "GPU select" window in the setup window (F2) to enable/disable monitoring of select GPUs
  • This setting can be saved to be persistent after a restart
  • This replaces the "-s" and "-i" command line options
• An new option to hide nvtop's own process from the process list (enabled by default)
• Support messages on startup to inform about limitations on old kernels
• Provide an Appstream metainfo file for nvtop

Fix:

• Workaround to detect AMD GPUs which are always reporting 100% usage through the DRM driver and show the sum of the processes usage instead

Release 2.0.4

New this update:

• snap support thanks to @Nightmayr
• Standalone application through an AppImage
  • No compilation needed, download and run (see README)!
  • Built inside an Ubuntu 18.04 docker (should run almost everywhere but please report any issue).
• Logo and .desktop file (required for an AppImage). The logo is not the best since I am not very talented ...
• AMDGPU compute task reporting in the process list.

Fix and improvements this update:

• Fix warnings from misuse of ncurses print function. Thanks @felixonmars
• Go through /proc only once per update, independently of the number of GPUs.
  • Less resources used on systems with multiple AMD GPUs.
• Fix inconsistencies coming from AMDGPU fdinfo interface (e.g., greater than 100% usage in some occasions)

Help nvtop:

I am working on adding Intel support for the next release. If someone has (or plans to buy) a dedicated Intel GPU, please drop a comment on the #106 thread if you are willing to help by sharing some udev and fdinfo dump of your system.

Release 2.0.3

New this update:

• Second are shown on the graphs time axis.
• AMDGPU support for the Linux kernels >=5.19
  • Support for the updated fdinfo interface (seems to be a name harmonization between multiple drivers, i.e., AMD and Intel)
  • More precise GPU usage metrics
    • Per-GPU gfx, encode and decode time usage in nanoseconds allows for a precise percentage usage computation independently of the driver update rate (a GPU time usage column for the process list will follow)

Fix:

• Segfault while retrieving AMDGPU device handles and no device node could be opened.
• Compilation warnings

Thanks to all contributors!