Alpha 21264/EV67 Microprocessor Hardware Reference Manual Order Number: DS–0028B–TE This manual is directly derived from the internal 21264/EV67 Specifications, Revi- sion 1.4. You can access this hardware reference manual in PDF format from the following site: ftp://ftp.compaq.com/pub/products/alphaCPUdocs Revision/Update Information: This is a revised document. It supercedes...
Audience This manual is for system designers and programmers who use the Alpha 21264/EV67 microprocessor (referred to as the 21264/EV67). Content This manual contains the following chapters and appendixes: Chapter 1, Introduction, introduces the 21264/EV67 and provides an overview of the Alpha architecture.
Page 18
PALcode. Appendix E, 21264/EV67-to-Bcache Pin Interconnections, provides the pin interface between the 21264/EV67 and Bcache SSRAMs. The Glossary lists and defines terms associated with the 21264/EV67. An Index is provided at the end of the document. Documentation Included by Reference...
Bits and fields are cleared when read. Unless otherwise specified, such bits cannot be written. Reserved Bits and fields are reserved by Compaq and should not be used; however, zeros can be written to reserved fields that cannot be masked. Read Only The value may be read by software.
Page 20
[:]. For example, [9:7,5,2:0] specifies bits 9,8,7,5,2,1, and 0. Similarly, single bits are frequently indicated with square brackets. For example, [27] specifies bit 27. See also Field Notation. Caution Cautions indicate potential damage to equipment or loss of data. Alpha 21264/EV67 Hardware Reference Manual...
Page 21
The bit range may, but need not necessarily, correspond to the bit Extent in the register. See the explanation above Table 5–1 for more information. Signal Names The following examples describe signal-name conventions used in this document. Alpha 21264/EV67 Hardware Reference Manual Words Bytes ½...
Page 22
Boldface, mixed-case type denotes signal names that are assigned internal and external to the 21264/EV67 (that is, the signal traverses a chip interface pin). When a signal has high and low assertion states, a lower- case italic x represents the assertion states.
Page 23
Do not care. A capital X represents any valid value. Alpha 21264/EV67 Hardware Reference Manual xxiii...
This use of resources makes it easy to build implementations that issue multiple instructions every CPU cycle. The 21264/EV67 uses a set of subroutines, called privileged architecture library code (PALcode), that is specific to a particular Alpha operating system implementation and hardware platform.
1.1.1 Addressing The basic addressable unit in the Alpha architecture is the 8-bit byte. The 21264/EV67 supports a 48-bit or 43-bit virtual address (selectable under IPR control). Virtual addresses as seen by the program are translated into physical memory addresses by the memory-management mechanism.
The 21264/EV67 can issue four Alpha instructions in a single cycle, thereby minimiz- ing the average cycles per instruction (CPI). A number of low-latency and/or high- throughput features in the instruction issue unit and the onchip components of the mem- ory subsystem further reduce the average CPI.
Page 28
Chip and module level test support, including an instruction cache test interface to support chip and module level testing. • A 2.0-V external interface. Refer to Chapter 9 for 21264/EV67 dc and ac electrical characteristics. Refer to the Alpha Architecture Handbook, Version 4 implementation-dependent information. Introduction 1–4...
This chapter provides both an overview of the 21264/EV67 microarchitecture and a sys- tem designer’s view of the 21264/EV67 implementation of the Alpha architecture. The combination of the 21264/EV67 microarchitecture and privileged architecture library code (PALcode) defines the chip’s implementation of the Alpha architecture. If a certain piece of hardware seems to be “architecturally incomplete,”...
There can be up to 80 instructions, in 20 successive fetch slots, in flight between the register rename mappers and the end of the pipeline. The VPC logic contains a 20-entry table to store these fetched VPC addresses. Internal Architecture 2–2 Alpha 21264/EV67 Hardware Reference Manual...
4K entry table of 2-bit saturating counters. The value of the saturating counter determines the predication, taken/not-taken, of the cur- rent branch. Internal Architecture 2–4 Choice Predictor Branch Address FM-05810.AI4 Local Index Predictor 1K x 3 Local Branch Prediction FM-05811.AI4 Alpha 21264/EV67 Hardware Reference Manual...
The ITB supports an 8-bit ASN and contains an ASM bit. The Icache is virtually addressed and contains the access-check information, so the ITB is accessed only for Istream references that miss in the Icache. Istream transactions to I/O address space are UNDEFINED. Alpha 21264/EV67 Hardware Reference Manual 21264/EV67 Microarchitecture Global Predictor 4K x 2 FM-05812.AI4...
2.1.1.6 Integer Issue Queue The 20-entry integer issue queue (IQ), associated with the integer execution units (Ebox), issues the following types of instructions at a maximum rate of four per cycle: Internal Architecture 2–6 Alpha 21264/EV67 Hardware Reference Manual...
The add and multiply arbiters pick one requester per cycle, while the store pipeline arbiter picks two requesters per cycle, one for each store pipeline. Alpha 21264/EV67 Hardware Reference Manual 21264/EV67 Microarchitecture Internal Architecture...
“subclusters”, named upper (U) and lower (L). Fig- ure 2–6 shows the integer execution unit. In the figure, iop_wr is the cross-cluster bus for moving integer result values between clusters. Internal Architecture 2–8 Alpha 21264/EV67 Hardware Reference Manual...
The 72 Fbox register file entries contain storage for the values of the 31 Alpha floating- point registers (F31 is not stored) and 41 values written by instructions that have not been retired. Internal Architecture 2–10 LK98-0004A Alpha 21264/EV67 Hardware Reference Manual...
The duplicate Dcache tag (DTAG) array holds a duplicate copy of the Dcache tags and is used by the Cbox when processing Dcache fills, Icache fills, and system port probes. 2.1.5 Onchip Caches The 21264/EV67 contains two onchip primary-level caches. 2.1.5.1 Instruction Cache The instruction cache (Icache) is a 64KB virtual-addressed, 2-way set-predict cache.
The Dcache contains two sets, each with 512 rows containing 64-byte blocks per row (that is, 32K bytes of data per set). The 21264/EV67 requires two additional bits of vir- tual address beyond the bits that specify an 8KB page, in order to specify a Dcache row index.
The 7-stage pipeline provides an optimized environment for executing Alpha instruc- tions. The pipeline stages (0 to 6) are shown in Figure 2–8 and described in the follow- ing paragraphs. Alpha 21264/EV67 Hardware Reference Manual Pipeline Organization Internal Architecture 2–13...
Page 42
ALU Shifter Multiplier Integer Register File Address Address 64KB Data Cache Floating-Point Add, Divide, Floating- and Square Root Point Register Floating-Point File Multiply Alpha 21264/EV67 Hardware Reference Manual System (64 Bits) Interface Unit Cache (128 Bits) Physical Address (44 Bits) FM-05575.AI4...
IQ or FQ two cycles after they are issued. For example, if an instruction is issued in cycle n, it remains in the FQ or IQ in cycle n+1 but does not request service, and is deleted in cycle n+2. Alpha 21264/EV67 Hardware Reference Manual Internal Architecture 2–15...
2–16 Penalty (Cycles) Comments Integer or floating-point conditional branch misprediction. Memory format JSR or HW_RET. Load-load order or store-load order. — — — — 13+latency Add latency of instruction. See Section 2.3.3 for instruction latencies. Alpha 21264/EV67 Hardware Reference Manual...
Consumer fst or ftoi. Measured from when an fadd is issued from the FQ to when an fst or ftoi is issued from the IQ. Internal Architecture 2–20 Ebox IPRs = 1. Ibox and Mbox IPRs = 3. Alpha 21264/EV67 Hardware Reference Manual...
11 plus 9 from Table 2–4. Latency is 11 if hardware detects that no exception is possible (see Section 2.4.1). Branch instruction mispredict is reported in stage 7. JSR instruction mispredict is reported in stage 8. ) OR (EXP <= 2 ) OR (EXP <= 382 Alpha 21264/EV67 Hardware Reference Manual...
See Table 6–3. 2.6.2 Prefetch with Modify Intent: LDS Instruction The 21264/EV67 processes an LDS instruction, with F31 as the destination, as a prefetch with modify intent transaction (ReadBlkMod command). If the transaction hits a dirty Dcache block, the instruction is dismissed. Otherwise, the addressed cache block is allocated into the Dcache for write access, with its dirty and modified bits set.
2.7 Special Cases of Alpha Instruction Execution This section describes the mechanisms that the 21264/EV67 uses to process irregular instructions in the Alpha instruction set, and cases in which the 21264/EV67 processes instructions in a non-intuitive way. 2.7.1 Load Hit Speculation The latency of integer load instructions that hit in the Dcache is three cycles.
Dcache, even if they are not dependent on the load data. However, if software misses are likely, the 21264/EV67 can still benefit from scheduling the instruction stream for Dcache miss latency. The 21264/EV67 includes a saturating counter that is incremented when load instructions hit and is decremented when load instructions miss.
IQ. 2.7.3 CMOV Instruction For the 21264/EV67, the Alpha CMOV instruction has three operands, and so presents a special case. The required operation is to move either the value in register Rb or the value from the old physical destination register into the new destination register, based upon the value in Ra.
The Fbox add pipeline executes floating-point CMOV instructions as two distinct 4-cycle latency operations. 2.8 Memory and I/O Address Space Instructions This section provides an overview of the way the 21264/EV67 processes memory and I/ O address space instructions. The 21264/EV67 supports, and internally recognizes, a 44-bit physical address space that is divided equally between memory address space and I/O address space.
Mbox. Internal Architecture 2–28 Load Byte/Word Load Longword No merge No merge No merge Merge up to 32 bytes No merge No merge Alpha 21264/EV67 Hardware Reference Manual Load Quadword No merge No merge Merge up to 64 bytes...
Table 2–8 Rules for I/O Address Space Store Instruction Data Merging Merge Register/ Replayed Instruction Byte/Word Longword Quadword Table 2–8 shows some of the following rules: Alpha 21264/EV67 Hardware Reference Manual Memory and I/O Address Space Instructions Store Byte/Word Store Longword No merge No merge...
Because all memory transactions are to 64-byte blocks, efficiency is improved by merg- ing several small data transactions into a single larger data transaction. Table 2–9 lists the rules the 21264/EV67 uses when merging memory transactions into 64-byte natu- rally aligned data block transactions. Rows represent the merged instruction in the MAF and columns represent the new issued transaction.
Load memory to address X Store memory to address X Store memory to address X The 21264/EV67 maintains the default I/O instruction ordering as shown in Table 2–11 (assume address X and address Y are different). Table 2–11 I/O Reference Ordering...
When the SYSBUS_MB_ENABLE bit equals 0, the Cbox CSR MB_CNT[3:0] field contains the number of pending uncommitted transac- tions. The counter will increment for each of the following commands: • RdBlk, RdBlkMod, RdBlkI Internal Architecture 2–32 Alpha 21264/EV67 Hardware Reference Manual...
When all of the above have occurred and a probe response has been sent to the sys- tem for the marked probe queue entry, instruction execution continues with the instruction after the MB. Alpha 21264/EV67 Hardware Reference Manual I/O Write Buffer and the WMB Instruction Internal Architecture...
Load instructions (HW_LDs) to a virtual page table entry (VPTE) are processed by the 21264/EV67 to avoid litmus test problems associated with the ordering of memory transactions from another processor against loading of a page table entry and the subse- quent virtual-mode load from this processor.
SYSBUS_MB_ENABLE), the Cbox sig- nals the Ibox to clear IPR scoreboard bit [0]. The 21264/EV67 uses a similar mechanism to process Istream TB misses and fills to the PTE for the Istream. 1. The integer queue issues a HW_LD instruction with VPTE.
Performance Measurement Support—Performance Counters 2.13 Performance Measurement Support—Performance Counters The 21264/EV67 provides hardware support for two methods of obtaining program performance feedback information. The two methods do not require program modifica- tion. The first method offers similar capabilities to earlier microprocessor performance counters.
UNDZ [60] Underflow to zero. When UNDZ is set together with UNFD, underflow traps are disabled and the 21264/EV67 places a true zero in the destination register. See UNFD, above. [59:58] Dynamic rounding mode. Indicates the rounding mode to be used by an IEEE...
Denormal operand. Reserved [47:0] — — Alpha architecture FPCR bit 47 (DNOD) is not implemented by the 21264/EV67. 2.15 AMASK and IMPLVER Instruction Values The AMASK and IMPLVER instructions return processor type and supported architec- ture extensions, respectively. 2.15.1 AMASK The 21264/EV67 returns the AMASK instruction values provided in Table 2–15.
2.16 Design Examples The 21264/EV67 can be designed into many different uniprocessor and multiprocessor system configurations. Figures 2–12 and 2–13 illustrate two possible configurations. These configurations employ additional system/memory controller chipsets. Figure 2–12 shows a typical uniprocessor system with a second-level cache. This sys- tem configuration could be used in standalone or networked workstations.
Internal Architecture 2–40 21272 Core Logic Chipset Control Chip Data Slice Chips Host PCI Host PCI Bridge Chip Bridge Chip 64-bit PCI Bus 64-bit PCI Bus Alpha 21264/EV67 Hardware Reference Manual DRAM Arrays Address Data DRAM Arrays Address Data FM-05574-EV67...
This chapter contains the 21264/EV67 microprocessor logic symbol and provides infor- mation about signal names, their function, and their location. This chapter also describes the mechanical specifications of the 21264/EV67. It is organized as follows: • The 21264/EV67 logic symbol •...
3.2 21264/EV67 Signal Names and Functions Table 3–1 defines the 21264/EV67 signal types referred to in this section. Table 3–1 Signal Pin Types Definitions Signal Type Inputs I_DC_REF I_DA I_DA_CLK Outputs O_OD O_OD_TP O_PP O_PP_CLK Bidirectional B_DA_OD B_DA_PP Other Spare...
Page 72
BcDataOutClk_x[3:0] clocks. Tag parity state bit. Tag shared state bit. The 21264/EV67 will write a 1 on this sig- nal line if another agent has a copy of the cache line. Tag valid state bit. If set, this line indicates that the cache line is valid.
Page 73
Count Description A skew-controlled differential 50% duty cycle copy of the sys- tem clock. It is used by the 21264/EV67 as a reference, or framing, clock. These six interrupt signal lines may be asserted by the system. The response of the 21264/EV67 is determined by the system software.
BiST. If the Icache BiST passes, the pin is deasserted at the end of the BiST operation; otherwise, it remains high. The 21264/EV67 generates a timeout reset signal if an instruc- tion is not retired within one billion cycles. The 21264/EV67 signals the timeout reset event by outputting a 256 GCLK cycle wide pulse on TestStat_H.
Page 75
Provides an external test point to measure phase alignment of the PLL. A skew-controlled differential 50% duty cycle copy of the system clock. It is used by the 21264/EV67 as a reference, or framing, clock. 3.3-V dedicated power supply for the 21264/EV67 PLL.
I_DA Pin Assignments The 21264/EV67 package has 587 pins aligned in a pin grid array (PGA) design. There are 380 functional signal pins, 1 dedicated 3.3-V pin for the PLL, 112 ground VSS pins, and 94 VDD pins. Table 3–4 lists the signal pins and their corresponding pin grid array (PGA) locations in alphabetical order for the signal type.
Pin Assignments Table 3–6 lists the 21264/EV67 ground and power (VSS and VDD, respectively) pin list. Table 3–6 Ground and Power (VSS and VDD) Pin List Signal PGA Location AA45 AG43 AR41 AW37 AW41 BA35 BA41 BC45 AB40 AH42 AK40...
Bcache port • Interrupts Chapter 3 lists and defines all 21264/EV67 hardware interface signal pins. Chapter 9 describes the 21264/EV67 hardware interface electrical requirements. 4.1 Introduction to the External Interfaces A 21264/EV67-based system can be divided into three major sections: •...
Page 90
GCLK. The period of BcDataOutClk_x[3:0] is a programmable mul- tiple of GCLK. – The Bcache turns the BcDataOutClk_x[3:0] clocks around and returns them to the 21264/EV67 as BcDataInClk_H[7:0]. Likewise, BcTagOutClk_x returns as BcTagInClk_H. – The Bcache interface supports a 64-byte block size.
The Cbox contains an 8-entry miss buffer (MAF) and an 8-entry victim buffer (VAF). A miss occurs when the 21264/EV67 probes the Bcache but does not find the addressed block. The 21264/EV67 can queue eight cache misses to the system in its MAF.
WH64 Memory WH64 Memory WH64 I/O ECB Memory ECB I/O MB/WMB TB Fill Flows Alpha 21264/EV67 Hardware Reference Manual Physical Address Considerations BcHit Status and Action Dcache hit, done. Bcache hit, done. Miss, generate RdBlk command. RdBytes, RdLWs, or RdQWs based on size.
Page 94
Note that whenever ENABLE_EVICT[0] is true (in the write-many chain), BC_CLEAN_VICTIM must also be true (in the write-once chain). Otherwise, the 21264/EV67 could respond miss to a probe, rather than hit, before an Evict command has been sent off chip, but after the Evict command has removed a (clean) block from the internal caches and the Bcache.
The 21264/EV67 Cbox provides control signals and an interface for a second-level cache (Bcache). The 21264/EV67 supports a Bcache from 1MB to 16MB, with 64-byte blocks. A 128- bit bidirectional data bus is used for transfers between the 21264/EV67 and the Bcache.
• Filtering out all probe misses from the 21264/EV67 cache system If a probe misses in the 21264/EV67 cache system (Bcache miss and VAF miss), the 21264/EV67 stalls probe processing with the expectation that a SysDc fill will allocate this block. Because of this, in duplicate tag mode, the 21264/EV67 can never generate a probe miss response.
The 21264/EV67 requires the system to allow only one change to a block at a time. This means that if the 21264/EV67 gains the bus to read or write a block, no other node on the bus should be allowed to access that block until the data has been moved.
State Name Description Clean/Shared This 21264/EV67 holds a read-only copy of the block, and at least one other agent in the sys- tem may hold a copy of the block. Upon eviction, the block is not written to memory. Dirty This 21264/EV67 holds a read-write copy of the block, and must write it to memory after it is evicted from the cache.
Rdiox commands are noncached references to I/O address space. • Evict and STCChangeToDirty commands are generated by ECB and STx_C instructions, respectively. Table 4–5 shows the system responses to 21264/EV67 commands and 21264/EV67 reactions. Table 4–5 System Responses to 21264/EV67 Commands and 21264/EV67 Reactions 21264/EV67...
Page 100
The original data in the Dcache is replaced with the filled data. The block is not writable, so the 21264/EV67 will retry the store instruc- tion and generate another ChxToDirty class command. To avoid a potential livelock situation, the STC_ENABLE CSR bit must be set.
Both commands allocate buffers in the VAF (victim address file). This buffer is a coherent part of the 21264/EV67 cache system. Write data control and deallocation of the VAF can be directly controlled by using the SysDc WriteData and ReleaseBuffer commands.
Dcache without interrupting load/store instruction processing in the processor core. 4.6 Lock Mechanism The 21264/EV67 does not contain a dedicated lock register, nor are system components required to do so. When a load-lock (LDx_L) instruction executes, data is accessed from the Dcache or Bcache.
4.6.1 In-Order Processing of LDx_L/STx_C Instructions The 21264/EV67 uses the stWait logic in the IQ to ensure that LDx_L/STx_C pairs are issued in order. The stWait logic treats an Ldx_L instruction like Stx instructions. STx_C instructions are always loaded into the IQ with their associate stWait bit set.
0 by clearing a previously set M_CTL[SMC], allowing synchronization between processors. 4.7 System Port The system port is the 21264/EV67’s connection to either a memory or I/O controller or to a shared multiprocessor system controller. System port interface signals are shown in Figure 4–4.
SysFillValid_L IRQ_H[5:0] 4.7.1 System Port Pins Table 3–1 defines the 21264/EV67 signal types referred to in this section. Table 4–6 lists the system port pin groups along with their type, number, and functional descrip- tion. Table 4–6 System Port Pins...
System Port 4.7.2 Programming the System Interface Clocks The system forwarded clocks are free running and derived from the 21264/EV67 GCLK. The period of the system forwarded clocks is controlled by three Cbox CSRs, based on the bit-rate ratio (similar to the Bcache bit-rate ratio) except that all transfers are dual-data.
This section describes the 21264/EV67-to-system commands format and operation. The command, address, ID, and mask bits are transmitted in four consecutive cycles on SysAddOut_L[14:0]. The 21264/EV67 sends the command information in one of the two following modes as selected by the Cbox CSR bit.
M1 and M2 are not asserted simultaneously. Reporting probe results as soon as possible is critical to high-speed operation, so when a result is known the 21264/EV67 uses the earli- est opportunity to send an M signal to the system. M bit assertion can occur either in a valid command or a NZNOP.
Illegal combination Page hit mode + both SysAddOut_L[1:0] are unused Function The 21264/EV67 drives this command on idle cycles during reset. After the clock forward reset period, the first NZNOP is generated and this command is no longer generated. Returns probe status and ID number of the VDB entry holding the requested cache block.
Dcache with a status of dirty/shared, clean/ shared, or clean respectively. Table 4–15 Programming INVAL_TO_DIRTY_ENABLE[1:0] INVAL_TO_DIRTY_ENABLE[1:0] Alpha 21264/EV67 Hardware Reference Manual Cbox Action WH64 instructions are converted to RdModx commands at the interface. Beyond this point, no other agent sees the WH64 instruction. This mode is useful for microprocessors that do not want to support InvalToDirty transac- tions.
LDx_L/STx_C sequence. 4.7.5 ProbeResponse Commands (Command[4:0] = 00001) The 21264/EV67 responds to system probes that did not miss with a 4-cycle transfer on SysAddOut_L[14:0]. As shown in Table 4–14, the Command[4:0] field for a ProbeRe- sponse command equals 00001.
4.7.6 SysAck and 21264/EV67-to-System Commands Flow Control Controlling the flow of 21264/EV67-to-system commands is a joint task of the 21264/ EV67 and the system. The flow is controlled using the A bit, which is asserted by the system, and the Cbox CSR SYSBUS_ACK_LIMIT[4:0] counter.
System Port • There is no mechanism for the system to reject a 21264/EV67-to-system command. ProbeResponse, VDBFlushReq, NOP, NZNOP, and RdBlkxSpec (with a clear RV bit) commands do not require a response from the system. Systems must provide adequate resources for responses to all probes sent to the 21264/EV67.
Probe type and next tag state (see Tables 4–21 and 4–22). SysDc[4:0] Controls data movement in and out of the 21264/EV67. See Table 4–24 for a list of data movement types. Clears the victim or I/O write buffer (IOWB) valid bit specified in ID[3:0].
21264/EV67 queue. The 21264/EV67 removes probes from the internal probe queue when the probe response is sent. The 21264/EV67 expects to hit in cache on a probe response, so it always fetches a cache block from the Bcache on system probes. This can become a performance prob- lem for systems that do not monitor the Bcache tags, so the 21264/EV67 provides Cbox CSR PRB_TAG_ONLY[0], which only accesses Bcache tags for system probes.
SysDc command. If the SysDc command allows the 21264/EV67 to retire an instruction before an MB, or allows the 21264/EV67 itself to retire an MB (SysDc is MBDone), that MB will not complete until the probe is exe- cuted.
(the last cycle) to the delivery of the SysDc command to the processor. 4.7.8 Data Movement In and Out of the 21264/EV67 There are two modes of operation for data movement in and out of the 21264/EV67: fast mode and fast mode disable. The data movement mode is selected using Cbox CSR FAST_MODE_DISABLE[0].
Because there is a bandwidth difference between address (4 cycles) and data (8 cycles) transfers, the 21264/EV67 tries to fully use fast data mode by delaying the next SysAddOut write command until a fast data mode slot is available on the SysDataOut bus.
2. The 21264/EV67 drivers stay off until the last piece of fill data is received, or a new SysDc write command overrides the current SysDc fill command. It is the responsi- bility of the external system to schedule SysDc fill or write commands so that there is no conflict on the SysData bus.
21264/EV67 is preceded by a SysDc command. The 21264/EV67 drivers are only enabled for the duration of an 8-cycle transfer of data from the 21264/ EV67 to the system. Systems must ensure that there is no overlap of enabled drivers and that there is adequate settle time on the SysData bus.
BPHASE, before the start of a write transfer, and disabled on the succeeding GCLK BPHASE at the end of the write transfer. The write data is enveloped by the 21264/ EV67 drivers to guarantee that every data transfer has the same data valid window.
21264/EV67. The system designer may tie this pin to the asserted state (validating all fills), or use it to enable or cancel fills as they progress. The 21264/EV67 samples SysFillValid_L at D1 time (when the 21264/EV67 samples the second data cycle).
SysAddOut_L[5:3] STByte/Word The order in which data is provided to the 21264/EV67 (for a memory or I/O fill) or moved from the 21264/EV67 (write victims or probe reads) can be determined by the system. The system chooses to reflect back the same low-order address bits and the cor- responding octaword found in the SysAddOut field or the system chooses any other starting point within the block.
QW pointed to by the 21264/EV67; however, some systems may find it more beneficial to begin the transfer elsewhere. The system must always indicate the starting point to the 21264/EV67. The wrap order for subsequent QWs is interleaved.
I/O space. However, unlike the earlier Alpha microprocessor implementa- tions, the 21264/EV67 can generate speculative references to memory space. To accom- modate the speculative nature of the 21264/EV67, the system must not generate or lock error registers because of speculative references. The 21264/EV67 translates all mem-...
21264/EV67 Command NXM Address System/21264/EV67 Response CleanToDirty ChangeToDirty commands to NXM space are impossible in the 21264/EV67 because all SharedToDirty NXM references to memory space are atomically filled with an Invalid cache status. STCChangeToDirty InvalToDirty InvalToDirty commands are not speculative, so InvalToDirty commands to NXM space InvalToDirtyVic indicate an operating system error.
This case assumes that a SetDirty command has been sent to the system environment SharedToDirty because of a store instruction that hit in the 21264/EV67 caches and that another processor has performed a load/store instruction to the same address. The 21264/EV67 provides MAF hit information so that the system can correctly respond to the Set/Dirty command.
Bcache size can be 1MB, 2MB, 4MB, 8MB, or 16MB. The Bcache port has a 144-bit data bus that is used for data transfers between the 21264/EV67 and the Bcache. All Bcache control and address signal lines are clocked synchronously on Bcache clock cycle boundaries.
The Bcache supports the following multiples of the GCLK period: 1.5X (dual-data mode only), 2X, 2.5X, 3X, 3.5X, 4X, 5X, 6X, 7X, and 8X. However, the 21264/EV67 imposes a maximum Bcache clock period based on the SYSCLK ratio. Table 4–35 lists the range of maximum Bcache clock periods.
Int_Data_BcClk output Bcache tag parity bit BcTagInClk_H input Int_Data_BcClk output Bcache tag shared bit BcTagInClk_H input Int_Data_BcClk output Bcache tag valid bit BcTagInClk_H input Input reference voltage for tag data Int_Index_BcClk Bcache data write enable Alpha 21264/EV67 Hardware Reference Manual...
Table 4–37 BC_CPU_CLK_DELAY[1:0] Values BC_CPU_CLK_DELAY[1:0] Value In the 21264/EV67 topology, the index pins are loaded by all the SSRAMs, while the clock and data pins see a limit load. This arrangement requires a relatively large amount of delay between the index pins and the Bcache clock pins to meet the setup constraints at the SSRAMs.
With the exception of the 2.5X-SD and 3.5X-SD cases, the clock waveform generated by the 21264/EV67 for the forwarded clocks has a 50-50 duty cycle. In the 2.5X-SD case, the 21264/EV67 produces an asymmetric clock that is high for two GCLK phases and low for three phases.
The following three sections describe these Bcache transactions. 4.8.3.1 Bcache Data Read and Tag Read Transactions The 21264/EV67 always reads four pieces of data (64 bytes) from the Bcache during a data read transaction, and always interrogates the tag array on the first cycle. Once started, data read transactions are never cancelled.
SSRAM setup/hold Bcache address latch requirements, a Bcache read command proceeds through the 21264/EV67 Cbox as follows: 1. When the 21264/EV67 clocks out the first address value on the Bcache index pins with the appropriate Int_Add_BcClk value, the Cbox loads the values of Cbox CSR...
3. The difference between the data delivery (Int_Data_BcClk) and forwarded clocks out provides the setup for the data at the Bcache data flip-flop. 4. For Bcache writes, the 21264/EV67 drivers are enabled on the GCLK BPHASE preceding the start of a write transfer, and disabled on the succeeding GCLK BPHASE at the end of a write transfer.
Page 138
The minimum spacing required between the read and write indices at the data/tag pins, expressed as GCLK cycles. wr_rd The minimum spacing required between the write and read indices at the data/tag pins, expressed as GCLK cycles. Cache and External Interfaces 4–50 Alpha 21264/EV67 Hardware Reference Manual...
4.8.4.1 BcAdd_H[23:4] The BcAdd_H[23:4] pins are high drive outputs that provides the index for the Bcache. The 21264/EV67 supports Bcache sizes of 1MB, 2MB, 4MB, 8MB, and 16MB. Table 4–42 lists the values to be programmed into Cbox CSRs BC_ENABLE[0] and BC_SIZE[3:0] to support each size of the Bcache.
Bcache Port When the Cbox CSR BC_BANK_ENABLE[0] is not set, the unused BcAdd_H[23:4] pins are tied to zero. For example, when configured as a 4MB cache, the 21264/EV67 never changes BcAdd_H[23:22] from logic zero, and when BC_BANK_ENABLE[0] is asserted, the 21264/EV67 drives the complement of the MSB index on the next higher BcAdd_H pin.
Bcache banking is possible by decoding the index MSB (as determined by Cbox CSR BC_SIZE[3:0]) and asserting Cbox CSR BC_BANK_ENABLE[0]. To facilitate bank- ing, the 21264/EV67 provides the complement of the MSB bit in the next higher unused index bit. For example, when configured as an 8MB cache with banking enabled, the 21264/EV67 drives the inversion of PA[22] on BcAdd_H[23] for use as a chip enable in a banked configuration.
This chapter describes 21264/EV67 internal processor registers (IPRs). They are sepa- rated into the following circuit logic groups: Ebox, Ibox, Mbox, and Cbox. The gray areas in register figures indicate reserved fields. Bit ranges that are coupled with the field name specify those bits in that named field that are included in the IPR.
CC register may be written and its associated counter enabled and dis- abled. Figure 5–2 shows the cycle counter control register. Figure 5–2 Cycle Counter Control Register CC_ENA COUNTER[31:4] Alpha 21264/EV67 Hardware Reference Manual Score- Index Board (Binary)
When set, this bit allows the cycle counter to increment. CC[31:4] may be written by way of this field. Write transactions to CC_CTL result in CC[3:0] being cleared. — — Alpha 21264/EV67 Hardware Reference Manual LK99-0010A 3 2 1 LK99-0014A...
ITB_TAG and ITB_PTE registers are written into the ITB entry. The specific ITB entry that is written is determined by a round-robin algorithm; the algorithm writes to entry number 0 as the first entry after the 21264/EV67 is reset. Figure 5–8 shows the ITB tag array write register.
Because the Icache is virtually indexed and tagged, it is normally not nec- essary to flush the Icache when paging. Therefore, a write to ITB_IS will not flush the Icache. Alpha 21264/EV67 Hardware Reference Manual Ibox IPRs 12 11 10...
Figure 5–12 Exception Address Register PC[63:2] Internal Processor Registers 5–8 Type Description Address of the profiled instruction Read as zero Indicates that the PC field contains a physical-mode PALmode address Alpha 21264/EV67 Hardware Reference Manual 2 1 0 LK99-0018A 2 1 0 LK99-0018A...
IER field and bit[0] corresponds to the processor mode field. A HW_MFPR instruction to this register returns the values in both fields. Figure 5–16 shows the interrupt enable and current processor mode register. Alpha 21264/EV67 Hardware Reference Manual 38 37 Internal Processor Registers...
Performance Counter Interrupt Enables Software Interrupt Enables AST Interrupt Enable When set, enables those AST interrupt requests that are also enabled by the value in ASTER. — — Current Mode Kernel Executive Supervisor User — — Alpha 21264/EV67 Hardware Reference Manual LK99-0022A...
ASTRR bits and whether the processor mode value held in the IER_CM register is greater than or equal to the value for the mode. — — 33 32 31 30 29 28 27 26 25 Alpha 21264/EV67 Hardware Reference Manual LK99-0025A...
Dstream exceptions: The REG field contains the register number of either the source specifier (for stores) or the destination specifier (for loads) of the instruction that triggered the trap. Figure 5–20 shows the exception summary register. Alpha 21264/EV67 Hardware Reference Manual Type Description —...
I-stream virtual address is latched in the EXC_ADDR register or the VA register. If BAD_IVA is clear, EXC_ADDR contains the address; if BAD_IVA is set, VA con- tains the address. Alpha 21264/EV67 Hardware Reference Manual LK99-0026A...
The Ibox control register (I_CTL) is a read-write register that controls various Ibox functions. Its contents are cleared by chip reset. Figure 5–22 shows the Ibox control register. Alpha 21264/EV67 Hardware Reference Manual Type Description Destination register of load or operate instruction that triggered the trap OR source register of store that triggered the trap.
Virtual Page Table Base. See Section 5.1.5 for details. This is a read-only field that supplies the revision ID number for the 21264/EV67 part. 21264/EV67 pass 2.2.2 ID is 001110 21264/EV67 pass 2.2.3 ID is 001111 21264/EV67 pass 2.4 ID is 001100 21264/EV67 pass 2.5 ID is 000111...
Page 159
SL_RCV [14] SL_XMIT [13] [12] BP_MODE[1:0] [11:10] Alpha 21264/EV67 Hardware Reference Manual Type Description RW,0 Machine check enable — set to enable machine checks. RW,0 The stWait table is used to reduce load/store order traps. When set, the stWait table is cleared after 64K cycles. When clear, the stWait table is cleared after 16K cycles.
PALshadow Register Enable. Enables access to the PALshadow registers. If SDE[1] is set, R4-R7 and R20-R23 are used as PALshadow registers. SDE[0] does not affect 21264/EV67 operation. RW,0 Super Page Mode Enable. Identical to the SPE bits in the Mbox M_CTL SPE[2:0]. See Section 5.3.9.
Extent Type Reserved [63:41] [40] [39] [38] Alpha 21264/EV67 Hardware Reference Manual 41 40 34 33 32 Description Reserved for Compaq. ProfileMe Mispredict Trap. If the I_STAT[TRP] bit is set, this bit indicates that the profiled instruc- tion caused a mispredict trap. JSR/JMP/RET/COR or HW_JSR/...
Page 162
This bit indicates that the Icache encountered a parity error on instruction fetch. When a parity error is detected, the Icache is flushed, a replay trap back to the address of the error instruction is generated, and a correctable read interrupt is requested. Reserved for Compaq. Alpha 21264/EV67 Hardware Reference Manual...
IPR Index Bit A HW_MFPR from this register returns the values in all of its component bit fields. Figure 5–24 shows the process context register. Alpha 21264/EV67 Hardware Reference Manual , this register is selected. Bits [4:0] of the Register Field...
Kernel Mode AST enable register—used to individually enable each of the four AST interrupt requests. The bit order with this field is: User Mode Supervisor Mode Executive Mode Kernel Mode — — Alpha 21264/EV67 Hardware Reference Manual 2 1 0 LK99-0032A...
Figure 5–25 Performance Counter Control Register SEXT(PCTR0_CTL[47]) PCTR0[19:0] PM_STALLED PM_KILLED_BM PCTR1[19:0] SL1[1:0] Alpha 21264/EV67 Hardware Reference Manual Type Description RW,1 Floating-point enable—if clear, floating-point instructions generate FEN exceptions. This bit is set by hardware on reset. Process performance counting enable.
Reads to this field return zero. Writes to this field are ignored. Selector 0. 0 = Aggregate counting mode 1 = ProfileMe mode See Table 5–16 for more information. Selector 1. Selects counter PCTR0 and PCTR1 modes. See Table 5–16 for more information. Alpha 21264/EV67 Hardware Reference Manual...
Figure 5–26 shows the DTB tag array write registers 0 and 1. Figure 5–26 DTB Tag Array Write Registers 0 and 1 48 47 VA[47:13] Alpha 21264/EV67 Hardware Reference Manual Profiled instruction valid. When set, indicates a nontrapping profiled instruction retired valid. When clear, indicates that a nontrapping profiled instruction was killed after the cycle in which it was mapped.
The DTB entry’s virtual page number matches DTB_IS[47:13] and its ASM bit is set. Figure 5–29 shows the Dstream translation buffer invalidate single registers. Figure 5–29 Dstream Translation Buffer Invalidate Single Registers 48 47 VA[47:13] Alpha 21264/EV67 Hardware Reference Manual Type Description — — Alt_Mode:...
Opcode of the instruction that caused the error. HW_LD is displayed as 3 and HW_ST is displayed as 7. This bit is set when a fault-on-write error occurs during a write transaction and PTE[FOW] was set. Alpha 21264/EV67 Hardware Reference Manual LK99-0038A 4 3 2 LK99-0039A...
Figure 5–32 shows the Mbox control register. Figure 5–32 Mbox Control Register SMC[1:0] SPE[2:0] Alpha 21264/EV67 Hardware Reference Manual Type Description This bit is set when a fault-on-read error occurs during a read transaction and PTE[FOR] was set.
(see Section 2.6.2) to behave like normal prefetches. Place 21264/EV67 in periodic conservative mode by using an 8-bit counter to add by 4 each time a branch mispredict happens and sub- tract by one each time a conditional branch retires. Enter conserva- tive mode if the MSB of the counter is set.
The Dcache status register (DC_STAT) is a read-write register. If a Dcache tag parity error or data ECC error occurs, information about the error is latched in this register. Figure 5–34 shows the Dcache status register. Alpha 21264/EV67 Hardware Reference Manual Type Description —...
The Cbox configuration registers are split into three shift register chains: • The hardware allocates 367 bits for the WRITE_ONCE chain, of which the 21264/ EV67 uses 304 bits. During hardware reset (after BiST), 367 bits are always shifted into the WRITE_ONCE chain from the SROM, MSB first, so that the unused bits are shifted out the end of the WRITE_ONCE chain.
Many CSRs are duplicated for ease of hardware implementation. These CSRs are indicated in italics. They must be written with values that are identical to the values written to the original CSRs. Alpha 21264/EV67 Hardware Reference Manual Description — Cbox data register. A HW_MTPR instruction to this register causes six bits of data to be placed into a serial shift register.
2.0X 0100 2.5X 1000 3.0X Enable duplicate tag mode in the 21264/EV67. Enable probe-tag only mode in the 21264/EV67. When asserted, disables fast data movement mode. Enables RdVictim mode on the pins. Duplicate CSR. Enable inhibition of incrementing acknowledge counter for RdVic commands.
Page 177
Asserted when (BC_LATE_WRITE_NUM > 3) or ((BC_LATE_WRITE_NUM = 3) and (BC_CPU_LATE_WRITE_NUM > 1)). Enables the update of the 21264/EV67 Bcache tag outputs based on the falling edge of the forwarded clock. Internal Processor Registers Cbox CSRs and IPRs 5–35...
Page 178
Internal Processor Registers 5–36 Description Enables the update of the 21264/EV67 Bcache tag outputs based on the rising edge of the forwarded clock. Enable clock forwarding on the Bcache interface. Initial value for the Bcache clock forwarding unload pointer FIFO.
CSR to program the system forwarded clock shift register load val- ues. CSR to program the system forwarded clock b-phase enables. CSR to program the ratio between frame clock and system for- warded clock. Fifth SYSDC_DELAY bit. Alpha 21264/EV67 Hardware Reference Manual...
DSTREAM_DC_ERR, only bits 6:19 are valid. If C_STAT value is DOUBLE_BIT_ERROR and SKEWED_FILL_MODE[0] is set, then C_ADDR is X. Alpha 21264/EV67 Hardware Reference Manual Error Status Either no error, or error on a speculative load, or a Bcache vic- tim read due to a Dcache/Bcache miss...
There are a few extra instructions that are only available in PALmode, and will cause a dispatch to the OPCDEC PALcode entry point if attempted while not in PALmode. The Alpha architecture allows some flexibility in what these special PALmode instructions do. In the 21264/EV67, the special PALmode-only instructions perform the following func- tions: •...
When executing in PALmode, there are certain restrictions for using the privileged instructions because PALmode gives the programmer complete access to many of the internal details of the 21264/EV67. Refer to Section 6.4 for information on these spe- cial PALmode instructions.
JSR_COROUTINE, the stack can be managed by setting the HINT bits accordingly. See Section D.25 for more information about the HW_RET instruction. Figure 6–3 shows the HW_RET instruction format. Alpha 21264/EV67 Hardware Reference Manual Opcodes Reserved for PALcode Description The opcode value.
Stall until the HW_RET instruction is retired or aborted If instructions beyond the HW_RET have been issued out of order, they will be killed and refetched. Holds a 13-bit signed longword displacement. 16 15 INDEX SCBD_MASK FM-05657.AI4 Alpha 21264/EV67 Hardware Reference Manual DISP FM-05656.AI4...
Implicit writers are instructions that may write a value into the IPR as a side effect of execution. For example, a load instruction that generates an access violation is an implicit writer of the VA, MM_STAT, and EXC_ADDR IPRs. In the 21264/ EV67, only instructions that generate an exception will act as implicit IPR writers.
Software was required to schedule HW_MTPR and HW_MFPR instructions for each machine’s pipeline organization in order to ensure correct behavior. This software scheduling task is more difficult in the 21264/EV67 because the Ibox performs dynamic scheduling. Hence, eight extra scoreboard bits are used within the IQ to help maintain correct IPR access order.
PALcode routine reordered. invoked by the exception associated with the writer, then ordering is guaran- teed. Alpha 21264/EV67 Hardware Reference Manual Internal Processor Register Access Mechanisms First Instruction Explicit Reader Explicit Writer A variety of mechanisms are be reordered. used to ensure order: scoreboard bits to stall issue of reader;...
See Appendix D for a listing of cases where this method is recommended. Privileged Architecture Library Code 6–10 First Instruction Reader reads second Scoreboard bits stall second register. Writer cannot writer in map stage until first write second register writer is retired. until it is retired. Alpha 21264/EV67 Hardware Reference Manual...
HW_MFPR and the LD. 6.6 PALshadow Registers The 21264/EV67 contains eight extra virtual integer registers, called shadow registers, which are available to PALcode for use as scratch space and storage for commonly used values. These registers are made available under the control of the SDE[1] field of the I_CTL IPR.
6.7.1 Status Flags The FPCR status bits in the 21264/EV67 are set with PALcode assistance. Floating- point exceptions, for which the associated FPCR status bit is clear or for which the associated trap is enabled, result in a hardware trap to the ARITH PALcode routine. The EXC_SUM register contains information to allow this routine to update the FPCR appropriately, and to decide whether to report the exception to the operating system.
DTBM_SINGLE Fault DFAULT Fault OPCDEC Fault IACV Fault Alpha 21264/EV67 Hardware Reference Manual to 7F inclusive and 3F inclusive, and IER_CM[CM] is not equal to the kernel Offset Description Dstream TB miss on virtual page table entry fetch. Use three- level flow.
Interrupt 6.9 Translation Buffer (TB) Fill Flows This section shows the expected PALcode flows for DTB miss and ITB miss. Familiar- ity with 21264/EV67 IPRs is assumed. 6.9.1 DTB Fill Figure 6–5 shows single-miss DTB instructions flow. Figure 6–5 Single-Miss DTB Instructions Flow Example Figure 6–5 shows single-miss DTB instructions flow.
Page 199
PTE from (I) it will see the new data. Processor I Wr Data Wr PTE Alpha 21264/EV67 Hardware Reference Manual Translation Buffer (TB) Fill Flows ; (0,4,2,6) (0L) write pte0 ; (3,7,1,5) (1L) write pte1 ;...
This behavior is functionally correct because DTB loads that tag-match an existing DTB entry are ignored by the 21264/EV67 and the second DTB miss execution will load exactly the same entry as the first. 6.9.2 ITB Fill Figure 6–6 shows the ITB miss instructions flow.
6.10 Performance Counter Support The 21264/EV67 provides hardware support for two methods of obtaining program performance feedback information. The two methods do not require program modifica- tion. Instead, performance monitoring utilities make calls to the PALcode to set up the counters and contain interrupt handlers that call PALcode to retrieve the collected data.
The handler may also choose to write the counters to control the frequency of inter- rupts. Table 6–10 Aggregate Mode Returned IPR Contents PCTR_CTL Alpha 21264/EV67 Hardware Reference Manual Performance Counter Support Field Contents PCTR0[19:0]...
I_CTL[PCT0_EN] and either I_CTL[SPCE] or PCTX[PPCE]. On overflow, an inter- rupt is triggered as ISUM[PC0] if enabled via IER_CM[PCEN0]. The 21264/EV67 can retire up to 11 instructions per cycle, which exceeds PCTR0’s maximum increment of 8 per cycle. However, no retires go uncounted because the 21264/EV67 cannot sustain 11 retires per cycle, and the 21264/EV67 corrects PCTR0 in subsequent cycles.
SL0 & SL1. 4. End window The last cycle of the window depends on whether the instruction traps, retires, aborts, and/or is squashed by the fetcher. Alpha 21264/EV67 Hardware Reference Manual Performance Counter Support New Instructions CMOV1 Ra, oldRc CMOV2 newRc1, Rb...
Branch direction if instruction is a conditional branch. Instruction stalled for at least one cycle between fetch and map stages of pipeline. Instruction killed during or before cycle in which it was mapped. Counter 0 value. Counter 1 value. Alpha 21264/EV67 Hardware Reference Manual...
Counts cycles that a profiled instruction delayed the retire pointer advance during the ProfileMe window. The 21264/EV67 tracks instructions in the pipeline by allocating them "inums" near the front of the pipeline. All inums are retired in the order in which they were allocated at the end of the pipeline.
GCLK frequency during sleep mode. 7.1 Power-Up Reset Flow and the Reset_L and DCOK_H Pins The 21264/EV67 reset sequence is triggered using the two input signals Reset_L and DCOK_H in a sequence that is described in Section 7.1.1. After Reset_L is deasserted,...
Enough time for Reset_L to propagate through 5 stages of RESET synchronizer (clocked by the inter- nal framing clock, which is driven by EV6Clk_x). Worst case through Pass 3 of the 21264/EV67 would be 5x8x8 = 320 GCLK cycles, because Y Min = 1 FrameClk cycle.
Prior to DCOK_H being asserted, the logic internal to the 21264/EV67 is being reset and the internal clock network is running (either clocked by the PLL VCO, which is at a nomi- nal speed, or by ClkIn_H, if the PLL is bypassed).
IRQ_H pins. The IRQ_H pins are sampled on the rising edge of DCOK_H, during which time the 21264/EV67 is in reset and is not generating any sys- tem activity. During normal operation, the IRQ_H pins supply interrupt requests to the 21264/EV67.
PLL ramp up sequence. Ramping up of the PLL is required to guarantee that the dynamic change in frequency will not cause the supply on the 21264/ EV67 to fall due to the supply loop inductance. Clock control circuitry steps GCLK from power-up/reset clocking to 1/16 and finally normal operating frequency.
As BiST completes, the TestStat_H pin is held low for 16 GCLK cycles. Then, if BiST succeeds, the pin remains low. Otherwise, it is asserted. After successfully completing BiST, the 21264/EV67 then performs the SROM load sequence (described in Chapter 11). After the SROM load sequence is finished, the 21264/EV67 deasserts SromOE_L.
RUN state. ClkFwdRst_H is asserted by the system, which causes the state machine to transition to the WAIT_FAULT_RESET state. The 21264/EV67 internally resets a minimum amount of internal state. Note the effects of that reset on the IPRs in Table 7–5 Table 7–5 Effect on IPRs After Fault Reset...
Clks 7.3 Energy Star Certification and Sleep Mode Flow The 21264/EV67 is Energy Star compliant. Energy Star is a program administered by the Environmental Protection Agency to reduce energy consumption. For compliance, a computer must automatically enter a low power sleep mode using 30 watts or less after a specified period of inactivity.
WRITE_MANY Cleared (That is, the WRITE_MANY chain is initialized and the Bcache is Note that Interrupt enables are maintained during sleep mode, enabling the 21264/ EV67 to wake up. The 21264/EV67 waits for either an unmasked clock interrupt or an unmasked device interrupt from the system.
The warm reset sequence of operation is triggered by the assertion of the Reset_L sig- nal line. The reset state machine is initially in RUN state. The 21264/EV67 then, by default, ramps down the PLL (similar to the sleep flow sequence) and the reset state machine ends up in the WAIT_RESET state.
Array Initialization The 21264/EV67 waits until Reset_L is deasserted before transitioning from the WAIT_RESET state. The 21264/EV67 ramps up the PLL until the state machine enters the WAIT_ClkFwdRst0 state. Note that the system must assert ClkFwdRst_H before the state machine enters the WAIT_ClkFwdRst0 state. Then, similarly to the other flows, SromOE_L is asserted and the system waits for the deassertion of ClkFwdRst_H.
WrVictimBlk command generation to the system interface are squashed. Using the INVAL_TO_DIRTY_ENABLE and INIT_MODE registers, initialization code loaded from the SROM can generate and delete blocks inside the 21264/EV67 without system interaction. This behavior is very useful for initialization and startup processing, when the system interfaces are not fully functional.
;bc_bank_enable_a ;This loop generates legal ECC data, and ;invalidate tags which are written to the ;Bcache for all but the final 64KB of address. ;and cleans up the Dcache also. Reset State Comments — — Alpha 21264/EV67 Hardware Reference Manual...
Page 223
DTB alternate processor mode DTB_IAP DTB invalidate all process ASM = 0 DTB_IA DTB invalidate all process Alpha 21264/EV67 Hardware Reference Manual Internal Processor Register Power-Up Reset State Reset State Comments — Must be written to in PALcode. — —...
Cbox shift control 7.9 IEEE 1149.1 Test Port Reset Signal Trst_L must be asserted when powering up the 21264/EV67. Trst_L must not be deasserted prior to assertion of DCOK_H. Trst_L can remain asserted during nor- mal operation of the 21264/EV67.
Page 226
PAL_BASE + 0x780. DOWN1 21264/EV67 was in a state in which GCLK was at its highest speed and Reset_L was asserted. Internal chip functions are reset and the internal duration counter is set to 8205 cycles. The purpose of this sequence is to down-ramp the clocks in anticipation of power being removed.
The PLL multiplies the clock frequency of a differential input reference clock and aligns the phase of its output to that differential input clock. Thus, the 21264/EV67 can communicate synchronously on clock boundaries with clock periods that are defined by the system.
769.2 833.3 Dividers 11 through 16 are out of range for the 21264/EV67 and reserved for future use. Valid refer- ence clock (ClkIn_x) frequencies for the 21264/EV67 are specified in the range from 80 to 200. Divider values that are out of that range are displayed as a dash “—”.
Error Detection and Error Handling This chapter gives an overview of the 21264/EV67 error detection and error handling mechanisms, and is organized as follows: • Data error correction code • Icache data or tag parity error • Dcache tag parity error •...
Data Error Correction Code 8.1 Data Error Correction Code The 21264/EV67 supports a quadword error correction code (ECC) for the system data bus. ECC is generated by the 21264/EV67 for all memory write transactions (WrVictimBlk) emitted from the 21264/EV67 and for all probe data. ECC is also checked on every memory read transaction for single-bit correction and double-bit error detection.
Cbox scrubs the block in the Dcache by evicting the block into the victim buffer (thereby scrubbing it) and writing it back into the Dcache as follows: – C_STAT[DSTREAM_DC_ERR] is set. Alpha 21264/EV67 Hardware Reference Manual Dcache Data Single-Bit Correctable ECC Error Error Detection and Error Handling 8–3...
The Dcache duplicate tag has the correct version of the Dcache coherence state for the 21264/EV67, allowing it to be used for correct tag/status data when the Dcache tags generate a parity error. These tags are parity protected also; however, the Dcache dupli- cate tag cell is designed to be much more tolerant of soft errors.
MCHK is removed. The CRD PALcode reads the status, to detect this condition, and scrubs the block. In the normal MCHK flow, the PALcode clears the pending CRD error. Alpha 21264/EV67 Hardware Reference Manual Bcache Tag Parity Error Error Detection and Error Handling...
The Ibox will invoke a replay trap at an instruction that is older than (or equal to) any instruction that consumes the load instruction’s data. The 21264/ EV67 then stalls the replayed Istream in the map stage of the pipeline, until the error is corrected.
If the error is not corrected by PAL- code at the time, the error will be detected and corrected by a load/victim operation. Alpha 21264/EV67 Hardware Reference Manual Error Detection and Error Handling...
A CRD error interrupt is posted, when enabled. • The PALcode on the probed processor may choose to scrub the error, though it will probably be scrubbed by the requesting processor. Error Detection and Error Handling 8–8 Alpha 21264/EV67 Hardware Reference Manual...
8.11 Double-Bit Fill Errors Double-bit errors for fills are detected, but not corrected, in the 21264/EV67. The fol- lowing events may cause a double-bit fill error: • Icache fill from Bcache • Dcache fill from Bcache • Icache fill from memory •...
Section D.36. Log as CRD Corrected and Scrub error as described scrubbed in in Section D.36. Dcache Log as CRD None May scrub error as described in Section D.36. Log as CRD None Log as MCHK Alpha 21264/EV67 Hardware Reference Manual...
Page 239
For a single-bit error on a non-target quadword, the error is not corrected in hardware, but is corrected by PALcode during the scrub operation. The contents of C_ADDR may not be accurate when there is heavy cache fill traffic. Alpha 21264/EV67 Hardware Reference Manual Error Case Summary Hardware...
This chapter describes the electrical characteristics of the 21264/EV67 and its interface pins. The chapter contains both ac and dc electrical characteristics and power supply considerations, and is organized as follows: • Electrical characteristics • DC characteristics • Power supply sequencing •...
The test load must be mal operation, these inputs are coupled with a 680-pF capacitor. 3. Functional operation of the 21264/EV67 with less than all VDD and VSS pins con- nected is not implied.
Current out of a 21264/EV67 pin is represented by a – symbol while a + Note: symbol indicates current flowing into a 21264/EV67 pin. Table 9–3 VDD (I_DC_POWER) Parameter Symbol Description Processor core supply voltage Power (sleep) Processor power required (sleep)
Before the power-on sequencing can occur, systems should ensure that DCOK_H is deasserted and Reset_L is asserted. Then, systems ramp power to the 21264/EV67 PLL_VDD @ 3.3 V and the 21264/EV67 power planes (VDD @ 2.0 V, not to exceed 2.15 V under any circumstances), with PLL_VDD leading VDD. Systems should supply differential clocks to the 21264/EV67 on ClkIn_H and ClkIn_L.
To avoid failure mechanism number two, systems must sequence and control external signal flow in such a way as to avoid zero differential into the 21264/EV67 input receivers (I_DA, I_DA_CLK, B_DA_OD, B_DA_PP, and B_DA_PP). Finally, to avoid failure mechanism number three, systems must sequence input and bidirectional pins (I_DA, I_DA_CLK, B_DA_OD, B_DA_PP, and I_DC_REF) such that the 21264/ EV67 does not see a voltage above its VDD.
Page 249
The TSU and TDH of FrameClk_x are referenced to the deasserting edge of ClkIn_x. This signal is a feedback to the internal PLL and may be monitored for overall 21264/EV67 jitter. It can also be used as a feedback signal to an external PLL when in PLL bypass mode. Proper termina- tion of EV6Clk_x is imperative.
• Thermal design considerations 10.1 Operating Temperature The 21264/EV67 is specified to operate when the temperature at the center of the heat sink (T is as shown in Table 10–1. Temperature T the heat sink, between the two package studs. The GRAFOIL pad is the interface mate- rial between the package and the heat sink.
Page 252
( C/W) Heat sink type 3 has a 80 mm 80 mm Table 10–3 Maximum T for 21264/EV67 @ 600 MHz and @ 2.0 V with Various Airflows Airflow (linear ft/min) Maximum T with heat sink type 1 ( C)
Table 10–7 Maximum T for 21264/EV67 @ 750 MHz and @ 2.0 V with Various Airflows Airflow (linear ft/min) Maximum T with heat sink type 1 ( C) Maximum T with heat sink type 2 ( C) Maximum T with heat sink type 3 Heat sink type 3 has a 80 mm 80 mm Table 10–8 Maximum T...
Figure 10–2 shows the heat sink type 2, along with its approximate dimensions. Figure 10–2 Type 2 Heat Sink 81.0 mm (3.19 in) 81.0 mm 25.4 mm (3.19 in) (1.0 in) 44.5 mm (1.75) FM-06120.AI4 Alpha 21264/EV67 Hardware Reference Manual Thermal Management 10–5...
10.3 Thermal Design Considerations Follow these guidelines for printed circuit board (PCB) component placement: • Orient the 21264/EV67 on the PCB with the heat sink fins aligned with the airflow direction. • Avoid preheating ambient air. Place the 21264/EV67 on the PCB so that inlet air is not preheated by any other PCB components.
Power-up self-test and initialization • Notes on IEEE 1149.1 operation and compliance The 21264/EV67 has several manufacturing test features that are used only by the fac- tory, and they are beyond the scope of this chapter. 11.1 Test Pins The 21264/EV67 test access ports include the IEEE 1149.1 test access port, a dual-pur- pose SROM/Serial diagnostic terminal port, and a test status output pin.
The SromOE_L pin supplies the output enable as well as the reset to the serial ROM. (Refer to the serial ROM specifications for details.) The 21264/EV67 asserts this signal low for the duration of the Icache load from the serial ROM. When the load has been completed, the signal remains deasserted.
Tdi_H, Tms_H, and Trst_L pins, as required by the present standard. The scope of 1149.1 compliant features on the 21264/EV67 is limited to the board level assembly verification test. The systems that do not intend to drive this port must termi- nate the port pins as follows: pull-ups on Tdi_H and Tms_H, pull-downs on Tck_H and Trst_L.
Note: of the SromClk_H pin to determine BiST results. After the power-up dur- ing the normal chip operation, whenever the 21264/EV67 does not retire an instruction for 2K CPU cycles, the pin is asserted high for 3 CPU cycles. Testability and Diagnostics 11–4...
11.5.2 SROM Initialization Power-up initialization on the 21264/EV67 is different from previous generation Alpha systems in two aspects. First, in the 21264/EV67 systems, the presence of serial ROMs is mandatory as initialization of several Cbox configuration registers depends on them. Second, it is possible to skip or partially fill Icache from serial ROMs. Figure 11–...
Data(0,n) plus MBZ(m,0) must equal 367 bits. (If Cbox Config Data(0,n) is (0,366), MBZ would be zero.) For the 21264/EV67, Cbox Config Data is 304 bits; the value for n is 303. Therefore, the value MBZ field for Pass 3 is: MBZ(m,0) = 367 minus 304 = 63 = (62,0) Tables 11–3 and 5–24 describe the details of the Icache and Cbox bit fields, respec-...
Icache load. 11.6 Notes on IEEE 1149.1 Operation and Compliance 1. IEEE 1149.1 port pins on the 21264/EV67 are not pulled up or pulled down on the chip. The necessary pull-up or pull-down function must be implemented on the board.
This appendix provides a summary of the Alpha instruction set and describes the 21264/EV67 IEEE floating-point conformance. It is organized as follows: • Alpha instruction summary • Reserved opcodes • IEEE floating-point instructions • VAX floating-point instructions • Independent floating-point instructions •...
Branch if zero Branch if > zero 11.08 Bit clear 11.20 Logical sum Branch if low bit clear Branch if low bit set Branch if zero Branch if < zero Branch if zero Unconditional branch Alpha 21264/EV67 Hardware Reference Manual...
Page 269
CMPTLT CMPTUN CMPULE CMPULT CPYS CPYSE CPYSN CTLZ CTPOP CTTZ CVTDG CVTGD CVTGF Alpha 21264/EV67 Hardware Reference Manual Alpha Instruction Summary Opcode Description Branch to subroutine Trap to PALcode 11.24 CMOVE if zero 11.46 CMOVE if zero 11.66 CMOVE if > zero 11.16...
Page 270
Extract word low Floating branch if zero Floating branch if zero Floating branch if > zero Floating branch if zero Floating branch if < zero Floating branch if zero 17.02A FCMOVE if zero 17.02D FCMOVE if zero Alpha 21264/EV67 Hardware Reference Manual...
Page 271
INSQL INSWH INSWL ITOFF ITOFS ITOFT JSR_COROUTINE Mbr LDAH LDBU LDL_L LDQ_L LDQ_U Alpha 21264/EV67 Hardware Reference Manual Alpha Instruction Summary Opcode Description 17.02F FCMOVE if > zero 17.02E FCMOVE if zero 17.02C FCMOVE if < zero 17.02B FCMOVE if zero 18.8000 Prefetch data...
Page 272
Multiply longword with integer overflow enable 13.20 Multiply quadword 13.60 Multiply quadword with integer overflow enable 16.082 Multiply S_floating 16.0A2 Multiply T_floating 11.28 Logical sum with complement 1C.31 Pixel error 1C.37 Pack longwords to bytes Alpha 21264/EV67 Hardware Reference Manual...
Page 273
S8SUBQ SEXTB SEXTW SQRTF SQRTG SQRTS SQRTT STL_C STQ_C STQ_U Alpha 21264/EV67 Hardware Reference Manual Alpha Instruction Summary Opcode Description 1C.36 Pack words to bytes 18.E000 Read and clear 1A.2 Return from subroutine 18.C000 Read process cycle counter 18.F000 Read and set 10.02...
ZAPNOT A.2 Reserved Opcodes This section describes the opcodes that are reserved in the Alpha architecture. They can be reserved for Compaq or for PALcode. A.2.1 Opcodes Reserved for Compaq Table A–3 lists opcodes reserved for Compaq. Table A–3 Opcodes Reserved for Compaq...
A.2.2 Opcodes Reserved for PALcode Table A–4 lists the 21264/EV67-specific instructions. See Chapter 2 for more information. Table A–4 Opcodes Reserved for PALcode 21264/EV67 Architecture Mnemonic Opcode Mnemonic HW_LD PAL1B HW_ST PAL1F HW_REI PAL1E HW_MFPR PAL19 HW_MTPR PAL1D A.3 IEEE Floating-Point Instructions Table A–5 lists the hexadecimal value of the 11-bit function code field for the IEEE...
Table A–7 lists the hexadecimal value of the 11-bit function code field for the floating- point instructions that are not directly tied to IEEE or VAX floating point. The opcode for the following instructions is 17 Alpha 21264/EV67 Hardware Reference Manual VAX Floating-Point Instructions /SUC...
6-bit opcode and ffff is the hexadecimal 26-bit function code. Table A–10 Required PALcode Function Codes Mnemonic DRAINA HALT Alpha 21264/EV67 Hardware Reference Manual Required PALcode Function Codes \ PAL \ LDQ_L (mem) (mem)
IEEE Floating-Point Conformance A.8 IEEE Floating-Point Conformance The 21264/EV67 supports the IEEE floating-point operations defined in the Alpha Sys- tem Reference Manual, Revision 7 and therefore also from the Alpha Architecture Handbook, Version 4. Support for a complete implementation of the IEEE Standard for Binary Floating-Point Arithmetic (ANSI/IEEE Standard 754 1985) is provided by a combination of hardware and software.
The 21264/EV67 does not produce a denormal result for the underflow exception. Instead, a true zero (+0) is written to the destination register. In the 21264/EV67, the FPCR underflow to zero (UNDZ) bit must be set if the underflow disable (UNFD) bit is set.
Page 282
QNaN CQNaN root True or False False for EQ, True for UN False for EQ,True for UN True or False False False Alpha 21264/EV67 Hardware Reference Manual Exception (none) (none) Invalid Op Invalid Op (none) Invalid Op Invalid Op Div Zero...
Page 283
FBEQ FBNE FBLT FBLE FBGT FBGE LDS LDT STS STT CPYS CPYSN FCMOVx See Section 2.14 for information about the floating-point control register (FPCR). Alpha 21264/EV67 Hardware Reference Manual IEEE Floating-Point Conformance 21264/EV67 Hardware Supplied Result Exception Invalid Op Result...
B.1 Boundary-Scan Register The Boundary-Scan Register (BSR) on the 21264/EV67 is 367 bits long. It is accessed by the three public (SAMPLE, EXTEST, CLAMP) instructions. The register operation for the public instructions is compliant with the IEEE 1149.1 standard.
Page 296
( BC_3, SysDataInValid_L, " 0 ( BC_3, SysDataOutValid_L, attribute DESIGN_WARNING of Alpha_21264/EV67: entity is "1. IEEE 1149.1 circuits on Alpha 21264/EV67 are designed primarily to support " testing in off-line module manufacturing environment. The SAMPLE/PRELOAD"& " instruction support is designed primarily for supporting interconnection"&...
Page 301
DTB_ALT_MODE (SCRBRD=6)*/ ** MAP_SHADOW_REGISTERS ** The shadow registers are mapped. This code may be done by the SROM Alpha 21264/EV67 Hardware Reference Manual /* initialize Int. Reg. 27*/ /* initialize F.P. Reg. 26*/ /* initialize F.P. Reg. 27*/ /* initialize Int.
Page 302
/* continue executing in next block*/ /* fetch in next block*/ /* initialize Shadow Reg. 2*/ /* initialize Shadow Reg. 3*/ /* continue executing in next block*/ /* fetch in next block*/ /* initialize Shadow Reg. 4*/ Alpha 21264/EV67 Hardware Reference Manual...
Page 303
.align 6 bccshf:mtpr r1,EV6__DATA subq r0,1,r0 r0,bccend r1,6,r1 Alpha 21264/EV67 Hardware Reference Manual /* initialize Shadow Reg. 5*/ /* continue executing in next block*/ /* fetch in next block*/ /* initialize Shadow Reg. 6*/ /* initialize Shadow Reg. 7*/ /* continue executing in next block*/ /* go back to 1st block and start executing*/ /* data<35:32>...
Page 304
/* under the above mtpr to SCRBRD=4*/ /* value = 0x000000000000001F*/ /* clear bits in DC_STAT (SCRBRD=6)*/ /* nop*/ /* and 1st clear PCTR_CTL (SCRBRD=4)*/ /* set up value for demon write*/ /* set up value for demon write*/ /* nop*/ Alpha 21264/EV67 Hardware Reference Manual...
Page 305
* already been initialized. This technique * can sometimes be used to debug snippets of * this code. Alpha 21264/EV67 Hardware Reference Manual /* and 2nd clear PCTR_CTL (SCRBRD=4)*/ /* set up value for demon write*/ /* set up value for demon write*/...
HW_RET instructions that do not have the STALL bit set. PALcode Restrictions and Guidelines D–8 /* r0 <- current location */ /* r1 <- cc_ctl enable bit */ /* Enable/clear the cycle counter. */ Alpha 21264/EV67 Hardware Reference Manual...
D.5 Restriction 7 : Replay Trap, Interrupt Code Sequence, and STF/ ITOF On an Mbox replay trap, the 21264/EV67 Ibox guarantees that the refetched load or store instruction that caused the trap is issued before any newer load or store instruc- tions.
Istream ACV limits, and the IVA_FORM format selection. The VA_CTL[VA_48] bit determines the VA_FORM format selection and the Dstream ACV limits. IPR mode bits I_CTL[VA_FORM_32] and VA_CTL[VA_FORM_32] should be consistent when executing in native mode. PALcode Restrictions and Guidelines D–10 Alpha 21264/EV67 Hardware Reference Manual...
(a non-PALmode trap) until the register has been unlocked. After being unlocked, a subsequent new path exception condition will be allowed to reload the register and trap to PALcode. The 21264/EV67 may complete execution of the first PALcode flow, encountering the second exception condition before the delimit- ing instruction is retired, hence the need for the locking mechanism to ensure visibility of the initial register value.
The following example contains a code sequence that creates the dependency chain. :Assume Ra holds value to write to ASN0/ASN1 HW_MFPR R0, VA, SCBD<7,6,5,4> XOR R0, R0, R0 BIS R0, R9, R9 PALcode Restrictions and Guidelines D–12 Alpha 21264/EV67 Hardware Reference Manual...
A HW_ST/P/CONDITIONAL will not clear the lock flag such that a successive store- conditional (either STx_C or HW_ST/C) might succeed even in the absence of a load- locked instruction. In the 21264/EV67, a store-conditional is forced to fail if there is an intervening memory operation between the store-conditional and its address-matching LDxL.
(up to four instructions) of all PALcode flows except CALL_PAL flows. Conditional branches should be avoided in this window. PALcode Restrictions and Guidelines D–14 Alpha 21264/EV67 Hardware Reference Manual...
Istream fill requests and stalls instruction fetch until after the desired MTPR/MFPR action is completed. This code disables Istream prefetching by way of a HW_MTPR to I_CTL[SBE], IC_FLUSH, and HW_RET_STALL sequence. Alpha 21264/EV67 Hardware Reference Manual PALcode Restrictions and Guidelines D–15...
In normal operation, with counters enabled, a counter overflow will produce an overflow pulse, clear the counter, and produce a performance counter interrupt. Interrupts can only be blocked for one cycle. Alpha 21264/EV67 Hardware Reference Manual Restriction 31 : I_CTL[VA_48] Update ; block 6 ;...
The new update value must not be within one cycle of overflow (within 16 for SL0, within 4 for SL1) as required by Section D.28. PALcode Restrictions and Guidelines D–18 Alpha 21264/EV67 Hardware Reference Manual...
2. There cannot be any mispredictable/trappable instructions in the previous fetch block. D.40 Restriction 44: Not Applicable to the 21264/EV67 D.41 Restriction 45: No HW_JMP or JMP Instructions in PALcode Do not include HW_JMP or JMP instructions in PALcode; use HW_RET instead.
Because CBOX_ERR[C_ADDR] is not guaranteed, the CRD_HANDLER might not evict the sberr. PALcode Restrictions and Guidelines D–22 ; make sure hw_ret goes ; Hold up loads ; Hold up loads ; Hold up loads ; Ignore restriction 43 ; Return Alpha 21264/EV67 Hardware Reference Manual...
Page 321
<.+4> r31, next_reread s7, sys__cbox Alpha 21264/EV67 Hardware Reference Manual ; Loop dec value ; Start offset ; Block size (64K -> size of dcache) ; 2X bcache size ; Skip next instruction if ADDR ;...
Writes to DC_CTL[F_BAD_DECC] and DC_CTL[DCDAT_ERR_EN] must be brack- eted by MB instructions to quiesce the memory system. The Istream must also be qui- esced before and during the sequence, as described in Section D.26. PALcode Restrictions and Guidelines D–24 Alpha 21264/EV67 Hardware Reference Manual...
This appendix provides the pin interface between the 21264/EV67 and Bcache SSRAMs. E.1 Forwarding Clock Pin Groupings Table E–1 lists the correspondance between the clock signals for the 21264/EV67 and Bcache (late-write non-bursting and dual-data rate) SSRAMs. Table E–1 Bcache Forwarding Clock Pin Groupings...
BcTagValid_H E.2 Late-Write Non-Bursting SSRAMs Table E–2 provides the data pin connections between late-write non-bursting SSRAMs and the 21264/EV67 or the system board. Table E–3 provides the same information for the tag pins. Data Pin Usage Table E–2 Late-Write Non-Bursting SSRAMs Data Pin Usage...
Unconnected E.3 Dual-Data Rate SSRAMs Table E–4 provides the data pin connections between dual-data rate SSRAMs and the 21264/EV67 or the system board. Table E–5 provides the same information for the tag pins. Data and Tag Pin Usage Table E–4 Dual-Data Rate SSRAM Data Pin Usage...
From board, pulled up to VDD Unconnected or pulled down to VSS BcDataOE_L From board, pulled down to VSS Table E–5 Dual-Data Rate SSRAM Tag Pin Usage 21264/EV67 Signal Name or Board Connection Dual-Data Rate SSRAM Tag Pin Name BcAdd_H[23:6] BcTag_H[33:20] BcTagOE_L BcTagWr_L...
This glossary provides definitions for specific terms and acronyms associated with the Alpha 21264/EV67 microprocessor and chips in general. abort The unit stops the operation it is performing, without saving status, to perform some other operation. address space number (ASN) An optionally implemented register used to reduce the need for invalidation of cached address translations for process-specific addresses when a context switch occurs.
Page 328
All data and commands are associated with a clock and the receiver’s latch on both the rise and fall of the clock. Bit times are a multiple of the 21264/EV67 clocks. Systems must produce a bit time identical to 21264/EV67’s bit time. The bit time is one-half the period of the forwarding clock.
Page 329
Also called cache consis- tency. cache fill An operation that loads an entire cache block by using multiple read cycles from main memory. cache flush An operation that marks all cache blocks as invalid. Alpha 21264/EV67 Hardware Reference Manual Glossary –3...
Dual-data rate. A dual-data rate SSRAM can provide data on both the rising and falling edges of the clock signal. denormal An IEEE floating-point bit pattern that represents a number whose magnitude lies between zero and the smallest finite number. Dual inline package. Alpha 21264/EV67 Hardware Reference Manual Glossary –5...
Page 332
The error may be correctable (soft error) or uncorrectable (hard error). Emitter-coupled logic. EEPROM Electrically erasable programmable read-only memory. A memory device that can be byte-erased, written to, and read from. Contrast with FEPROM. Glossary –6 Alpha 21264/EV67 Hardware Reference Manual...
The framing clock defines the start of a transmission either from the system to the 21264/EV67 or from the 21264/EV67 to the system. The framing clock is a power-of- 2 multiple of the 21264/EV67 GCLK frequency, and is usually the system clock. The framing clock and the input oscillator can have the same frequency.
Page 334
Instruction cache. A cache reserved for storage of instructions. One of the three areas of primary cache (located on the 21264/EV67) used to store instructions. The Icache con- tains 8KB of memory space. It is a direct-mapped cache. Icache blocks, or lines, con- tain 32 bytes of instruction stream data with associated tag as well as a 6-bit ASM field and an 8-bit branch history field per block.
(LW) Four contiguous bytes starting on an arbitrary byte boundary. The bits are numbered from right to left, 0 through 31. Load queue. Least significant bit. Alpha 21264/EV67 Hardware Reference Manual Glossary –9...
Page 336
A board on which logic devices (such as transistors, resistors, and memory chips) are mounted and connected to perform a specific system function. module-level cache See second-level cache. Metal-oxide semiconductor. MOSFET Metal-oxide semiconductor field-effect transistor. Glossary –10 Alpha 21264/EV67 Hardware Reference Manual...
Page 337
0 through 127. OpenVMS Alpha operating system The version of the open VMS operating system for Alpha platforms. operand The data or register upon which an operation is performed. Alpha 21264/EV67 Hardware Reference Manual Glossary –11...
Page 338
A CPU design technique whereby multiple instructions are simultaneously overlapped in execution. Programmable logic array. PLCC Plastic leadless chip carrier or plastic-leaded chip carrier. Programmable logic device. Phase-locked loop. PMOS P-type metal-oxide semiconductor. Probe queue. Glossary –12 Alpha 21264/EV67 Hardware Reference Manual...
Page 339
Row address select. Read-after-write. READ_BLOCK A transaction where the 21264/EV67 requests that an external logic unit fetch read data. read data wrapping System feature that reduces apparent memory latency by allowing read data cycles to differ the usual low-to-high sequence. Requires cooperation between the 21264/EV67 and external hardware.
Page 340
Read-only memory. Register-transfer logic. Serial access memory. Should be one. Should be zero. scheduling The process of ordering instruction execution to obtain optimum performance. Glossary –14 Alpha 21264/EV67 Hardware Reference Manual...
Page 341
A stack uses the last-in/first-out concept. As items are added to (pushed on) the stack, the stack pointer decrements. As items are retrieved from (popped off) the stack, the stack pointer increments. Alpha 21264/EV67 Hardware Reference Manual Glossary –15...
Page 342
An operation that may halt the processor or cause it to lose information. Only privileged software (that is, software running in kernel mode) can trigger an UNDEFINED opera- tion. (This meaning only applies when the word is written in all upper case.) Glossary –16 Alpha 21264/EV67 Hardware Reference Manual...
Page 343
A cache that is addressed with virtual addresses. The tag of the cache is a virtual address. This process allows direct addressing of the cache without having to go through the translation buffer making cache hit times faster. VLSI Very-large-scale integration. Virtual program counter. VRAM Video random-access memory. Alpha 21264/EV67 Hardware Reference Manual Glossary –17...
WRITE_BLOCK A transaction where the 21264/EV67 requests that an external logic unit process write data. write data wrapping System feature that reduces apparent memory latency by allowing write data cycles to differ the usual low-to-high sequence.
Page 345
BC_CLK_DELAY Cbox CSR 4–45 defined 5–35 BC_CLK_LD_VECTOR Cbox CSR defined 5–38 BC_CLKFWD_ENABLE Cbox CSR defined 5–36 Alpha 21264/EV67 Hardware Reference Manual BC_CLOCK_OUT Cbox CSR BC_CPU_CLK_DELAY Cbox CSR defined BC_CPU_LATE_WRITE_NUM Cbox CSR defined BC_DDM_FALL_EN Cbox CSR defined BC_DDM_RISE_EN Cbox CSR defined...
Page 347
CMOV instruction, special cases of COLD reset machine state 7–17 Commands 21264/EV67 to system 4–19 system to 21264/EV67 4–26 when to NXM 4–38 Alpha 21264/EV67 Hardware Reference Manual Conventions abbreviations address aligned 4–13 bit notation D–15 caution data units do not care...
Page 351
ITB_MISS fault 6–14 ITB_PTE array write register 5–6 at power-on reset state 7–14 Alpha 21264/EV67 Hardware Reference Manual ITB_TAG array write register at power-on reset state IVA_FORM instruction virtual address format register at power-on reset state JITTER_CMD Cbox CSR, defined...
Page 352
Open-drain output driver. See O_OD pin type Operating temperature 4–5 Packaging Paired instruction fetch order PAL_BASE register after fault reset after warm reset at power-on reset state through sleep mode Alpha 21264/EV67 Hardware Reference Manual 7–16 6–12 6–14 3–3 4–38 4–21 4–21 3–3 9–2 9–4...
Page 353
PLL_IDD, values for 9–3 PLL_VDD signal pin 3–5 PLL_VDD, values for 9–3 PllBypass_H signal pin 3–5 PMPC ProfileMe register 5–8 Alpha 21264/EV67 Hardware Reference Manual Ports IEEE 1149.1 serial terminal SROM load Power maximum sleep defined Power supply sequencing Power-on...
Page 355
SysDataInValid_L signal pin rules for SysDataOutClk_L signal pin 4–18 SysDataOutValid_L signal pin rules for 5–34 SysDc commands system probes, with SysDc field, system to 21264/EV67 commands 5–36 4–29 4–18 SYSDC_DELAY Cbox CSR defined 5–34 SysFillValid_L signal pin rules for System clock ratio configuration...
Page 356
Write-after-read. See WAR 4–21 Write-after-write. See WAW WrLWs, 21264/EV67 command WrQWs, 21264/EV67 command WrVictimBlk, 21264/EV67 command system probes, with X convention 7–18 7–18 7–19 7–17 Alpha 21264/EV67 Hardware Reference Manual 7–18 7–17 6–14 2–6 7–11 2–6 2–34 4–38 4–37 4–22 4–39 4–5...
Need help?
Do you have a question about the 21264 and is the answer not in the manual?
Questions and answers