PMEVTYPER<n>_EL0, Performance Monitors Event Type Registers, n = 0 - 30

The PMEVTYPER<n>_EL0 characteristics are:

Purpose

Configures event counter n, where n is 0 to 30.

Configuration

External register PMEVTYPER<n>_EL0 bits [31:0] are architecturally mapped to AArch64 System register PMEVTYPER<n>_EL0[31:0].

External register PMEVTYPER<n>_EL0 bits [63:32] are architecturally mapped to AArch64 System register PMEVTYPER<n>_EL0[63:32] when FEAT_PMUv3_TH is implemented, or FEAT_PMUv3p8 is implemented or FEAT_PMUv3_EXT64 is implemented.

External register PMEVTYPER<n>_EL0 bits [31:0] are architecturally mapped to AArch32 System register PMEVTYPER<n>[31:0].

This register is present only when FEAT_PMUv3_EXT is implemented. Otherwise, direct accesses to PMEVTYPER<n>_EL0 are RES0.

PMEVTYPER<n>_EL0 is in the Core power domain.

If event counter n is not implemented:

Attributes

PMEVTYPER<n>_EL0 is a 64-bit register.

This register is part of the PMU block.

Field descriptions

6362616059585756555453525150494847464544434241403938373635343332
313029282726252423222120191817161514131211109876543210
TCTERES0SYNCVSTLCRES0TH
PUNSKNSUNSHMMTSHTRLKRLURLHRES0evtCount[15:10]evtCount[9:0]

TC, bits [63:61]
When FEAT_PMUv3_TH is implemented, (FEAT_PMUv3_EDGE is not implemented or PMU.PMEVTYPER<n>_EL0.TE == 0) and (FEAT_PMUv3_TH2 is not implemented, or n is even or PMU.PMEVTYPER<n>_EL0.TLC IN {0b0x}):

Threshold Control. Defines the threshold function. In the description of this field:

TCMeaning
0b000

Not-equal. The counter increments by VB[n] on each processor cycle when VB[n] is not equal to TH[n].

0b001

Not-equal, count. The counter increments by 1 on each processor cycle when VB[n] is not equal to TH[n].

0b010

Equals. The counter increments by VB[n] on each processor cycle when VB[n] is equal to TH[n].

0b011

Equals, count. The counter increments by 1 on each processor cycle when VB[n] is equal to TH[n].

0b100

Greater-than-or-equal. The counter increments by VB[n] on each processor cycle when VB[n] is greater than or equal to TH[n].

0b101

Greater-than-or-equal, count. The counter increments by 1 on each processor cycle when VB[n] is greater than or equal to TH[n].

0b110

Less-than. The counter increments by VB[n] on each processor cycle when VB[n] is less than TH[n].

0b111

Less-than, count. The counter increments by 1 on each processor cycle when VB[n] is less than TH[n].

Comparisons treat VB[n] and TH[n] as unsigned integer values.

On each processor cycle when the condition specified by PMEVTYPER<n>_EL0.TC[2:1] is true:

On each processor cycle when the condition specified by PMEVTYPER<n>_EL0.TC[2:1] is false:

If PMEVTYPER<n>_EL0.{TC, TLC, TH} are zero then the threshold function is disabled.

The reset behavior of this field is:


When FEAT_PMUv3_TH2 is implemented, PMU.PMEVTYPER<n>_EL0.TE == 0, n is odd and PMU.PMEVTYPER<n>_EL0.TLC == 0b10:

Threshold Control. Defines the threshold function. In the description of this field:

TCMeaning
0b000

Not-equal. The counter increments by V[n-1] on each processor cycle when VB[n] is not equal to TH[n].

0b010

Equals. The counter increments by V[n-1] on each processor cycle when VB[n] is equal to TH[n].

0b100

Greater-than-or-equal. The counter increments by V[n-1] on each processor cycle when VB[n] is greater than or equal to TH[n].

0b110

