Re: [PATCH v1 5/5] perf cs-etm: Track exception number

2018-12-05 Thread leo . yan
On Wed, Dec 05, 2018 at 11:03:29AM -0700, Mathieu Poirier wrote: [...] > > > > static ocsd_datapath_resp_t > > > > cs_etm_decoder__buffer_exception(struct cs_etm_decoder *decoder, > > > > +const ocsd_generic_trace_elem *elem, > > > > cons

Re: [PATCH v1 5/5] perf cs-etm: Track exception number

2018-12-05 Thread Mathieu Poirier
On Tue, 4 Dec 2018 at 20:49, wrote: > > On Mon, Nov 19, 2018 at 01:47:49PM -0700, Mathieu Poirier wrote: > > On Sun, Nov 11, 2018 at 12:59:43PM +0800, Leo Yan wrote: > > > When an exception packet comes, it contains the info for exception > > > number; the exception number indicates the exception

Re: [PATCH v1 5/5] perf cs-etm: Track exception number

2018-12-04 Thread leo . yan
On Mon, Nov 19, 2018 at 01:47:49PM -0700, Mathieu Poirier wrote: > On Sun, Nov 11, 2018 at 12:59:43PM +0800, Leo Yan wrote: > > When an exception packet comes, it contains the info for exception > > number; the exception number indicates the exception types, so from it > > we can know if the except

Re: [PATCH v1 5/5] perf cs-etm: Track exception number

2018-11-19 Thread Mathieu Poirier
On Sun, Nov 11, 2018 at 12:59:43PM +0800, Leo Yan wrote: > When an exception packet comes, it contains the info for exception > number; the exception number indicates the exception types, so from it > we can know if the exception is taken for interrupt, system call or > other traps, etc. But becau

[PATCH v1 5/5] perf cs-etm: Track exception number

2018-11-10 Thread Leo Yan
When an exception packet comes, it contains the info for exception number; the exception number indicates the exception types, so from it we can know if the exception is taken for interrupt, system call or other traps, etc. But because the exception return packet cannot delivery exception number c