Writing a Linux Debugger Part 2: Breakpoints

Re:Writing a Linux Debugger Part 2: Breakpoints by pebblexe on Saturday March 25, 2017 @02:52PM (#13956987)

Does anyone know of an easy way to interact with performance monitor counters in Linux? I've been reading stuff by Brendan Gregg about DTrace and the importance of PMCs, and it made it sound like Linux doesn't have the equivalent.

[ Parent | on HN ]

Re:Writing a Linux Debugger Part 2: Breakpoints by caf on Saturday March 25, 2017 @06:18PM (#13957817)

Yes, this is what "perf stat <command>" does. Add more -d options to see more counters, or use -e to ask for specific counter(s) ("perf list" to list them).

[ Parent | on HN ]

Re:Writing a Linux Debugger Part 2: Breakpoints by Langdal on Saturday March 25, 2017 @05:06PM (#13957570)

Another nice tool is likwid. It lets you select a performance counter group (e.g. L3 CACHE) to monitor while running a program. It also provides derived metrics.

https://github.com/RRZE-HPC/likwid

[ Parent | on HN ]

Re:Writing a Linux Debugger Part 2: Breakpoints by CalChris on Saturday March 25, 2017 @03:35PM (#13957181)

VTune has a Linux client. That would be the best by far.

https://software.intel.com/en-us/intel-vtune-amplifier-xe

There's also PAPI and TAU:

http://icl.utk.edu/papi/

http://www.cs.uoregon.edu/research/tau/home.php

[ Parent | on HN ]

Re:Writing a Linux Debugger Part 2: Breakpoints by dima55 on Saturday March 25, 2017 @03:02PM (#13957051)

There are multiple tools, and that's all Brendan Gregg has been talking about for years. Read any non-ancient posts on his blog.

[ Parent | on HN ]

Re:Writing a Linux Debugger Part 2: Breakpoints by adamnemecek on Saturday March 25, 2017 @03:44PM (#13957214)

it's not quite there (AFAIK) yet but here's an attempt https://github.com/dtrace4linux/linux

[ Parent | on HN ]