Re: [PATCH v3 22/33] tracing: Add support for 'field variables'

2017-10-12 Thread Tom Zanussi
Hi Namhyung, On Thu, 2017-10-12 at 11:52 +0900, Namhyung Kim wrote: > On Fri, Sep 22, 2017 at 03:00:02PM -0500, Tom Zanussi wrote: > > Users should be able to directly specify event fields in hist trigger > > 'actions' rather than being forced to explicitly create a variable for > > that purpose.

Re: [PATCH v3 22/33] tracing: Add support for 'field variables'

2017-10-12 Thread Tom Zanussi
Hi Namhyung, On Thu, 2017-10-12 at 11:52 +0900, Namhyung Kim wrote: > On Fri, Sep 22, 2017 at 03:00:02PM -0500, Tom Zanussi wrote: > > Users should be able to directly specify event fields in hist trigger > > 'actions' rather than being forced to explicitly create a variable for > > that purpose.

Re: [PATCH v3 22/33] tracing: Add support for 'field variables'

2017-10-11 Thread Namhyung Kim
On Fri, Sep 22, 2017 at 03:00:02PM -0500, Tom Zanussi wrote: > Users should be able to directly specify event fields in hist trigger > 'actions' rather than being forced to explicitly create a variable for > that purpose. > > Add support allowing fields to be used directly in actions, which >

Re: [PATCH v3 22/33] tracing: Add support for 'field variables'

2017-10-11 Thread Namhyung Kim
On Fri, Sep 22, 2017 at 03:00:02PM -0500, Tom Zanussi wrote: > Users should be able to directly specify event fields in hist trigger > 'actions' rather than being forced to explicitly create a variable for > that purpose. > > Add support allowing fields to be used directly in actions, which >

[PATCH v3 22/33] tracing: Add support for 'field variables'

2017-09-22 Thread Tom Zanussi
Users should be able to directly specify event fields in hist trigger 'actions' rather than being forced to explicitly create a variable for that purpose. Add support allowing fields to be used directly in actions, which essentially does just that - creates 'invisible' variables for each bare

[PATCH v3 22/33] tracing: Add support for 'field variables'

2017-09-22 Thread Tom Zanussi
Users should be able to directly specify event fields in hist trigger 'actions' rather than being forced to explicitly create a variable for that purpose. Add support allowing fields to be used directly in actions, which essentially does just that - creates 'invisible' variables for each bare