Sable CPU Module Specification

Sable CPU Module Specification Sable CPU Module Specification

people.freebsd.org
from people.freebsd.org More from this publisher
20.02.2013 Views

Copyright © 1993 Digital Equipment Corporation. Table 64 (Cont.): Processor Initiated Transactions - Control Flow Datum/Cache Cycle Status Size Activity X 32 bytes LOAD LOCK X X STORE COND - Cacheable X X 2Processor Checks Data EDC. 3Processor Checks Tag Store and Control Store Parity. 4 B-Cache Controller Checks Tag Store and Control Store Parity. 5B-Cache Controller Checks Data EDC. 6System-bus interface Controller Checks System-bus Parity. • Request System-bus 34 • System-bus WRITE cycle 5 • Relinquish System-bus • ACK write • Request System-bus • Probe B-Cache 4 • Same as generic read except if reference to cacheable address space then lock bit set after arbitrating for the System-bus; otherwise no change to lock bit. 6 (Lock bit VALID = TRUE, Lock Address = access address) (IF (B-Cache hit) THEN change Systembus read to NUT.) 2 • Relinquish System-bus • ACK read • Request System-bus • Probe B-Cache 4 • Same as generic write to except fails IF (Lock bit VALID = FALSE). (IF (write failed due to lock bit not set) THEN change System-bus write to NUT.) • Relinquish System-bus • ACK write (conditionally) CPU Module Transactions 161

Copyright © 1993 Digital Equipment Corporation. Table 64 (Cont.): Processor Initiated Transactions - Control Flow Datum/Cache Cycle Status Size Activity STORE COND. I/O X X • Request System-bus • If the CUCERR_L signal is asserted by the responder module during the first cycle 4 of a System-bus transaction when the 21064 is performing a Store Conditional to non-cacheable address space, then the write will not complete, and the Store conditional failed indicators will be signaled to the processor. • Relinquish System-bus • ACK write (conditionally) Processor initiated transactions to non-cacheable address space may be retried by the sytem bus (CERR_L asserted during cycle 3). When this occurs, the C4 will initiate a retry of the transaction (READ or WRITE) without DECchip 21064 intervention required. Multiple retries are allowed and a transaction will either be retried, complete succesfully, or not be acknowledge (error condition). Retry is NOT supported to cacheable address space. 5.3.2 System-bus Initiated The CPU module System-bus interface controller provides B-Cache control when the the System-bus is active. The behavior of the System-bus interface controller is determined by the System-bus transaction, and the state of the B-Cache control bits. Table 65 illustrates the control flows for these cycles. The activity column shows the activity that occurs after the processor has relinquished its ownership of the B-Cache and the B-Cache TAG probe results are available. Table 65: System-bus Initiated Transactions - Control Flow Cycle Probe Result Status Activity Read HIT B-Cache Dirty Assert System-bus DIRTY and SHARED set SHARED bit in Tag Control Store if not already set, cache block remains DIRTY. Provide Data to System-bus 12 1 B-Cache Controller Checks Tag Store and Control Store Parity. 2 B-Cache Controller Checks Data EDC. 162 CPU Module Transactions

Copyright © 1993 Digital Equipment Corporation.<br />

Table 64 (Cont.): Processor Initiated Transactions - Control Flow<br />

Datum/Cache<br />

Cycle Status Size Activity<br />

STORE COND.<br />

I/O<br />

X X<br />

• Request System-bus<br />

• If the CUCERR_L signal is asserted by the responder<br />

module during the first cycle 4 of a System-bus<br />

transaction when the 21064 is performing a Store<br />

Conditional to non-cacheable address space, then<br />

the write will not complete, and the Store conditional<br />

failed indicators will be signaled to the processor.<br />

• Relinquish System-bus<br />

• ACK write (conditionally)<br />

Processor initiated transactions to non-cacheable address space may be retried by the<br />

sytem bus (CERR_L asserted during cycle 3). When this occurs, the C4 will initiate<br />

a retry of the transaction (READ or WRITE) without DECchip 21064 intervention<br />

required. Multiple retries are allowed and a transaction will either be retried, complete<br />

succesfully, or not be acknowledge (error condition). Retry is NOT supported to<br />

cacheable address space.<br />

5.3.2 System-bus Initiated<br />

The <strong>CPU</strong> module System-bus interface controller provides B-Cache control when the<br />

the System-bus is active.<br />

The behavior of the System-bus interface controller is determined by the System-bus<br />

transaction, and the state of the B-Cache control bits. Table 65 illustrates the control<br />

flows for these cycles. The activity column shows the activity that occurs after the<br />

processor has relinquished its ownership of the B-Cache and the B-Cache TAG probe<br />

results are available.<br />

Table 65: System-bus Initiated Transactions - Control Flow<br />

Cycle<br />

Probe Result<br />

Status Activity<br />

Read HIT B-Cache Dirty Assert System-bus DIRTY and SHARED set SHARED bit in Tag Control<br />

Store if not already set, cache block remains DIRTY.<br />

Provide Data to System-bus 12<br />

1 B-Cache Controller Checks Tag Store and Control Store Parity.<br />

2 B-Cache Controller Checks Data EDC.<br />

162 <strong>CPU</strong> <strong>Module</strong> Transactions

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

Saved successfully!

Ooh no, something went wrong!