Re: [Intel-gfx] [PATCH 1/2] trace: Export anonymous tracing

2020-03-03 Thread Steven Rostedt
On Sun, 01 Mar 2020 22:22:25 + Chris Wilson wrote: > Quoting Steven Rostedt (2020-03-01 18:18:16) > > On Sun, 1 Mar 2020 15:52:47 + > > Chris Wilson wrote: > > > > > To facilitate construction of per-client event ringbuffers, in > > > particular for a per-client debug and error repor

Re: [Intel-gfx] [PATCH 1/2] trace: Export anonymous tracing

2020-03-01 Thread Steven Rostedt
On Sun, 01 Mar 2020 22:22:25 + Chris Wilson wrote: > > I'm curious to why we need it to be anonymous. Why not allow them to be > > visible from the tracing directory. This could allow for easier > > debugging. Note, the trace instances have ref counters thus they can't > > be removed if somet

Re: [Intel-gfx] [PATCH 1/2] trace: Export anonymous tracing

2020-03-01 Thread Chris Wilson
Quoting Steven Rostedt (2020-03-01 18:18:16) > On Sun, 1 Mar 2020 15:52:47 + > Chris Wilson wrote: > > > To facilitate construction of per-client event ringbuffers, in > > particular for a per-client debug and error report log, it would be > > extremely useful to create an anonymous file tha

Re: [Intel-gfx] [PATCH 1/2] trace: Export anonymous tracing

2020-03-01 Thread Steven Rostedt
On Sun, 1 Mar 2020 15:52:47 + Chris Wilson wrote: > To facilitate construction of per-client event ringbuffers, in > particular for a per-client debug and error report log, it would be > extremely useful to create an anonymous file that can be handed to > userspace so that it can see its and

[Intel-gfx] [PATCH 1/2] trace: Export anonymous tracing

2020-03-01 Thread Chris Wilson
To facilitate construction of per-client event ringbuffers, in particular for a per-client debug and error report log, it would be extremely useful to create an anonymous file that can be handed to userspace so that it can see its and only its events. trace already provides a means of encapsulating