![Intel ITANIUM ARCHITECTURE - SOFTWARE DEVELOPERS VOLUME 3 REV 2.3 Manual Download Page 408](http://html.mh-extra.com/html/intel/itanium-architecture-software-developers-volume-3-rev-2-3/itanium-architecture-software-developers-volume-3-rev-2-3_manual_2073404408.webp)
2:160
Volume 2, Part 1: Debugging and Performance Monitoring
7.2.2
Performance Monitor Overflow Status Registers
(PMC[0]..PMC[3])
Performance monitor interrupts may be caused by an overflow from a generic
performance monitor or an implementation-dependent event from a model-specific
monitor. The four performance monitor overflow registers (PMC[0]...PMC[3]) shown in
indicate which monitor caused the interruption.
Each of the 252 overflow bits in the performance monitoring overflow status
registers(PMC[0]...PMC[3]) corresponds to a generic performance counter pair or to an
implementation-dependent monitor. For generic performance counter pairs, overflow
status bit PMC[i/64]{i%64} corresponds to generic counter pair PMC[i]/PMD[i], where
4<=i<=p, and p is the index of the last implemented generic PMC/PMD pair.
There are currently two criteria for generating a performance monitor interrupt:
1. A generic performance counter pair (PMC[n]/PMD[n]) overflows and its overflow
interrupt bit (PMC[n].oi) is 1.
2. An implementation-dependent monitor wants to report an event with an
interruption.
If any of these criteria are met, the processor will:
• Set the corresponding overflow status bit in PMC[0]..PMC[3] to 1, and
• Raise a Performance Monitor interrupt, and
• Set the freeze bit (PMC[0].fr) which suspends event monitoring.
PMU interrupts are generated by events, such as the overflowing of a generic counter
pair which is configured to interrupt on overflow. Each such event generates one
interrupt. Provided that software does not clear the freeze bit, while either or both of
PSR.up and pp are 1, before clearing the overflow bits, writes to PMCs and PMDs by
software do not generate interrupts, nor cause a monitor which had generated an
interrupt to generate a second interrupt. (For overflow bits in PMC 0, even if either or
both of PSR.up and .pp are 1, software may clear the overflow bits and the freeze bit
with a single write to PMC 0 without causing any additional interrupts to be generated.)
Software may restore PMU state which has the freeze bit equal to 1 and one or more
overflow bits equal to 1 without generating any interrupts provided that it ensures
either that:
• both PSR.up and pp are zero during the restore, or
• the freeze bit is a 1 (and serialized) before any overflow bits are set to 1
When the PMU is disabled by writing a 0 into PSR.up and .pp and serializing this write,
the PMU cannot generate any interrupts and no SW writes to any PMU state can cause
any interrupts.
When a generic performance counter pair (PMC[n]/PMD[n]) overflows and its overflow
interrupt bit (PMC[n].oi) is 0, the corresponding overflow status register bit is set to 1.
However, in this case of counter overflow without interrupt, the freeze bit in the PMC[0]
is left unchanged, and event monitoring continues.
Summary of Contents for ITANIUM ARCHITECTURE - SOFTWARE DEVELOPERS VOLUME 3 REV 2.3
Page 1: ......
Page 11: ...x Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 13: ...1 2 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 33: ...1 22 Volume 1 Part 1 Introduction to the Intel Itanium Architecture ...
Page 57: ...1 46 Volume 1 Part 1 Execution Environment ...
Page 147: ...1 136 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 149: ...1 138 Volume 1 Part 2 About the Optimization Guide ...
Page 191: ...1 180 Volume 1 Part 2 Predication Control Flow and Instruction Stream ...
Page 230: ......
Page 248: ...236 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 250: ...2 2 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 264: ...2 16 Volume 2 Part 1 Intel Itanium System Environment ...
Page 380: ...2 132 Volume 2 Part 1 Interruptions ...
Page 398: ...2 150 Volume 2 Part 1 Register Stack Engine ...
Page 486: ...2 238 Volume 2 Part 1 IA 32 Interruption Vector Descriptions ...
Page 750: ...2 502 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 754: ...2 506 Volume 2 Part 2 About the System Programmer s Guide ...
Page 796: ...2 548 Volume 2 Part 2 Interruptions and Serialization ...
Page 808: ...2 560 Volume 2 Part 2 Context Management ...
Page 842: ...2 594 Volume 2 Part 2 Floating point System Software ...
Page 850: ...2 602 Volume 2 Part 2 IA 32 Application Support ...
Page 862: ...2 614 Volume 2 Part 2 External Interrupt Architecture ...
Page 870: ...2 622 Volume 2 Part 2 Performance Monitoring Support ...
Page 891: ......
Page 1099: ...3 200 Volume 3 Instruction Reference padd Interruptions Illegal Operation fault ...
Page 1295: ...3 396 Volume 3 Resource and Dependency Semantics ...
Page 1296: ......
Page 1302: ...402 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 1494: ...4 192 Volume 4 Base IA 32 Instruction Reference FWAIT Wait See entry for WAIT ...
Page 1647: ...Volume 4 Base IA 32 Instruction Reference 4 345 ROL ROR Rotate See entry for RCL RCR ROL ROR ...
Page 1884: ...4 582 Volume 4 IA 32 SSE Instruction Reference ...
Page 1885: ...Index Intel Itanium Architecture Software Developer s Manual Rev 2 3 Index ...
Page 1886: ...Index Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 1898: ...INDEX Index 12 Index for Volumes 1 2 3 and 4 ...