Table of Contents
Advertisement
Table D–1 Ibox Status Register Fields (Continued)
Name
Bits
LS0
<38>
TRAP
<37:34>
TYPE<3:0>
Type
Description
RO
ProfileMe Load-Store Order Trap.
LS0 <38> RO ProfileMe Load-Store Order Trap.
If the profiled instruction caused a replay trap, this bit
indicates that the precise trap cause was an Mbox load-store
order replay trap. If clear, this bit indicates that the replay trap
was any one of the following:
Mbox load-load order
Mbox load queue full
Mbox store queue full
Mbox wrong size trap (such as, STL ••LDQ)
Mbox Bcache alias (2 physical addresses map to same Bcache
line)
Mbox Dcache alias (2 physical addresses map to same Dcache
line)
Icache parity error
Dcache ECC error
RO
RO ProfileMe Trap Types.
If the profiled instruction caused a trap (indicated by
I_STAT<TRP>), this field indicates the trap type as listed here:
Value
Trap Type
0 Replay
1 Invalid (unused)
2 DTB Double miss (3 level page tables)
3 DTB Double miss (4 level page tables)
4 Floating point disabled
5 Unaligned Load/Store
6 DTB Single miss
7 Dstream Fault
8 OPCDEC
9 Invalid (use PMPC, described below)
10 Machine Check
11 Invalid (use PMPC, described below)
12 Arithmetic
13 Invalid (use PMPC, described below)
14 MT_FPCR
15 Reset
Traps due to ITB miss, Istream access violation, or interrupts
are not reported in the trap type field because they do not cause
pipeline aborts.
Continued on next page
Registers
D-3
Advertisement
Table of Contents
Troubleshooting
