{"push_id":1134309250,"size":2,"distinct_size":2,"ref":"refs/heads/perf","head":"6c72b9f112adebdbce8c7c655a1515b76341c8a8","before":"53f1bc4ba6b0f4728c8ef78e1b175385be8c6c8e","commits":[{"sha":"3245555903b739986e4cfa52f501634dd12a422d","author":{"name":"Barret Rhoden","email":"2d0cb557c0ff6ef738e972832f2a702bb3e84662@cs.berkeley.edu"},"message":"perf: Handle generic event types\n\nLinux's perf has a bunch of generic, built-in events.  For instance,\n'cycles' or 'cpu-cycles' is translated to whatever arch-specific codes\nare needed.\n\nThose generic events have a special type, e.g. PERF_TYPE_HARDWARE, that\nare part of the perf data ABI.  The generic HW events also happen to\ncorrespond to x86's architectural counters.\n\nUsers can now specify the same generic events as perf with Akaros, at\nleast for the basic hardware counters.  The infrastructure is there if\nwe want to expand to other types and configs.\n\nTo some extent, this is set of event parsing functionality similar to\nand somewhat parallel to libpfm4.  The difference is that libpfm4 has\naccess to all sorts of special counters for particular machines, while\nthese ones are supported on all machines.  You can still use either pfm\nevent strings or these generics.  For instance, the following event\nstrings are equivalent on most Intel machines:\n\n\tcycles \t\t\t(generic)\n\tcpu-cycles \t\t(generic alias)\n\tunhalted_core_cycles \t(libpfm4)\n\tr3c \t\t\t(raw)\n\nSigned-off-by: Barret Rhoden <brho@cs.berkeley.edu>","distinct":true,"url":"https://api.github.com/repos/brho/akaros/commits/3245555903b739986e4cfa52f501634dd12a422d"},{"sha":"6c72b9f112adebdbce8c7c655a1515b76341c8a8","author":{"name":"Barret Rhoden","email":"2d0cb557c0ff6ef738e972832f2a702bb3e84662@cs.berkeley.edu"},"message":"WIP-pop","distinct":true,"url":"https://api.github.com/repos/brho/akaros/commits/6c72b9f112adebdbce8c7c655a1515b76341c8a8"}]}
{"actor":{"display_login":"brho"}}