LIBPFM(3) | Linux Programmer's Manual | LIBPFM(3) |
libpfm_intel_adl_glc - support for Intel Alderlake Goldencove (P-Core) core PMU
#include <perfmon/pfmlib.h> PMU name: adl_glc PMU desc: Intel Alderlake Goldencove (P-core)
The library supports the Intel Alderlake Goldencove (P-Core) core PMU. It should be noted that this PMU model only covers each core's PMU and not the socket level PMU. Because the processor uses a hybrid architecture with a P-Core and E-Core with a different PMU model, it may be necessary to force a PMU instance name to get the desired encoding. For instance, to encode for the P-Core adl_glc::BR_INST_RETIRED and for the E-core adl_grt::BR_INST_RETIRED.
On Adlerlake Goldencove (P-Core), the number of generic counters depends on the Hyperthreading (HT) mode.
The pfm_get_pmu_info() function returns the maximum number of generic counters in num_cntrs.
The following modifiers are supported on Intel SapphireRapid processors:
For Alderlake Goldencove (P-Core), the library uses the hardcoded bubble width and bubble length provided by Intel preset events. It is not possible to tweak either the latency or the width via the library.
Intel Alderlake Goldencove (P-Core) supports two encodings for offcore_response events (0x2a, 0x2b). In the library, these are called OCR0 and OCR1. The two encodings are equivalent. On Linux, the kernel can schedule any OCR encoding into any of the two OCR counters. The offcore_response events are exposed as a normal events by the library. The extra settings are exposed as regular umasks. The library takes care of encoding the events according to the underlying kernel interface.
On Intel Alderlake Goldencove (P-Core), the event is treated as a regular event with a flat set of umasks to choose from. It is not possible to combine the various requests, supplier, snoop bits anymore. The library offers the list of validated combinations as per Intel's official event list.
Stephane Eranian <eranian@gmail.com>
February, 2024 |