events-nmi.txt 1.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243
  1. NMI Trace Events
  2. These events normally show up here:
  3. /sys/kernel/debug/tracing/events/nmi
  4. --
  5. nmi_handler:
  6. You might want to use this tracepoint if you suspect that your
  7. NMI handlers are hogging large amounts of CPU time. The kernel
  8. will warn if it sees long-running handlers:
  9. INFO: NMI handler took too long to run: 9.207 msecs
  10. and this tracepoint will allow you to drill down and get some
  11. more details.
  12. Let's say you suspect that perf_event_nmi_handler() is causing
  13. you some problems and you only want to trace that handler
  14. specifically. You need to find its address:
  15. $ grep perf_event_nmi_handler /proc/kallsyms
  16. ffffffff81625600 t perf_event_nmi_handler
  17. Let's also say you are only interested in when that function is
  18. really hogging a lot of CPU time, like a millisecond at a time.
  19. Note that the kernel's output is in milliseconds, but the input
  20. to the filter is in nanoseconds! You can filter on 'delta_ns':
  21. cd /sys/kernel/debug/tracing/events/nmi/nmi_handler
  22. echo 'handler==0xffffffff81625600 && delta_ns>1000000' > filter
  23. echo 1 > enable
  24. Your output would then look like:
  25. $ cat /sys/kernel/debug/tracing/trace_pipe
  26. <idle>-0 [000] d.h3 505.397558: nmi_handler: perf_event_nmi_handler() delta_ns: 3236765 handled: 1
  27. <idle>-0 [000] d.h3 505.805893: nmi_handler: perf_event_nmi_handler() delta_ns: 3174234 handled: 1
  28. <idle>-0 [000] d.h3 506.158206: nmi_handler: perf_event_nmi_handler() delta_ns: 3084642 handled: 1
  29. <idle>-0 [000] d.h3 506.334346: nmi_handler: perf_event_nmi_handler() delta_ns: 3080351 handled: 1