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 />

5.1.1.7 BARRIER TRANSACTION<br />

The BARRIER transaction appears on the external interface as a result of an MB<br />

instruction. The acknowledgment of the BARRIER transaction tells the 21064 that<br />

all invalidates have been supplied to it, and that any external write buffers have<br />

been pushed out to the coherence point. Any errors detected during these operations<br />

can be reported to the 21064 when the BARRIER transaction is acknowledged. The<br />

Cobra <strong>CPU</strong> will immediately acknowledge this transaction because it does not buffer<br />

block_write transactions.<br />

Figure 63: BARRIER TRANSACTION<br />

Cycle<br />

sysClkOut1_h<br />

cReq_h<br />

cAck_h<br />

0 1 2<br />

LJ-01871-TI0<br />

1. The BARRIER transaction begins. The 21064 places the command code for BAR-<br />

RIER onto the cReq_h outputs.<br />

2. The external logic notices the BARRIER command, and because it has completed<br />

processing the command (it isn’t going to do anything), it places an acknowledge<br />

code on the cAck_h inputs.<br />

3. The 21064 detects the acknowledge on cAck_h, and removes the command. The<br />

external logic removes the acknowledge code from cAck_h. The cycle is finished.<br />

5.1.1.8 FETCH TRANSACTION<br />

A FETCH transaction appears on the external interface as a result of a FETCH<br />

instruction. The transaction supplies an address to the external logic, which the<br />

system chooses to ignore and responds with an immediate acknowledge.<br />

<strong>CPU</strong> <strong>Module</strong> Transactions 153

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

Saved successfully!

Ooh no, something went wrong!