Less-than. The counter increments by V[n-1] on each processor cycle when VB[n] is less than TH[n].

All other values are reserved.

Comparisons treat VB[n] and TH[n] as unsigned integer values.

On each processor cycle when the condition specified by PMEVTYPER<n>_EL0.TC is true, the counter increments by V[n-1].

On each processor cycle when the condition specified by PMEVTYPER<n>_EL0.TC is false, the counter does not increment.

The reset behavior of this field is:


When FEAT_PMUv3_EDGE is implemented and PMU.PMEVTYPER<n>_EL0.TE == 1:

Threshold Control. Defines the threshold function. In the description of this field:

TCMeaning
0b001

Equal to not-equal. The counter increments on each processor cycle when VB[n] is not equal to TH[n] and VB[n] was equal to TH[n] on the previous processor cycle.

0b010

Equal to/from not-equal. The counter increments on each processor cycle when either:

  • VB[n] is not equal to TH[n] and VB[n] was equal to TH[n] on the previous processor cycle.
  • VB[n] is equal to TH[n] and VB[n] was not equal to TH[n] on the previous processor cycle.
0b011

Not-equal to equal. The counter increments on each processor cycle when VB[n] is equal to TH[n] and VB[n] was not equal to TH[n] on the previous processor cycle.

0b101

Less-than to greater-than-or-equal. The counter increments on each processor cycle when VB[n] is greater than or equal to TH[n] and VB[n] was less than TH[n] on the previous processor cycle.

0b110

Less-than to/from greater-than-or-equal. The counter increments on each processor cycle when either:

  • VB[n] is greater than or equal to TH[n] and VB[n] was less than TH[n] on the previous processor cycle.
  • VB[n] is less than TH[n] and VB[n] was greater than or equal to TH[n] on the previous processor cycle.
0b111

Greater-than-or-equal to less-than. The counter increments on each processor cycle when VB[n] is less than TH[n] and VB[n] was greater than or equal to TH[n] on the previous processor cycle.

All other values are reserved.

Comparisons treat VB[n] and TH[n] as unsigned integer values.

On each processor cycle when the condition specified by PMEVTYPER<n>_EL0.TC is true:

On each processor cycle when the condition specified by PMEVTYPER<n>_EL0.TC is false, the counter does not increment.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

TE, bit [60]
When FEAT_PMUv3_EDGE is implemented:

Threshold Edge. Enables the edge condition. When PMEVTYPER<n>_EL0.TE is 1, the event counter increments on cycles when the result of the threshold condition changes. See PMEVTYPER<n>_EL0.TC for more information.

TEMeaning
0b0

Threshold edge condition disabled.

0b1

Threshold edge condition enabled.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

Bit [59]

Reserved, RES0.

SYNC, bit [58]
When FEAT_SEBEP is implemented:

Synchronous mode. Controls whether a PMU exception generated by the counter is synchronous or asynchronous.

SYNCMeaning
0b0

Asynchronous PMU exception is enabled.

0b1

Synchronous PMU exception is enabled.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

VS, bits [57:56]
When FEAT_PMUv3_SME is implemented:

SVE mode filtering. Controls counting events in Streaming and Non-streaming SVE modes.

VSMeaning
0b00

This mechanism has no effect on the filtering of events.

0b01

The PE does not count events in Streaming SVE mode.

0b10

The PE does not count events in Non-streaming SVE mode.

All other values are reserved.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

TLC, bits [55:54]
When FEAT_PMUv3_TH2 is implemented and n is odd:

Threshold Linking Control. Extends PMEVTYPER<n>_EL0.TC with additional controls for event linking. See PMEVTYPER<n>_EL0.TC.

TLCMeaning
0b00

Threshold linking disabled.

0b01

Threshold linking enabled. If the threshold condition described by PMEVTYPER<n>_EL0.TC is false, the counter increments by V[n-1]. Otherwise, the counter increments as described by PMEVTYPER<n>_EL0.TC.

