Re: [for-next][PATCH 2/2] tracing: Use temp buffer when filtering events

2020-08-29 Thread Wen Gong
On 2020-08-29 06:55, Steven Rostedt wrote: On Fri, 28 Aug 2020 18:54:50 -0400 Steven Rostedt wrote: On Fri, 28 Aug 2020 18:49:55 -0400 Steven Rostedt wrote: > On Fri, 28 Aug 2020 15:53:06 +0800 > Wen Gong wrote: > > > this patch commit id is : 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 which

Re: [for-next][PATCH 2/2] tracing: Use temp buffer when filtering events

2020-08-28 Thread Steven Rostedt
On Fri, 28 Aug 2020 18:49:55 -0400 Steven Rostedt wrote: > On Fri, 28 Aug 2020 15:53:06 +0800 > Wen Gong wrote: > > > this patch commit id is : 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 which > > has upstream. > > > > how much size is the per cpu buffer? > > seems it is initilized in

Re: [for-next][PATCH 2/2] tracing: Use temp buffer when filtering events

2020-08-28 Thread Steven Rostedt
On Fri, 28 Aug 2020 15:53:06 +0800 Wen Gong wrote: > this patch commit id is : 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 which > has upstream. > > how much size is the per cpu buffer? > seems it is initilized in trace_buffered_event_enable, > it is only 1 page size as below: > void

Re: [for-next][PATCH 2/2] tracing: Use temp buffer when filtering events

2020-08-28 Thread Wen Gong
On 2016-05-04 21:52, Steven Rostedt wrote: From: "Steven Rostedt (Red Hat)" Filtering of events requires the data to be written to the ring buffer before it can be decided to filter or not. This is because the parameters of the filter are based on the result that is written to the ring buffer