Re: [Intel-gfx] [PATCH 2/2] RFC drm/i915: Export per-client debug tracing

2020-03-02 Thread Daniel Vetter
On Sun, Mar 01, 2020 at 03:52:48PM +, Chris Wilson wrote: > Rather than put sensitive, and often voluminous, user details into a > global dmesg, report the error and debug messages directly back to the > user via the kernel tracing mechanism. > > Signed-off-by: Chris Wilson > Cc: Steven

Re: [Intel-gfx] [PATCH 2/2] RFC drm/i915: Export per-client debug tracing

2020-03-01 Thread Chris Wilson
Quoting Lionel Landwerlin (2020-03-01 16:27:24) > On 01/03/2020 17:52, Chris Wilson wrote: > > Rather than put sensitive, and often voluminous, user details into a > > global dmesg, report the error and debug messages directly back to the > > user via the kernel tracing mechanism. > > > Sounds

Re: [Intel-gfx] [PATCH 2/2] RFC drm/i915: Export per-client debug tracing

2020-03-01 Thread Lionel Landwerlin
On 01/03/2020 17:52, Chris Wilson wrote: Rather than put sensitive, and often voluminous, user details into a global dmesg, report the error and debug messages directly back to the user via the kernel tracing mechanism. Sounds really nice. Don't you want the existing global tracing to be the

[Intel-gfx] [PATCH 2/2] RFC drm/i915: Export per-client debug tracing

2020-03-01 Thread Chris Wilson
Rather than put sensitive, and often voluminous, user details into a global dmesg, report the error and debug messages directly back to the user via the kernel tracing mechanism. Signed-off-by: Chris Wilson Cc: Steven Rostedt (VMware) --- drivers/gpu/drm/i915/gem/i915_gem_context.c | 104