[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAH9NwWc7x2nUQAhL4vpeOJ-gRUHs4QqqBeo4jbQt0e2Mb=a7_w@mail.gmail.com>
Date: Sat, 2 Jul 2022 13:57:43 +0200
From: Christian Gmeiner <christian.gmeiner@...il.com>
To: Lucas Stach <l.stach@...gutronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>,
David Airlie <airlied@...ux.ie>,
"moderated list:DRM DRIVERS FOR VIVANTE GPU IP"
<etnaviv@...ts.freedesktop.org>,
"open list:DRM DRIVERS FOR VIVANTE GPU IP"
<dri-devel@...ts.freedesktop.org>, Daniel Vetter <daniel@...ll.ch>,
Russell King <linux+etnaviv@...linux.org.uk>
Subject: Re: [PATCH v2 4/4] drm/etnaviv: export loadavg via perfmon
Hi Lucas
> You need to explain a bit more how you intend to use those.
>
> Contrary to all other perfmon values, where we go to great lengths to
> only count the load put onto the GPU by the specific process requesting
> the perfmon, the loadavg values also include the load caused by other
> submits. Due to this difference in behavior I fear that those new
> counters might be confusing to use. But maybe you have a use-case in
> mind that I don't see right now.
I see these values as total load avg of a sub-GPU component. Sure it is not per
process but it is a starting point. I have no problem introducing per
process load avg
values .. lets see how the next version of this series will look like,
--
greets
--
Christian Gmeiner, MSc
https://christian-gmeiner.info/privacypolicy
Powered by blists - more mailing lists