Announcement

Collapse
No announcement yet.

Announcing radeontop, a tool for viewing the GPU usage

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • agd5f
    replied
    Originally posted by marek View Post
    It doesn't work on Bonaire. Everything is at 0%, only VRAM seems to be correct.
    The MMIO BAR changed on CIK parts. The relevant mapping code would need to be changed.

    Leave a comment:


  • marek
    replied
    It doesn't work on Bonaire. Everything is at 0%, only VRAM seems to be correct.

    Leave a comment:


  • curaga
    replied
    Faithful followers, Dear Leader of Best Korea announced a new version is available on a repository near you.
    v0.8

    Release highlights include VRAM reporting on a 3.15 kernel or newer, as well as pci ids for Hawaii.
    I might have just accidentally killed OpenBSD support, not sure if libdrm is available there. If not, patches welcome OpenBSD users, should be fairly easy to ifdef out.

    In other news, PTS has radeontop support in its git version now, to be released as 5.1 or 5.0.2 I believe. So if you install radeontop as suid root, you get GPU usage graphing:
    MONITOR=gpu.usage phoronix-test-suite run pts/blahblah

    Leave a comment:


  • BobMartin333
    replied
    wow!! great reply. really interesting. Cheers!!

    Leave a comment:


  • ByteTraveller
    replied
    Cheers - I'll look into that.

    Leave a comment:


  • curaga
    replied
    I don't think that information is available via a register. Only the memory manager knows how much is used, and it currently only exports that information in debugfs.

    Leave a comment:


  • ByteTraveller
    replied
    Are there any plans to report on the VRAM usage? I've just discovered the gallium_hud functionality in mesa, and appreciated the VRAM graph there.

    Leave a comment:


  • curaga
    replied
    Rejoice, for a new release is available! From Russia with love.

    v0.7
    This release comes with many locale fixes and a complete Russian
    translation.

    The pci ids were updated to detect Oland, Hainan, Bonaire, Kabini, and
    Kaveri. Dumping works better in pipes.

    Leave a comment:


  • curaga
    replied
    Apparently it's been ported to OpenBSD with no code changes. Nice to know, I wasn't expecting that.

    Now, anyone running the AMD blob (on Linux) willing to try it? I wonder if it also works with the blob. If so, the case for PTS integration would be clear - "is it cpu or gpu limited" result for every AMD graphics test

    Leave a comment:


  • ByteTraveller
    replied
    Finally got round to making a script to output the GPU info somewhere useful then conky can read it in (intended to be ran as root, via an init.d script):

    Code:
    #!/bin/bash
    
    
    # Make sure the directory structure is in place
    [[ ! -d '/run/shm/radeontop' ]] && mkdir -p '/run/shm/radeontop'
    
    # Removing old data
    rm '/run/shm/radeontop/gpu' 2>/dev/null
    
    while true
    do
        # Running radeontop in dump mode, killing off the silly full buffering and outputting just the GPU stats. AWK's redirection fails - you must close the file to have it behave like a bash overwrite, and if you don't close or don't insert an arbitrary delay prior to the print (e.g. system sleep/beep call), nothing is output!
        stdbuf -oL radeontop -d - | awk '($2 == "gpu") { print substr($3, 1, length($3) - 1) > "/run/shm/radeontop/gpu"; close("/run/shm/radeontop/gpu"); }'
    done
    Had great difficulty getting AWK to do its job - looks like some strange buffering is happening if you don't close the file and don't arbitrarily delay the command.

    Leave a comment:

Working...
X