0b10

Threshold linking enabled. If the threshold condition described by PMEVTYPER<n>_EL0.TC is true, the counter increments by V[n-1]. Otherwise, the counter does not increment.

All other values are reserved.

See PMEVTYPER<n>_EL0.TC for more information

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

Bits [53:44]

Reserved, RES0.

TH, bits [43:32]
When FEAT_PMUv3_TH is implemented:

Threshold value. Provides the unsigned value for the threshold function defined by PMEVTYPER<n>_EL0.TC.

If PMEVTYPER<n>_EL0.{TC, TH} are both zero and either FEAT_PMUv3_TH2 is not implemented or PMEVTYPER<n>_EL0.TLC is also zero, then the threshold function is disabled.

If PMU.PMMIR_EL1.THWIDTH is less than 12, then bits PMEVTYPER<n>_EL0.TH[11:UInt(PMU.PMMIR_EL1.THWIDTH)] are RES0. This accounts for the behavior when writing a value greater-than-or-equal-to 2UInt(PMU.PMMIR_EL1.THWIDTH).

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

P, bit [31]

EL1 filtering. Controls counting events in EL1.

PMeaning
0b0

This mechanism has no effect on filtering of events.

0b1

The PE does not count events in EL1.

If Secure and Non-secure states are implemented, then counting events in Non-secure EL1 is further controlled by PMEVTYPER<n>_EL0.NSK.

If FEAT_RME is implemented, then counting events in Realm EL1 is further controlled by PMEVTYPER<n>_EL0.RLK.

If EL3 is implemented, then counting events in EL3 is further controlled by PMEVTYPER<n>_EL0.M.

The reset behavior of this field is:

U, bit [30]

EL0 filtering. Controls counting events in EL0.

UMeaning
0b0

This mechanism has no effect on filtering of events.

0b1

The PE does not count events in EL0.

If Secure and Non-secure states are implemented, then counting events in Non-secure EL0 is further controlled by PMEVTYPER<n>_EL0.NSU.

If FEAT_RME is implemented, then counting events in Realm EL0 is further controlled by PMEVTYPER<n>_EL0.RLU.

The reset behavior of this field is:

NSK, bit [29]
When EL3 is implemented:

Non-secure EL1 filtering. Controls counting events in Non-secure EL1. If PMEVTYPER<n>_EL0.NSK is not equal to PMEVTYPER<n>_EL0.P, then the PE does not count events in Non-secure EL1. Otherwise, this mechanism has no effect on filtering of events in Non-secure EL1.

NSKMeaning
0b0

When PMEVTYPER<n>_EL0.P == 0, this mechanism has no effect on filtering of events.

When PMEVTYPER<n>_EL0.P == 1, the PE does not count events in Non-secure EL1.

0b1

When PMEVTYPER<n>_EL0.P == 0, the PE does not count events in Non-secure EL1.

When PMEVTYPER<n>_EL0.P == 1, this mechanism has no effect on filtering of events.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

NSU, bit [28]
When EL3 is implemented:

Non-secure EL0 filtering. Controls counting events in Non-secure EL0. If PMEVTYPER<n>_EL0.NSU is not equal to PMEVTYPER<n>_EL0.U, then the PE does not count events in Non-secure EL0. Otherwise, this mechanism has no effect on filtering of events in Non-secure EL0.

NSUMeaning
0b0

When PMEVTYPER<n>_EL0.U == 0, this mechanism has no effect on filtering of events.

When PMEVTYPER<n>_EL0.U == 1, the PE does not count events in Non-secure EL0.

0b1

When PMEVTYPER<n>_EL0.U == 0, the PE does not count events in Non-secure EL0.

When PMEVTYPER<n>_EL0.U == 1, this mechanism has no effect on filtering of events.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

NSH, bit [27]
When EL2 is implemented:

EL2 filtering. Controls counting events in EL2.

