Re: [PATCH v1 3/5] perf cs-etm: Support for NO_SYNC packet

2018-12-05 Thread leo . yan
On Wed, Dec 05, 2018 at 10:48:45AM -0700, Mathieu Poirier wrote: [...] > > So I think there still have some difference between TRACE_ON and > > NO_SYNC packets, TRACE_ON packet indicates the start of trace and it's > > also possible caused by tracing discontinuity; NO_SYNC packets usually > >

Re: [PATCH v1 3/5] perf cs-etm: Support for NO_SYNC packet

2018-12-05 Thread leo . yan
On Wed, Dec 05, 2018 at 10:48:45AM -0700, Mathieu Poirier wrote: [...] > > So I think there still have some difference between TRACE_ON and > > NO_SYNC packets, TRACE_ON packet indicates the start of trace and it's > > also possible caused by tracing discontinuity; NO_SYNC packets usually > >

Re: [PATCH v1 3/5] perf cs-etm: Support for NO_SYNC packet

2018-12-05 Thread Mathieu Poirier
On Tue, 4 Dec 2018 at 20:31, wrote: > > On Mon, Nov 19, 2018 at 11:27:59AM -0700, Mathieu Poirier wrote: > > On Sun, Nov 11, 2018 at 12:59:41PM +0800, Leo Yan wrote: > > > As described in OpenCSD (CoreSight decoder lib), in the decoding stream > > > it includes one trace element with type

Re: [PATCH v1 3/5] perf cs-etm: Support for NO_SYNC packet

2018-12-05 Thread Mathieu Poirier
On Tue, 4 Dec 2018 at 20:31, wrote: > > On Mon, Nov 19, 2018 at 11:27:59AM -0700, Mathieu Poirier wrote: > > On Sun, Nov 11, 2018 at 12:59:41PM +0800, Leo Yan wrote: > > > As described in OpenCSD (CoreSight decoder lib), in the decoding stream > > > it includes one trace element with type

Re: [PATCH v1 3/5] perf cs-etm: Support for NO_SYNC packet

2018-12-04 Thread leo . yan
On Mon, Nov 19, 2018 at 11:27:59AM -0700, Mathieu Poirier wrote: > On Sun, Nov 11, 2018 at 12:59:41PM +0800, Leo Yan wrote: > > As described in OpenCSD (CoreSight decoder lib), in the decoding stream > > it includes one trace element with type OCSD_GEN_TRC_ELEM_NO_SYNC; the > > element indicates

Re: [PATCH v1 3/5] perf cs-etm: Support for NO_SYNC packet

2018-12-04 Thread leo . yan
On Mon, Nov 19, 2018 at 11:27:59AM -0700, Mathieu Poirier wrote: > On Sun, Nov 11, 2018 at 12:59:41PM +0800, Leo Yan wrote: > > As described in OpenCSD (CoreSight decoder lib), in the decoding stream > > it includes one trace element with type OCSD_GEN_TRC_ELEM_NO_SYNC; the > > element indicates

Re: [PATCH v1 3/5] perf cs-etm: Support for NO_SYNC packet

2018-11-19 Thread Mathieu Poirier
On Sun, Nov 11, 2018 at 12:59:41PM +0800, Leo Yan wrote: > As described in OpenCSD (CoreSight decoder lib), in the decoding stream > it includes one trace element with type OCSD_GEN_TRC_ELEM_NO_SYNC; the > element indicates 'either at start of decode, or after overflow / bad > packet', we should

Re: [PATCH v1 3/5] perf cs-etm: Support for NO_SYNC packet

2018-11-19 Thread Mathieu Poirier
On Sun, Nov 11, 2018 at 12:59:41PM +0800, Leo Yan wrote: > As described in OpenCSD (CoreSight decoder lib), in the decoding stream > it includes one trace element with type OCSD_GEN_TRC_ELEM_NO_SYNC; the > element indicates 'either at start of decode, or after overflow / bad > packet', we should

[PATCH v1 3/5] perf cs-etm: Support for NO_SYNC packet

2018-11-10 Thread Leo Yan
As described in OpenCSD (CoreSight decoder lib), in the decoding stream it includes one trace element with type OCSD_GEN_TRC_ELEM_NO_SYNC; the element indicates 'either at start of decode, or after overflow / bad packet', we should take it as a signal for the tracing off and this will cause

[PATCH v1 3/5] perf cs-etm: Support for NO_SYNC packet

2018-11-10 Thread Leo Yan
As described in OpenCSD (CoreSight decoder lib), in the decoding stream it includes one trace element with type OCSD_GEN_TRC_ELEM_NO_SYNC; the element indicates 'either at start of decode, or after overflow / bad packet', we should take it as a signal for the tracing off and this will cause