830Ć0016Ć02 Rev A 11/15/96 Colorado 3 RT6224K hyperSPARC CPU Module Features D Based on ROSS’ fourth-generation — Level 2 MBus support for cache — Zero-wait-state, 512-Kbyte or hyperSPARC processor coherency 1-Mbyte 2nd-level cache — RT620C Central Processing Unit D SPARC compliant — Demand-paged virtual memory (CPU) — SPARC Instruction Set Architec- management — RT626 Cache Controller, Memory ture (ISA) Version 8 compliant D Module design Management, and Tag Unit — Conforms to SPARC Reference — MBus-standard form factor: 3.30” (CMTU) MMU Architecture (8.34 cm) x 5.78” (14.67 cm) — Four (512-Kbyte) or eight — Conforms to SPARC Level 2 MBus — Provides CPU upgrade path at (1-Mbyte) RT628 Cache Data Units Module Specification (Revision 1.2) module level (CDUs) D Dual-clock architecture — Advanced packaging technology Ċ IntraĆModule Bus incorporates low for a compact design voltage logic to reduce power andĊ CPU scaleable up to 166 MHz D increase speed — MBus scaleable up to 66 MHz High performance * D Full multiprocessing implementation D Each hyperSPARC processor features — 152-194 SPECint92 — Hardware support for symmetric, — Superscalar SPARC CPU with inte- — 181-226 SPECfp92 shared-memory multiprocessing grated floating point unit and * in a 50MHz MBus system 8-Kbyte instruction cache RT620C CPU IMCLK OSC IMA[31:0] IMD[63:0] RT626 RT628 RT628 VOLTAGE CMTU CDU CDU REGULATOR + 5V MBus (Level 2) Figure 1. Logic Block Diagram Selection Guide Part Number: RT6224K * Ć125/512 Ć125/1024 Ć142/512 Ć142/1024 Ć150/512 Ć166/512 CPU Operating Frequency (MHz) 125 125 142 142 150 166 Typical Power Consumption (w)** 32 32 36 36 37 40 Second-level Cache Size 512K 1M 512K 1M 512K 512K SPECint92 / SPECfp92 152 / 181 151 / 187 168 / 196 174 / 212 178 / 209 194 / 226 SPECrateint92 / SPECratefp92 3582 / 4202 3647 / 4415 3938 / 4641 3979 / 4890 4109 / 4869 4533 / 5247 (single processor) SPECrateint92 / SPECratefp92 6717 / 7805 6857 / 8323 7528 / 8446 7684 / 9163 7721 / 8769 8453 / 9446 (dual processor) *See Appendix C for hyperSPARC ordering information ** Commercial • ROSS Technology, Inc. • 5316 Hwy. 290 West • Austin, Texas 78735 • TEL (512) 436-2000 •FAX (512) 892-3036 1 830Ć0016Ć02 Rev A 11/15/96 Colorado 3 RT6224K Functional Description Component Overview The RT6224K hyperSPARC Module is a complete SPARC Superscalar SPARC Processor (RT620C) CPU, including on-board primary and secondary cache The RT620C Central Processing Unit is the heart of ROSS’ memories. It is packaged as a compact PCB and interfaces to fourth-generation of microprocessor. The RT620C CPU ar- the remainder of the system via a SPARC-standard MBus chitecture employs two advanced concepts for increasing connector. The CPU on the RT6224K consists of a high- computer system performance: superscalability and superpi- speed superscalar, highly pipelined processor with dual inte- pelining. ger ALUs and an on-chip floating-point unit (RT620C), a Cache Controller, Memory Management, and Tag Unit The RT620C is a high performance full-custom CMOS im- (RT626), and four (512-Kbyte cache configuration) or eight plementation of integrated SPARC integer and floating-point (1-Mbyte cache configuration) RT628 Cache Data Units. The logic, with an on-chip cache for instructions. RT6224K fits within the clearance envelope for MBus mod- Advanced architecture and manufacturing technologies give ules per the SPARC MBus Specification. the RT620C ultra high performance without requiring soft- The RT6224K interfaces to the rest of the system via the ware recompilation. Figure 2 is a logic block diagram of the SPARC MBus and conforms to the SPARC Reference MMU. RT620. This standardization allows the RT6224K to be interchange- IDP. The Integer Data Path comprises several units. Two able with other SPARC MBus-based CPU modules without independent Arithmetic and Logic Units (ALUs) handle inte- having to modify any portion of the memory system or I/O. ger arithmetic, logical, and shift instructions. The Load/Store This CPU “building block” strategy not only decreases the Unit (LSU) handles instructions that load and store data be- user’s time to market, but provides a mechanism for upgrad- tween memory and registers which includes the loading and ing in the field. storing of both integer and floating-point data. The Special IDP Special Registers Integer Registers (IREGS) Floating Point Registers (FREGS) Input Selection Input Selection Input Selection Input Selection ALU ALULDST FPADD FPMUL Align Check Align Check FPDP Floating Program Global Decoder Floating Counter Point Point Dependency Checker Queue Unit Schedule and Control Scheduler Load Store Align Align FPSCHED Exception Logic ISCHED Data Address Instruction Address Instruction Instruction Instruction Cache Intramodule Fetch Bus Controller Interface IFETCH ICACHE IBIU Control Address Out Control Data/ In Instruction Figure 2. RT620C CPU Logic Block Diagram 2 830Ć0016Ć02 Rev A 11/15/96 Colorado 3 RT6224K Register Unit (SRU) handles instructions that read and write Cache Control, Memory Management, and Tag Unit the SPARC Special Registers (SREGS). The Integer Register (RT626) File (IREGS) is also contained in the IDP. The CMTU (RT626) is a combined Cache Controller and FPDP. The Floating-Point Data Path also comprises several Memory Management Unit optimized for multiprocessing units. These are the Floating-Point Queue (FPQ), the Float- systems. The CMTU is a high-speed CMOS implementation ing-Point Arithmetic Unit (FAU), The Floating-Point Multi- of the SPARC Reference MMU, combined with cache, a plier Unit (FMU), the Floating-Point Register File (FREGS), memory controller, and on-chip physical cache tag memory. and the Floating-Point Status Register (FSR). These floating- The CMTU supports the SPARC MBus Level 2 protocol for point units handle all SPARC floating-point instructions. multiprocessing systems. Figure 3 depicts the CMTU block diagram. ISCHED. The Integer Scheduler performs key control func- tions. It provides global instruction decodes to identify which The CMTU directly connects to the RT620C Central Proces- execution unit resources are required, and determines wheth- sing Unit and RT628 Cache Data Units without any external er sequential or simultaneous execution is possible. circuitry. The RT626 CMTU uses four or eight RT628 CDUs to realize 512 Kbytes or 1 Mbyte, respectively, of zero-wait- The ISCHED also determines whether data forwarding can state, direct-mapped virtual cache memory. be performed and whether instruction dispatches (also called “launches”) need to be delayed due to data dependencies. MMU. The MMU portion of the CMTU provides translation The ISCHED initiates instruction launch and identifies and from a 32-bit virtual address (4 gigabytes) to 36-bit physical controls interrupt and trap handling. address (64 gigabytes), as provided in the SPARC reference MMU specification. Virtual addresses are further extended FPSCHED. The Floating-Point Instruction Scheduler per- with the use of a context register, which is used to identify up forms key control functions for the floating-point unit. When to 4096 contexts or tasks. The TLB entries contain context the Integer Unit detects floating-point instructions in the numbers to identify tasks or processes. This minimizes un- decode stage, it offloads these instructions to the floating- necessary TLB entry replacement during task switching. point functional units and continues processing. Therefore, functional blocks exist that perform necessary decode, sched- The CMTU performs its address translation task by compar- uling, and control for the floating-point operations. ing a virtual address supplied by the RT620C through the In- tra-Module Bus to the address tags in the TLB entries. If a The FPSCHED performs floating-point instruction decoding, “hit” occurs, the physical address stored in the TLB is used to resolves floating-point data dependency and data-forwarding translate the virtual-to-physical address. If the virtual address conditions, and provides the ISCHED with floating-point does not match any valid TLB entry, a “miss” occurs. This execution status. Delayed instructions are stored temporarily causes a table walk to be performed by the MMU. The table in the Floating-Point Instruction Queue (FPQ). Instructions walk is a search performed by the MMU through the address are launched from the FPQ as data dependencies are translation tables stored in main memory. Upon finding the resolved. PTE, the MMU translates the address and selects a TLB entry IFETCH. The Instruction Fetch Unit consists of two major for replacement. functional blocks referred to as the Program Counter Unit Cache Controller The CMTU’s cache controller supports (PCU) and the Instruction Fetch Controller (IFETCHC). two modes of caching: write-through with no write allocate The PCU calculates the address of the next instruction to be and copy-back with write allocate. The cache is “virtually in- fetched. It handles instructions that cause program control dexed” and “physically tagged.” transfer, such as CALL and BRANCH. This unit handles both In 1-Mbyte secondary cache versions, the cache is organized integer and floating-point branch instructions. as 16384 lines with two sub-blocks, each of which is 32 bytes. The IFETCHC fetches two instructions at a time, and in each Intra-Module Bus address bits IMA[19:6] select the cache clock cycle, the CPU attempts to launch both at once. line, IMA[5] selects the sub-block, and IMA[4:3] select the ICACHE. The on-chip instruction cache is organized as a 64-bit word of the cache line. In 512-Kbyte secondary cache two way set associative buffer. The ICACHE stores 8 Kbytes versions, only one sub-block is populated, and IMA[18:5] of instructions. Its inclusion follows the Harvard architecture select the cache line and IMA[4:3] select the 64-bit word of approach, reducing bus contention during memory accesses. the cache line. The ICACHE has a high-performance, one-wait-state cache The 16384 cache tag entries in the RT626 are virtual address miss penalty. indexed. From the processor side, the virtual address on the IBIU.