Re: [RFC][PATCH 11/21] tracing: Add variable support to hist triggers

2017-02-14 Thread Tom Zanussi
Hi Namhyung, On Mon, 2017-02-13 at 15:03 +0900, Namhyung Kim wrote: > On Wed, Feb 08, 2017 at 11:25:07AM -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

Re: [RFC][PATCH 11/21] tracing: Add variable support to hist triggers

2017-02-14 Thread Tom Zanussi
Hi Namhyung, On Mon, 2017-02-13 at 15:03 +0900, Namhyung Kim wrote: > On Wed, Feb 08, 2017 at 11:25:07AM -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

Re: [RFC][PATCH 11/21] tracing: Add variable support to hist triggers

2017-02-12 Thread Namhyung Kim
On Wed, Feb 08, 2017 at 11:25:07AM -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 not

Re: [RFC][PATCH 11/21] tracing: Add variable support to hist triggers

2017-02-12 Thread Namhyung Kim
On Wed, Feb 08, 2017 at 11:25:07AM -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 not

[RFC][PATCH 11/21] tracing: Add variable support to hist triggers

2017-02-08 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.

[RFC][PATCH 11/21] tracing: Add variable support to hist triggers

2017-02-08 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.