Re: [PATCH v3 1/7] tracing: Refactor hist trigger action code

Hi Namhyung, On Fri, 2018-08-10 at 15:58 +0900, Namhyung Kim wrote: > Hi Tom, > > On Thu, Aug 09, 2018 at 09:34:11AM -0500, Tom Zanussi wrote: > > From: Tom Zanussi > > > > The hist trigger action code currently implements two essentially > > hard-coded pairs of 'actions' - onmax(), which track

Re: [PATCH v3 1/7] tracing: Refactor hist trigger action code

Hi Tom, On Thu, Aug 09, 2018 at 09:34:11AM -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

[PATCH v3 1/7] 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