20.02.2013 Views

Sable CPU Module Specification

Sable CPU Module Specification

Sable CPU Module Specification

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Copyright © 1993 Digital Equipment Corporation.<br />

Table 26:<br />

Flag Description<br />

VALID When set indicates that the data found in the other bits of the control store, the tag store,<br />

and the data store contain valid information. The VALID bit is set only by the B-Cache<br />

controller when a cache block is filled with new data. The VALID bit is cleared only by the<br />

B-Cache controller when a System-bus write requires a cache block invalidation.<br />

DIRTY When set (and VALID bit set) indicates that the data store contains an updated copy of a<br />

main memory location. This cache data must be written back to main memory when the<br />

cache location is victimized. At most, in a Cobra system, there will be only one copy of any<br />

given memory location marked DIRTY. The DIRTY bit is set by the processor performing<br />

a Fast B-Cache write hit cycle, or by the B-Cache assisting the processor perform a STxC<br />

cycle. When the VALID bit is cleared the B-Cache controller will guarantee that the DIRTY<br />

bit is also cleared.<br />

SHARED When set (and VALID bit set) indicates that the data store contains a copy of a main<br />

memory location that another System-bus node also has a copy of. Writes to this location<br />

must ‘‘write-through’’ the cache so that a coherent view of memory is maintained. The<br />

SHARED bit is set by the B-Cache controller when the System-bus CSHARED_L signal<br />

is asserted during cache block allocation or when a System-bus read hits a location found<br />

in the B-Cache (CSHARED_L must be pulled). The SHARED bit is cleared by the B-<br />

Cache controller when it performs a System-bus WRITE and the CSHARED_L signal isn’t<br />

asserted. When the VALID bit is cleared the B-Cache controller guarantees that the DIRTY<br />

bit is also cleared.<br />

PARITY Contains EVEN parity over the contents of the Control Store. The PARITY is valid even if<br />

the VALID bit is not set. Parity is checked by the processor during every B-Cache probe<br />

cycle, and by the B-Cache controller during every System-bus initiated probe cycle. For<br />

details regarding parity error detection refer to Chapter 8.<br />

4.1.2 Tag Store<br />

The Tag Store contains the high order address bits ( for a 4 MB<br />

cache) of the memory location that currently resides in the cache entry. There is a<br />

single parity bit that provides EVEN parity over the complete Tag Store. Once powerup<br />

initialization has occurred, the parity bit will contain valid parity regardless of<br />

the value of the Control Stores VALID bit.<br />

Parity is checked by the processor during every B-Cache probe cycle, and by the B-<br />

Cache controller during every System-bus initiated probe cycle. For details regarding<br />

parity error detection refer to Chapter 8.<br />

4.1.3 Data Store<br />

The Data Store contains the actual data of the memory location that is ‘‘cached’’.<br />

Every cache entry is made up of 8 longwords each longword protected by 7 bits of<br />

EDC. Physically the cache is only 4 longwords wide, so a cache block consists of 2<br />

consecutive addresses aligned on a 32 byte block boundary. After initialization, the<br />

EDC bits are valid regardless of the validity of the Control Store’s VALID bit. Error<br />

84 Functions located elsewhere on the <strong>CPU</strong> module

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!