Intel PT addr_filter too narrow causes TIP packet to be missing on indirect call

Software Tuning, Performance Optimization & Platform Monitoring

Discussion regarding monitoring and software tuning methodologies, Performance Monitoring Unit (PMU) of Intel microprocessors, and platform updating.

Intel PT addr_filter too narrow causes TIP packet to be missing on indirect call

3,255 Views

I want to observe the TIP packets for both possible target addresses.

I set:

filter 0x5b2c46d30cb4/0x20

But in this case, the trace does not contain TIP packets indicating the call target.

However, when I move the filter earlier:

filter 0x5b2c46d30ca3/0x20

I see both TIPs correctly.

Are there any known limitations where addr_filter must include a few instructions preceding an indirect call in order for a TIP packet to be emitted?
Alternatively, are there any other conditions that could result in missing or omitted TIP packets?

Thank you!

- CPU: Intel 12th Gen Core i7-12700
- Kernel: Linux 6.8.0-60-generic

Link Copied

0 Replies

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.