On Fri, 1 May 2020 09:38:59 -0600
shuah wrote:
> On 5/1/20 8:17 AM, Steven Rostedt wrote:
> > On Fri, 1 May 2020 22:37:51 +0900
> > Masami Hiramatsu wrote:
> >
> >> Since the kprobe/kprobe_args_type.tc reads out all event logs
> >> from the trace buffer, the test can fail if there is another
>
On 5/1/20 10:20 AM, Steven Rostedt wrote:
On Fri, 1 May 2020 09:38:59 -0600
shuah wrote:
On 5/1/20 8:17 AM, Steven Rostedt wrote:
On Fri, 1 May 2020 22:37:51 +0900
Masami Hiramatsu wrote:
Since the kprobe/kprobe_args_type.tc reads out all event logs
from the trace buffer, the test can
On Fri, 1 May 2020 09:38:59 -0600
shuah wrote:
> On 5/1/20 8:17 AM, Steven Rostedt wrote:
> > On Fri, 1 May 2020 22:37:51 +0900
> > Masami Hiramatsu wrote:
> >
> >> Since the kprobe/kprobe_args_type.tc reads out all event logs
> >> from the trace buffer, the test can fail if there is another
On 5/1/20 8:17 AM, Steven Rostedt wrote:
On Fri, 1 May 2020 22:37:51 +0900
Masami Hiramatsu wrote:
Since the kprobe/kprobe_args_type.tc reads out all event logs
from the trace buffer, the test can fail if there is another
fork event happens.
Use head command to pick only the first kprobe even
On Fri, 1 May 2020 22:37:51 +0900
Masami Hiramatsu wrote:
> Since the kprobe/kprobe_args_type.tc reads out all event logs
> from the trace buffer, the test can fail if there is another
> fork event happens.
> Use head command to pick only the first kprobe event from
> the trace buffer to test th
5 matches
Mail list logo