On Thu, 27 Apr 2017 20:51:28 -0600
David Ahern <dsah...@gmail.com> wrote:

> On 4/27/17 8:49 PM, Steven Rostedt wrote:
> > On Thu, 27 Apr 2017 20:13:43 -0600
> > David Ahern <dsah...@gmail.com> wrote:
> >   
> >> On 4/27/17 7:41 PM, Steven Rostedt wrote:  
> >>> On Thu, 27 Apr 2017 19:31:12 -0500
> >>> David Carrillo-Cisneros <davi...@google.com> wrote:
> >>>     
> >>>> When processing tracepoint events, perf report outputs warnings about
> >>>> field not founds. The warnings are usually hidden by perf report UI
> >>>> and appear when using the --stdio option. e.g.
> >>>>
> >>>>   $ perf record -e syscalls:sys_enter_mmap some_load    
> >>
> >> '-e syscalls' vs raw_syscalls suggests an older kernel -- like RHEL6.  
> > 
> > New kernels have both syscalls and raw_syscalls. The raw_syscalls are
> > the true tracepoints that the syscalls use. His option works on
> > 4.11-rc8.  
> 
> 
> What's old is new again?
> 
> root@kenny-jessie4:~# uname -a
> Linux kenny-jessie4 4.11.0-rc8+ #258 SMP Thu Apr 27 08:36:06 PDT 2017
> x86_64 GNU/Linux
> 
> root@kenny-jessie4:~# perf list | grep syscalls
>   raw_syscalls:sys_enter                             [Tracepoint event]
>   raw_syscalls:sys_exit                              [Tracepoint event]
> 
> 
> Is an option needed to enable syscalls vs raw_syscalls?

Yep!

CONFIG_FTRACE_SYSCALLS=y

-- Steve

Reply via email to