retsnoop: v0.9.1 release version

Bump version to v0.9.1 for newly added convenience features.

Signed-off-by: Andrii Nakryiko <[email protected]>

retsnoop: v0.9 release with --trace mode

Bump retsnoop version to v0.9.

Signed-off-by: Andrii Nakryiko <[email protected]>

retsnoop: release v0.8.3

With ability to filter by kernel module globs, release new patch
version.

Signed-off-by: Andrii Nakryiko <[email protected]>

retsnoop: v0.8.2 release

Bump patch release version after adding few quality of life
improvements.

Signed-off-by: Andrii Nakryiko <[email protected]>

retsnoop: bump version to 0.8.1

Prepare patch version release.

Signed-off-by: Andrii Nakryiko <[email protected]>

retsnoop: release v0.8 version

Bump version to v0.8 given all the LBR-specific additions.

Signed-off-by: Andrii Nakryiko <[email protected]>

retsnoop: release v0.7

Bump version to v0.7.

Signed-off-by: Andrii Nakryiko <[email protected]>

retsnoop: add -V (--version) command to print retsnoop version

Add ability to fetch retsnoop's version at runtime.

Signed-off-by: Andrii Nakryiko <[email protected]>

retsnoop: use hardware event for LBR

Using INTEL_FIXED_VLBR_EVENT causes issues in practice: after a while
(I've seen 27 hours) LBR data becomes garbage. Song Liu suggested using
hardware events as a work around. Do just that for now.

Signed-off-by: Andrii Nakryiko <[email protected]>

retsnoop: filter out irrelevant LBRs

Capture sizes of kernel functions and use that to determine last traced
function address range. Having that, it's possible to filter out few
last LBRs that captured BPF/perf/kprobe internals that have nothing to
do with traced code.

Signed-off-by: Andrii Nakryiko <[email protected]>