Lines Matching refs:we

75 that, but first we need to record the data that will be processed by
76 that script.  Theoretically, there are a couple of ways we could do
79 - we could enable every event under the tracing/events/syscalls
82   useful if we want to later use the guidance we get from the
86 - we can enable the sys_enter and/or sys_exit syscalls found under
91 For this script, we only need to know that a syscall was entered; we
92 don't care how it exited, so we'll use 'perf record' to record only
107 Once we have a perf.data file containing our data, we can use the -g
208 Of course, for this script, we're not interested in printing every
209 trace event, but rather aggregating it in a useful way.  So we'll get
211 trace_unhandled() functions, which we won't be using.  That leaves us
232 In trace_end(), we'll simply print the results, but first we need to
233 generate some results to print.  To do that we need to have our
237 we simply increment a count associated with that hash entry indexed by
260 Putting that code into the raw_syscalls__sys_enter() handler, we
262 and having the counts we've tallied as values.