NSHMeaning
0b0

The PE does not count events in EL2.

0b1

This mechanism has no effect on filtering of events.

If EL3 is implemented and FEAT_SEL2 is implemented, then counting events in Secure EL2 is further controlled by PMEVTYPER<n>_EL0.SH.

If FEAT_RME is implemented, then counting events in Realm EL2 is further controlled by PMEVTYPER<n>_EL0.RLH.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

M, bit [26]
When EL3 is implemented and AArch64 is supported:

EL3 filtering. Controls counting events in EL3. If PMEVTYPER<n>_EL0.M is not equal to PMEVTYPER<n>_EL0.P, then the PE does not count events in EL3. Otherwise, this mechanism has no effect on filtering of events in EL3.

MMeaning
0b0

When PMEVTYPER<n>_EL0.P == 0, this mechanism has no effect on filtering of events.

When PMEVTYPER<n>_EL0.P == 1, the PE does not count events in EL3.

0b1

When PMEVTYPER<n>_EL0.P == 0, the PE does not count events in EL3.

When PMEVTYPER<n>_EL0.P == 1, this mechanism has no effect on filtering of events.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

MT, bit [25]
When FEAT_MTPMU is implemented or an IMPLEMENTATION DEFINED multi-threaded PMU extension is implemented:

Multithreading.

MTMeaning
0b0

Count events only on controlling PE.

0b1

Count events from any PE with the same affinity at level 1 and above as this PE.

From Armv8.6, the IMPLEMENTATION DEFINED multi-threaded PMU extension is not permitted, meaning if FEAT_MTPMU is not implemented, this field is RES0. See ID_AA64DFR0_EL1.MTPMU.

This field is ignored by the PE and treated as zero when FEAT_MTPMU is implemented and disabled.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

SH, bit [24]
When EL3 is implemented and FEAT_SEL2 is implemented:

Secure EL2 filtering. Controls counting events in Secure EL2. If PMEVTYPER<n>_EL0.SH is equal to PMEVTYPER<n>_EL0.NSH, then the PE does not count events in Secure EL2. Otherwise, this mechanism has no effect on filtering of events in Secure EL2.

SHMeaning
0b0

When PMEVTYPER<n>_EL0.NSH == 0, the PE does not count events in Secure EL2.

When PMEVTYPER<n>_EL0.NSH == 1, this mechanism has no effect on filtering of events.

0b1

When PMEVTYPER<n>_EL0.NSH == 0, this mechanism has no effect on filtering of events.

When PMEVTYPER<n>_EL0.NSH == 1, the PE does not count events in Secure EL2.

The reset behavior of this field is:

When Secure EL2 is not implemented, access to this field is RES0 .


Otherwise:

Reserved, RES0.

T, bit [23]
When FEAT_TME is implemented:

Non-Transactional state filtering bit. Controls counting of events in Non-transactional state.

TMeaning
0b0

This bit has no effect on the filtering of events.

0b1

Do not count Attributable events in Non-transactional state.

For each Unattributable event, it is IMPLEMENTATION DEFINED whether the filtering applies.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

RLK, bit [22]
When FEAT_RME is implemented:

Realm EL1 filtering. Controls counting events in Realm EL1. If PMEVTYPER<n>_EL0.RLK is not equal to PMEVTYPER<n>_EL0.P, then the PE does not count events in Realm EL1. Otherwise, this mechanism has no effect on filtering of events in Realm EL1.

RLKMeaning
0b0

When PMEVTYPER<n>_EL0.P == 0, this mechanism has no effect on filtering of events.

When PMEVTYPER<n>_EL0.P == 1, the PE does not count events in Realm EL1.

0b1

When PMEVTYPER<n>_EL0.P == 0, the PE does not count events in Realm EL1.

When PMEVTYPER<n>_EL0.P == 1, this mechanism has no effect on filtering of events.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

RLU, bit [21]
When FEAT_RME is implemented:

