Sable CPU Module Specification
Sable CPU Module Specification Sable CPU Module Specification
Copyright © 1993 Digital Equipment Corporation. As the System-bus is based on a ‘‘snooping’’ protocol, every System-bus transaction is monitored by all System-bus participants. The memory modules can only act as responders or bystanders, and as such only respond to requests from bus commanders. The Processor and I/O subsystems can act as either commanders, responders, or bystanders. Table 63: System-bus Initiated Transactions Transaction Abbrv Systembus cycles Activity Write WR 6 B-Cache probe; 9 IF HIT update/invalidate IF update pull System-bus SHARED, cache block SHARED = prev SHARED Read RD 7 B-Cache probe; Provide data if HIT dirty Exchange XD 7 B-Cache probe (READ); Provide data if HIT dirty No-op Transaction NUT 7 No operation Refer to Table 65 for a detailed description of the control flows for System-bus initiated cycles. 5.2.1 CPU as Commander When one of the CPU module’s processors requests data that isn’t resident on the CPU module, a request is passed to the System-bus interface controller, and a System-bus transaction is initiated. 5.2.2 CPU as Bystander The CPU module is a Bystander when some other System-bus commander has requested data from a resource on the System-bus that doesn’t reside exclusively on the CPU module. As a Bystander, each B-Cache controller may have to update or invalidate a stale datum, or provide dirty data to the System-bus thereby pre-empting a memory module from returning stale data (for that transaction only). 5.2.3 CPU as Responder The CPU module is a Responder when some other System-bus commander has requested data from a System-bus visible CPU module register. CPU Module Transactions 157
Copyright © 1993 Digital Equipment Corporation. 5.3 Control Flow of CPU Module Transactions 5.3.1 Processor Initiated The CPU module B-Cache controller provides B-Cache control under the following circumstances. A B-Cache miss occurs, a LDxC, STxC, FETCH/FETCHM, or a MB is executed, or when a write to a shared cache block is detected. The behavior of the B-Cache controller is based on the current processor cycle type, the state of the B-Cache control bits, and the state of the System-bus. The following table illustrates the control flows for these cycles. Table 64: Processor Initiated Transactions - Control Flow Datum/Cache Cycle Status Size Activity Read HIT† X‡ X Write HIT NOT Shared† X Shared 32 bytes 1Refer to Section 4.2 for details. 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. †‘‘Fast Cache’’ cycles, external logic does not intervene ‡X - don’t care 158 CPU Module Transactions • Block read - Processor managed 32 • Update duplicate tag store • Block written (DIRTY = TRUE) - Processor managed 3 • Request System-bus 345 • System-bus WRITE cycle 15 • Update Cache block (DIRTY = FALSE, SHARED = System-bus shared during write) • Relinquish System-bus • ACK write
- Page 121 and 122: 4.3.1 Duplicate Tag Error Register
- Page 123 and 124: 4.5 Lack of Cache Block Prefetch Co
- Page 125 and 126: Table 37: System-bus Control Regist
- Page 127 and 128: 4.7.2 System-bus Error Register - C
- Page 129 and 130: Table 38: System-bus Error Register
- Page 131 and 132: Table 38 (Cont.): System-bus Error
- Page 133 and 134: 4.7.3 System-bus Error Address Low
- Page 135 and 136: Copyright © 1993 Digital Equipment
- Page 137 and 138: 4.8 Multiprocessor Configuration CS
- Page 139 and 140: 4.9 System Interrupt Clear Register
- Page 141 and 142: 4.10 Address Lock Register - CSR13
- Page 143 and 144: 4.11 Miss Address Register - CSR14
- Page 145 and 146: Table 46 (Cont.): C4 Revision Regis
- Page 147 and 148: Table 48 (Cont.): Interval Timer In
- Page 149 and 150: Table 50: D-bus Microcontroller Clo
- Page 151 and 152: Figure 58: Granting Order rule 4 CP
- Page 153 and 154: Copyright © 1993 Digital Equipment
- Page 155 and 156: Table 54 (Cont.): BIU_CTL Field Des
- Page 157 and 158: Table 57: CPU EEPROM Defaults Locat
- Page 159 and 160: Copyright © 1993 Digital Equipment
- Page 161 and 162: Copyright © 1993 Digital Equipment
- Page 163 and 164: Copyright © 1993 Digital Equipment
- Page 165 and 166: Copyright © 1993 Digital Equipment
- Page 167 and 168: Copyright © 1993 Digital Equipment
- Page 169 and 170: Copyright © 1993 Digital Equipment
- Page 171: Copyright © 1993 Digital Equipment
- Page 175 and 176: Copyright © 1993 Digital Equipment
- Page 177 and 178: Copyright © 1993 Digital Equipment
- Page 179 and 180: Copyright © 1993 Digital Equipment
- Page 181 and 182: Copyright © 1993 Digital Equipment
- Page 183 and 184: Copyright © 1993 Digital Equipment
- Page 185 and 186: Copyright © 1993 Digital Equipment
- Page 187 and 188: Copyright © 1993 Digital Equipment
- Page 189 and 190: Copyright © 1993 Digital Equipment
- Page 191 and 192: Copyright © 1993 Digital Equipment
- Page 193 and 194: Copyright © 1993 Digital Equipment
- Page 195 and 196: Copyright © 1993 Digital Equipment
- Page 197 and 198: Copyright © 1993 Digital Equipment
- Page 199 and 200: Copyright © 1993 Digital Equipment
- Page 201 and 202: Copyright © 1993 Digital Equipment
- Page 203 and 204: Copyright © 1993 Digital Equipment
- Page 205 and 206: Copyright © 1993 Digital Equipment
- Page 207 and 208: Copyright © 1993 Digital Equipment
- Page 209 and 210: Copyright © 1993 Digital Equipment
- Page 211 and 212: CHAPTER 11 PHYSICAL AND ELECTRICAL
- Page 213 and 214: Table 81 (Cont.): MCA240 J5 SIDE 1
- Page 215 and 216: Table 82 (Cont.): MCA44 J1 Side 1 S
- Page 217 and 218: 11.3 CPU Module Max DC Power Requir
- Page 219 and 220: Copyright © 1993 Digital Equipment
- Page 221 and 222: Figure 68: module clocks Cobra - b
Copyright © 1993 Digital Equipment Corporation.<br />
5.3 Control Flow of <strong>CPU</strong> <strong>Module</strong> Transactions<br />
5.3.1 Processor Initiated<br />
The <strong>CPU</strong> module B-Cache controller provides B-Cache control under the following<br />
circumstances. A B-Cache miss occurs, a LDxC, STxC, FETCH/FETCHM, or a MB<br />
is executed, or when a write to a shared cache block is detected.<br />
The behavior of the B-Cache controller is based on the current processor cycle type,<br />
the state of the B-Cache control bits, and the state of the System-bus. The following<br />
table illustrates the control flows for these cycles.<br />
Table 64: Processor Initiated Transactions - Control Flow<br />
Datum/Cache<br />
Cycle Status Size Activity<br />
Read HIT† X‡ X<br />
Write HIT NOT Shared† X<br />
Shared 32 bytes<br />
1Refer to Section 4.2 for details.<br />
2Processor Checks Data EDC.<br />
3Processor Checks Tag Store and Control Store Parity.<br />
4 B-Cache Controller Checks Tag Store and Control Store Parity.<br />
5B-Cache Controller Checks Data EDC.<br />
†‘‘Fast Cache’’ cycles, external logic does not intervene<br />
‡X - don’t care<br />
158 <strong>CPU</strong> <strong>Module</strong> Transactions<br />
• Block read - Processor managed 32<br />
• Update duplicate tag store<br />
• Block written (DIRTY = TRUE) - Processor managed 3<br />
• Request System-bus 345<br />
• System-bus WRITE cycle 15<br />
• Update Cache block (DIRTY = FALSE, SHARED =<br />
System-bus shared during write)<br />
• Relinquish System-bus<br />
• ACK write