Re: [PATCH v6 01/15] tracing: Refactor hist trigger action code

Hi Masami, On Tue, 2018-10-23 at 14:09 +0900, Masami Hiramatsu wrote: > Hi Tom, > > On Thu, 11 Oct 2018 16:01:58 -0500 > Tom Zanussi wrote: > > > From: Tom Zanussi > > > > The hist trigger action code currently implements two essentially > > hard-coded pairs of 'actions' - onmax(), which trac

Re: [PATCH v6 01/15] tracing: Refactor hist trigger action code

Hi Tom, On Thu, 11 Oct 2018 16:01:58 -0500 Tom Zanussi wrote: > From: Tom Zanussi > > The hist trigger action code currently implements two essentially > hard-coded pairs of 'actions' - onmax(), which tracks a variable and > saves some event fields when a max is hit, and onmatch(), which is >

[PATCH v6 01/15] tracing: Refactor hist trigger action code

From: Tom Zanussi The hist trigger action code currently implements two essentially hard-coded pairs of 'actions' - onmax(), which tracks a variable and saves some event fields when a max is hit, and onmatch(), which is hard-coded to generate a synthetic event. These hardcoded pairs (track max/s