Realm EL0 filtering. Controls counting events in Realm EL0. If PMEVTYPER<n>_EL0.RLU is not equal to PMEVTYPER<n>_EL0.U, then the PE does not count events in Realm EL0. Otherwise, this mechanism has no effect on filtering of events in Realm EL0.

RLUMeaning
0b0

When PMEVTYPER<n>_EL0.U == 0, this mechanism has no effect on filtering of events.

When PMEVTYPER<n>_EL0.U == 1, the PE does not count events in Realm EL0.

0b1

When PMEVTYPER<n>_EL0.U == 0, the PE does not count events in Realm EL0.

When PMEVTYPER<n>_EL0.U == 1, this mechanism has no effect on filtering of events.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

RLH, bit [20]
When FEAT_RME is implemented:

Realm EL2 filtering. Controls counting events in Realm EL2. If PMEVTYPER<n>_EL0.RLH is equal to PMEVTYPER<n>_EL0.NSH, then the PE does not count events in Realm EL2. Otherwise, this mechanism has no effect on filtering of events in Realm EL2.

RLHMeaning
0b0

When PMEVTYPER<n>_EL0.NSH == 0, the PE does not count events in Realm EL2.

When PMEVTYPER<n>_EL0.NSH == 1, this mechanism has no effect on filtering of events.

0b1

When PMEVTYPER<n>_EL0.NSH == 0, this mechanism has no effect on filtering of events.

When PMEVTYPER<n>_EL0.NSH == 1, the PE does not count events in Realm EL2.

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

Bits [19:16]

Reserved, RES0.

evtCount[15:10], bits [15:10]
When FEAT_PMUv3p1 is implemented:

Extension to evtCount[9:0]. For more information, see evtCount[9:0].

The reset behavior of this field is:


Otherwise:

Reserved, RES0.

evtCount[9:0], bits [9:0]

Event to count.

The event number of the event that is counted by event counter PMU.PMEVCNTR<n>_EL0.

The ranges of event numbers allocated to each type of event are shown in 'Allocation of the PMU event number space'.

If FEAT_PMUv3p8 is implemented and PMEVTYPER<n>_EL0.evtCount is programmed to an event that is reserved or not supported by the PE, no events are counted and the value returned by a direct or external read of the PMEVTYPER<n>_EL0.evtCount field is the value written to the field.

Note

Arm recommends this behavior for all implementations of FEAT_PMUv3.

Otherwise, if PMEVTYPER<n>_EL0.evtCount is programmed to an event that is reserved or not supported by the PE, the behavior depends on the value written:

Note

UNPREDICTABLE means the event must not expose privileged information.

The reset behavior of this field is:

Accessing PMEVTYPER<n>_EL0

If FEAT_PMUv3_EXT32 is implemented and any of the following apply, then bits [63:32] of this register are accessible at offset 0xA00 + (4*n):

Otherwise accesses at this offset are IMPLEMENTATION DEFINED.

Note

SoftwareLockStatus() depends on the type of access attempted and AllowExternalPMUAccess() has a new definition from Armv8.4. Refer to the Pseudocode definitions for more information.

Accesses to this register use the following encodings:

When FEAT_PMUv3_EXT64 is implemented

[63:0] Accessible at offset 0x400 + (8 * n) from PMU

When FEAT_PMUv3_EXT32 is implemented

[31:0] Accessible at offset 0x400 + (4 * n) from PMU

When FEAT_PMUv3_EXT32 is implemented and (FEAT_PMUv3_TH is implemented, or FEAT_PMUv3p8 is implemented or FEAT_PMUv3_SME is implemented)

[63:32] Accessible at offset 0xA00 + (4 * n) from PMU


26/03/2024 09:49; 67c0ae5282a7629ba0ea0ba7267b43cd4f7939f6

Copyright © 2010-2024 Arm Limited or its affiliates. All rights reserved. This document is Non-Confidential.