commit | a6b8f1a43c3c576e67020d43fc0a347c96c912b8 | [log] [tgz] |
---|---|---|
author | vlankhaar <vlankhaar@google.com> | Tue Feb 13 09:29:24 2018 -0800 |
committer | lannadorai <lannadorai@gmail.com> | Fri Feb 23 23:43:51 2018 -0800 |
tree | e034862977ce25c077511649f2c69178f6230356 | |
parent | 37169ec8b9476dfce6c0b8f2ffc0a69dbce73d9d [diff] |
Treat multiple, contiguous hugepage regions as a single mapping. A hugepage_text modified region of memory normally results in a single mmap() entry reported in /proc/${pid}/maps, but when a subsequent mlock()/munlock() happens within that region, the mapping will be broken into multiple entries. This attempts to deduce mappings by looking for virtually contiguous mappings that are immediately followed by a non-anonymous-hugepage (i.e. pgoff!=0) mapping afterwards, and using that subsequent mapping to roll pgoff down to the range of anonymous-backed (likely hugepage_text) mappings. PiperOrigin-RevId: 185541172
The perf_to_profile
binary can be used to turn a perf.data file, which is generated by the linux profiler, perf, into a profile.proto file which can be visualized using the tool pprof.
For details on pprof, see https://github.com/google/pprof
THIS IS NOT AN OFFICIAL GOOGLE PRODUCT
To install all dependences and build the binary, run the following commands. These were tested on Debian GNU/Linux 8 (jessie):
sudo apt-get -y install autoconf automake g++ git libelf-dev libssl-dev libtool make pkg-config git clone --recursive https://github.com/google/perf_data_converter.git cd perf_data_converter make perf_to_profile
If you already have protocol buffers and googletest installed on your system, you can compile using your local packages with the following commands:
sudo apt-get -y install autoconf automake g++ git libelf-dev libssl-dev libtool make pkg-config git clone https://github.com/google/perf_data_converter.git cd perf_data_converter make perf_to_profile
Place the perf_to_profile
binary in a place accessible from your path (eg /usr/local/bin
).
There are a small number of tests that verify the basic functionality. To run these, after successful compilation, run:
make check
Profile a command using perf, for example:
perf record /bin/ls
The example command will generate a profile named perf.data, you should convert this into a profile.proto then visualize it using pprof:
perf_to_profile perf.data profile.pb pprof -web profile.pb
Recent versions of pprof will automatically invoke perf_to_profile
:
pprof -web perf.data
We appreciate your help!
Note that perf data converter and quipper projects do not use GitHub pull requests, and that we use the issue tracker for bug reports.