background image

19-124 Vol. 3B

PERFORMANCE-MONITORING EVENTS

2B

H

See 

Table 

18-2 

and 

Table 

18-5

L2_LOCK.(Core, Cache Line 

State)

L2 locked accesses.

This event counts all locked accesses to cache lines that 

miss the L1 data cache. 
The event can count occurrences for this core or both cores. 

It can also count accesses to cache lines at different MESI 

states.

2E

H

See 

Table 

18-2, 

Table 

18-4, 

and 

Table 

18-5

L2_RQSTS.(Core, Prefetch, 

Cache Line State)

L2 cache requests.

This event counts all completed L2 cache requests. This 

includes L1 data cache reads, writes, and locked accesses, 

L1 data prefetch requests, instruction fetches, and all L2 

hardware prefetch requests. 
This event can count occurrences:
• For this core or both cores.

• Due to demand requests and L2 hardware prefetch 

requests together, or separately.

• Of accesses to cache lines at different MESI states.

2E

H

41

H

L2_RQSTS.SELF.

DEMAND.I_STATE

L2 cache demand 

requests from this 

core that missed the 

L2.

This event counts all completed L2 cache demand requests 

from this core that miss the L2 cache. This includes L1 data 

cache reads, writes, and locked accesses, L1 data prefetch 

requests, and instruction fetches. 
This is an architectural performance event.

2E

H

4F

H

L2_RQSTS.SELF.

DEMAND.MESI

L2 cache demand 

requests from this 

core.

This event counts all completed L2 cache demand requests 

from this core. This includes L1 data cache reads, writes, 

and locked accesses, L1 data prefetch requests, and 

instruction fetches. 
This is an architectural performance event.

30

H

See 

Table 

18-2, 

Table 

18-4, 

and 

Table 

18-5

L2_REJECT_BUSQ.(Core, 

Prefetch, Cache Line State)

Rejected L2 cache 

requests.

This event indicates that a pending L2 cache request that 

requires a bus transaction is delayed from moving to the bus 

queue. Some of the reasons for this event are: 
• The bus queue is full. 

• The bus queue already holds an entry for a cache line in 

the same set. 

The number of events is greater or equal to the number of 

requests that were rejected. 
• For this core or both cores. 

• Due to demand requests and L2 hardware prefetch 

requests together, or separately. 

• Of accesses to cache lines at different MESI states.

32

H

See 

Table 

18-2

L2_NO_REQ.(Core)

Cycles no L2 cache 

requests are pending.

This event counts the number of cycles that no L2 cache 

requests were pending from a core. When using the 

BOTH_CORE modifier, the event counts only if none of the 

cores have a pending request. The event counts also when 

one core is halted and the other is not halted. 
The event can count occurrences for this core or both cores.

3A

H

00

H

EIST_TRANS

Number of Enhanced 

Intel SpeedStep 

Technology (EIST) 

transitions.

This event counts the number of transitions that include a 

frequency change, either with or without voltage change. 

This includes Enhanced Intel SpeedStep Technology (EIST) 

and TM2 transitions.
The event is incremented only while the counting core is in 

C0 state. Since transitions to higher-numbered CxE states 

and TM2 transitions include a frequency change or voltage 

transition, the event is incremented accordingly. 

Table 19-23.  Non-Architectural Performance Events in Processors Based on Intel® Core™ Microarchitecture (Contd.)

Event 

Num

Umask

Value

Event Name 

Definition

Description and

Comment