Gentoo Archives: gentoo-user

From: Peter Humphrey <peter@××××××××××××.uk>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Instrumenting the GPU
Date: Tue, 14 Nov 2017 09:05:44
Message-Id: 2495907.v5vVpxkAQK@peak
In Reply to: Re: [gentoo-user] Instrumenting the GPU by R0b0t1
On Tuesday, 14 November 2017 06:37:35 GMT R0b0t1 wrote:

> On Mon, Nov 13, 2017 at 9:46 AM, Peter Humphrey <peter@××××××××××××.uk>
wrote:
> > On Monday, 13 November 2017 15:12:56 GMT Daniel Frey wrote: > >> On 11/13/17 02:59, Peter Humphrey wrote: > >> > I'm hunting a problem with cooling in this box, and I've got as far > >> > as suspecting my new AMD WX 5100 GPU. > >> > > >> > One of my BOINC projects causes the GPU temperature, as shown by > >> > gkrellm, to shoot up to 75C or more and cause intolerable system > >> > cooling noise. If I suspend that project but leave the other seven > >> > running, the temperature returns to what I hope is a normal 55C. > >> > Those seven projects are supposed to use the GPU, but I'm not sure > >> > whether they do in fact. > >> > > >> > Is there any way I can monitor what is using the GPU, to find out? > >> > >> I don't know if there's a utility for consumer level cards that can do > >> this. I do remember for Nvidia there's nvidia-smi but I don't think it > >> will list processes for desktop cards. > > > > This isn't consumer grade (look it up in your local shops ;-) ): > > > > # lspci -v -s 01:00.0 > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. > > [AMD/ATI] > > Ellesmere [Radeon Pro WX 5100] (prog-if 00 [VGA controller])
[...]
> >> The only other generic ones I can think of are cuda-z and gputop. Have > >> you tried one of those? Although I don't think it'll give you the > >> information you need either. > > > > As it's AMD, not nVidia, nvidia-smi and cuda aren't suitable. I hadn't > > heard of GPU Top - thanks. I'll have a look at it. > > > > I forgot to add that I'm using the proprietary > > dev-libs/amdgpu-pro-opencl > > because mesa hasn't caught up yet. > > The level of detail you want will likely necessitate the use of a GPU > debugger. AMD provides CodeXL, located at > https://gpuopen.com/compute-product/codexl/. I suggest looking at the > profiling features.
That does look interesting - many thanks.
> You may want to communicate your findings to the relevant BOINC projects.
Of course. -- Regards, Peter.