HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
andikleen
pmu-tools
Python2014–2025
andikleen / pmu-tools

pmu-tools

Intel PMU profiling tools

Testing & Quality
Explore on GitHubRead Hacker News discussions
6Distinct people
11Mentions
0Explicit recommenders
2.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Intel PMU profiling tools

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 7:02:26 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year11 dated mentions

Observed mentions: 2014-05-13 20:11:34 UTC to 2025-08-16 23:06:03 UTC.

0122014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC202
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC211
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

2 sources
nkurz·Aug 29, 2014
Agner Fog's guides and the Intel reference documents are the best resources that I've found: http://www.agner.org/optimize/ http://www.intel.com/content/www/us/en/processors/architectu... IACA, perf, pmu-tools, and likwid are very useful tools. https://software.intel.com/en-us/articles/intel-architecture... https://perf.wiki.kernel.org/index.php/Main_Page https://github.com/andikleen/pmu-tools https://code.google.com/p/likwid/
In Minting Money with Monero and CPU Vector Intrinsics
nkurz·May 13, 2014
I think 'perf' is probably lying to you. Although maybe it's not a lie, as your Gist does contain that line '<not supported> dTLB-misses'. Perf tries very hard to be non-CPU specific, and thus doesn't do a great job of handling the CPU specific stuff. What processor are you running this on? If Intel, you might have luck with some of the more Intel specific wrappers here: https://github.com/andikleen/pmu-tools You also might have better luck with 'likwid': https://code.google.com/p/likwid/ Here's the arguments I was giving it to check: sudo likwid -C 1 -g \ INSTR_RETIRED_ANY:FIXC0, \ CPU_CLK_UNHALTED_CORE:FIXC1,\ CPU_CLK_UNHALTED_REF:FIXC2, \ DTLB_LOAD_MISSES_WALK_COMPLETED:PMC0 \ ./bytesum 1gb_file | INSTR_RETIRED_ANY | 7.38826e+08 | | CPU_CLK_UNHAL
Read the rest
TED_CORE | 5.42765e+08 | | CPU_CLK_UNHALTED_REF | 5.42753e+08 | | DTLB_LOAD_MISSES_WALK_COMPLETED | 1.04509e+06 | sudo likwid -C 1 -g \ INSTR_RETIRED_ANY:FIXC0, \ CPU_CLK_UNHALTED_CORE:FIXC1,\ CPU_CLK_UNHALTED_REF:FIXC2, \ DTLB_LOAD_MISSES_WALK_COMPLETED:PMC0 \ ./hugepage_prefetch 1gb_file | INSTR_RETIRED_ANY | 5.79098e+08 | | CPU_CLK_UNHALTED_CORE | 2.63809e+08 | | CPU_CLK_UNHALTED_REF | 2.63809e+08 | | DTLB_LOAD_MISSES_WALK_COMPLETED | 11970 | The other main advantage of 'likwid' is that it allows you to profile just a section of the code, rather than the program as a whole. For odd political reasons, 'perf' doesn't make this possible. ps. I think your 'argc' check is off by one. Since the name of the program is in argv[0], and argc is the length of argv, you want to check 'argc != 2' to confirm that a filename has been given.
In Computers are fast

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.