Re: [RFC PATCH 1/8] tracing/gpu: modify gpu_mem_total

2021-10-28 Thread Daniel Vetter
On Thu, Oct 21, 2021 at 09:07:15AM -0400, Steven Rostedt wrote: > On Thu, 21 Oct 2021 13:56:38 +0200 > Daniel Vetter wrote: > > > Yay, that patch is just impressive. Lands a new gpu tracepoints, never > > even showed up on the gpu subsystem discussion list. > > I'm guessing there was some

Re: [RFC PATCH 1/8] tracing/gpu: modify gpu_mem_total

2021-10-21 Thread Steven Rostedt
On Thu, 21 Oct 2021 13:56:38 +0200 Daniel Vetter wrote: > Yay, that patch is just impressive. Lands a new gpu tracepoints, never > even showed up on the gpu subsystem discussion list. I'm guessing there was some confusion. When this was first introduced, I stated it needs to go into the gpu

Re: [RFC PATCH 1/8] tracing/gpu: modify gpu_mem_total

2021-10-21 Thread Daniel Vetter
On Wed, Oct 20, 2021 at 08:10:20PM -0700, Gurchetan Singh wrote: > The existing gpu_mem_total tracepoint [1] is not currently used by > any in-tree consumers, we should add some. > > In addition, there's a desire to report imported memory via the > counters too [2]. > > To do this, we'll have to

[RFC PATCH 1/8] tracing/gpu: modify gpu_mem_total

2021-10-20 Thread Gurchetan Singh
The existing gpu_mem_total tracepoint [1] is not currently used by any in-tree consumers, we should add some. In addition, there's a desire to report imported memory via the counters too [2]. To do this, we'll have to redefine the event to: a) Change 'pid' to 'ctx_id' The reason is DRM