Re: [PATCH v7 15/37] tracing: Add variable support to hist triggers

2017-12-08 Thread Tom Zanussi
Hi Namhyung, On Fri, 2017-12-08 at 22:02 +0900, Namhyung Kim wrote: > Hi Tom, > > On Wed, Dec 06, 2017 at 04:37:56PM -0600, Tom Zanussi wrote: > > Add support for saving the value of a current event's event field by > > assigning it to a variable that can be read by a subsequent event. > > > >

Re: [PATCH v7 15/37] tracing: Add variable support to hist triggers

2017-12-08 Thread Tom Zanussi
Hi Namhyung, On Fri, 2017-12-08 at 22:02 +0900, Namhyung Kim wrote: > Hi Tom, > > On Wed, Dec 06, 2017 at 04:37:56PM -0600, Tom Zanussi wrote: > > Add support for saving the value of a current event's event field by > > assigning it to a variable that can be read by a subsequent event. > > > >

Re: [PATCH v7 15/37] tracing: Add variable support to hist triggers

2017-12-08 Thread Namhyung Kim
Hi Tom, On Wed, Dec 06, 2017 at 04:37:56PM -0600, Tom Zanussi wrote: > Add support for saving the value of a current event's event field by > assigning it to a variable that can be read by a subsequent event. > > The basic syntax for saving a variable is to simply prefix a unique > variable name

Re: [PATCH v7 15/37] tracing: Add variable support to hist triggers

2017-12-08 Thread Namhyung Kim
Hi Tom, On Wed, Dec 06, 2017 at 04:37:56PM -0600, Tom Zanussi wrote: > Add support for saving the value of a current event's event field by > assigning it to a variable that can be read by a subsequent event. > > The basic syntax for saving a variable is to simply prefix a unique > variable name

[PATCH v7 15/37] tracing: Add variable support to hist triggers

2017-12-06 Thread Tom Zanussi
Add support for saving the value of a current event's event field by assigning it to a variable that can be read by a subsequent event. The basic syntax for saving a variable is to simply prefix a unique variable name not corresponding to any keyword along with an '=' sign to any event field.

[PATCH v7 15/37] tracing: Add variable support to hist triggers

2017-12-06 Thread Tom Zanussi
Add support for saving the value of a current event's event field by assigning it to a variable that can be read by a subsequent event. The basic syntax for saving a variable is to simply prefix a unique variable name not corresponding to any keyword along with an '=' sign to any event field.