From: Daniele Ceraolo Spurio daniele.ceraolospu...@intel.com
These tracepoints are useful for observing the creation and
destruction of Full PPGTTs.
Signed-off-by: Daniele Ceraolo Spurio daniele.ceraolospu...@intel.com
---
drivers/gpu/drm/i915/i915_gem_context.c | 6 +
On Wed, Jun 18, 2014 at 05:16:39PM +0100, oscar.ma...@intel.com wrote:
From: Daniele Ceraolo Spurio daniele.ceraolospu...@intel.com
These tracepoints are useful for observing the creation and
destruction of Full PPGTTs.
Signed-off-by: Oscar Mateo oscar.ma...@intel.com
---
-Original Message-
From: Chris Wilson [mailto:ch...@chris-wilson.co.uk]
Sent: Thursday, June 19, 2014 8:57 AM
To: Mateo Lozano, Oscar
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915: Add ppgtt init/release trace
points
On Wed, Jun 18, 2014 at 05
] drm/i915: Add ppgtt init/release trace
points
On Wed, Jun 18, 2014 at 05:16:39PM +0100, oscar.ma...@intel.com wrote:
From: Daniele Ceraolo Spurio daniele.ceraolospu...@intel.com
These tracepoints are useful for observing the creation and
destruction of Full PPGTTs.
Signed
On Thu, Jun 19, 2014 at 04:41:50PM +0100, Daniele Ceraolo Spurio wrote:
Regarding the client, my idea is to print the task pid and/or the
process name; would that look good for you?
Going off an tangent. We have a problem with file-pid. In the dri3,
or rendernodes, future all pids belong to the
From: Daniele Ceraolo Spurio daniele.ceraolospu...@intel.com
These tracepoints are useful for observing the creation and
destruction of Full PPGTTs.
Signed-off-by: Oscar Mateo oscar.ma...@intel.com
---
drivers/gpu/drm/i915/i915_gem_context.c | 5 +
drivers/gpu/drm/i915/i915_trace.h |
