Fujitsu Fujitsu SPARC64 V manual Cache Error Handling, Handling of a Cache Tag Error

Models: Fujitsu SPARC64 V

1 255
Download 255 pages 53.5 Kb
Page 199
Image 199

SPARC64 V Implementation and the Ideal Specification

In the table on page 183 (defining terminology in TABLE P-20), the rows (ASIs 6F16, 7F16, and EF16) with error type of “Not detected (#dv)” or “COREERROR (#dv)” indicate that the SPARC64 V implementation deviates from the ideal specification, which is described in TABLE P-21but is not implemented in SPARC64 V.

TABLE P-21Ideal Handling of ASI Register Errors (not implemented in SPARC64 V)

ASI VA

 

Error

Error Detect

 

 

Register name

RW

Protect

Condition

Error Type

Correction

6F16

Parallel barrier assist

RW

Parity

AUG always

 

 

 

 

 

LDXA

 

 

 

 

 

BV interface

7F16

4016-8816

INTR_DATA0:7_R

R

ECC

LDXA

 

 

 

 

 

intr_receive

EF16

Parallel barrier assist

RW

Parity

AUG always

 

 

 

 

 

LDXA

BV interface

(I)AUG_CRE I(A)UG_CRE (I)AUG_CRE

I(A)UG_CRE

BUSY is set to 0

(I)AUG_CRE I(A)UG_CRE (I)AUG_CRE

W

W

None

Interrupt Receive

W

W

None

P.9 Cache Error Handling

In this section, handling of cache errors of the following types is specified:

Cache tag errors

Cache data errors in I1, D1, and U2 caches

This section concludes with the specification of automatic way reduction in the I1, D1, and U2 caches.

P.9.1 Handling of a Cache Tag Error

Error in D1 Cache Tag and I1 Cache Tag

Both the D1 cache (Data level 1) and the I1 cache (Instruction level 1) maintain a copy of their cache tags in the U2 (unified level 2) cache. The D1 cache tags, the D1 cache tags copy, the I1 cache tags, and the I1 cache tags copy are each protected by parity.

188 SPARC JPS1 Implementation Supplement: Fujitsu SPARC64 V • Release 1.0, 1 July 2002

Page 199
Image 199
Fujitsu Fujitsu SPARC64 V Cache Error Handling, Handling of a Cache Tag Error, Error in D1 Cache Tag and I1 Cache Tag