The Digital AlphaServer 8200 and 8400 systems are designed around the
DECchip 21164 CPU. The TLSB is the system bus that supports nine nodes in
the 8400 system and five nodes in the 8200 system. The AlphaServer 8400 can
be configured with up to six single or dual processor CPU modules (KN7CC),
seven memory modules (MS7CC), and three I/O modules (KFTHA and
KFTIA). One slot is dedicated to I/O and is normally occupied by the integrated I/O module (KFTIA) that supports PCI bus, XMI, and Futurebus+
adapters. All other nodes can be interchangeably configured for CPU or memory modules. The AlphaServer 8200 can be configured with up to three CPU
modules, three memory modules, and three I/O modules.
digital equipment corporation
maynard, massachusetts
First Printing, May 1995
The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation.
Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document.
The software, if any, described in this document is furnished under a license and may be used or copied only
in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies.
The following are trademarks of Digital Equipment Corporation: AlphaGeneration, AlphaServer, DEC,
DECchip, DEC LANcontroller, OpenVMS, StorageWorks, VAX, the AlphaGeneration logo, and the DIGITAL
logo.
OSF/1 is a registered trademark of the Open Software Foundation, Inc. Prestoserve is a trademark of Legato
Systems, Inc. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through
X/Open Company Ltd.
FCC NOTICE: The equipment described in this manual generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection
against such radio frequency interference when operated in a commercial environment. Operation of this
equipment in a residential area may cause interference, in which case the user at his own expense may be
required to take measures to correct the interference.
Contents
Preface ............................................................................................................................................ xv
This manual is intended for developers of system software and for service
personnel. It discusses the AlphaServer 8200/8400 systems that are designed around the DECchip 21164 CPU and use the TLSB bus as the main
communication path between all the system modules. The manual describes the operations of all components of the system: the TLSB bus,
CPU modules, memory modules, and the I/O modules. It discusses in detail the functions of all registers in the system. When necessary, the manual refers the reader to other documents for more elaborate discussions or
for specific information. Thus, the manual does not give the register files
of PCI bus devices but indicates sources where information can be found.
The manual assumes programming knowledge at machine language level
and familiarity with the OpenVMS Alpha and Digital UNIX (formerly
DEC OSF/1) operating systems.
Document Structure
Preface
The material is presented in eight chapters.
Chapter 1, Overview, presents an overall introduction to the server sys-
tem.
Chapter 2, TLSB Bus, describes the main communication path of the sys-
tem. It discusses the operations of the address bus and the data bus, CSR
addressing, and errors that can occur during bus transactions.
Chapter 3, CPU Module, describes the major components and operations
of the CPU module. It explains the CPU module’s memory and I/O address
spaces, and gives a summary of the errors detected by the CPU module.
Chapter 4, Memory Subsystem, describes the structure of the memory
hierarchy from the system perspective. The memory hierarchy comprises
the DECchip 21164 internal cache, the second-level cache implemented on
the CPU chip, the backup cache implemented on the CPU module, and the
main memory that is implemented as a separate module and forms a node
on the TLSB bus. The chapter provides a discussion of the various ways
main memory can be organized to optimize access time.
Chapter 5, Memory Interface, describes the various components of the
memory module, the memory data interface, and how the CSR interface
manages the transfer of information between the TLSB bus and the TLSB
accessible memory module registers.
Chapter 6, I/O Port, describes the configuration of the I/O port and the
main components of the I/O subsystem (KFTHA and KFTIA modules). It
discusses addressing of memory and I/O devices and accessing of remote
I/O node CSRs through mailboxes and direct I/O window space. The
xv
Terminology
KFTIA and KFTHA support the PCI bus, XMI bus, and the Futurebus+,
depending on the system in which they are used. The chapter describes
the transaction types on the TLSB interface and the hose interface. It presents a brief survey of the integrated I/O port (KFTIA). The survey focuses
mainly on the integrated I/O section of the module, which provides two PCI
buses that support ports for PCI devices such as Ethernet, SCSI, FDDI,
and NVRAM. The chapter also discusses the types of errors that affect the
hoses and how the I/O port handles errors.
Chapter 7, System Registers, describes in detail the functions of the system registers, which include the TLSB bus registers, CPU module registers, memory module registers, and I/O port registers. For KFTIA registers and device registers supported by the integrated I/O port, the reader is
referred to source material. This chapter is the only place where functions
of all registers are discussed fully at the bit level.
Chapter 8, Interrupts, gives an overview of various interrupts within the
system. It discusses vectored and nonvectored interrupts, interrupt rules,
mechanisms, and service.
Results of operations termed Unpredictable may vary from moment to
moment, implementation to implementation, and instruction to instruction
within implementations. Software must never use Unpredictable results.
Operations termed Undefined may vary from moment to moment, implementation to implementation, and instruction to instruction within implementations. Undefined operations may halt the processor or cause it to
lose information. However, they do not cause the processor to hang; that
is, reach a state from which there is no transition to a normal state of instruction execution. Nonprivileged software cannot invoke Undefined operations.
Documentation Titles
Table 1 lists the books in the Digital AlphaServer 8200 and 8400 documentation set.
xvi
Table 1 Digital AlphaServer 8200/8400 Documentation
BA350-LA Modular Storage Shelf User’s Guide
CIXCD Interface User Guide
DEC FDDIcontroller 400 Installation/Problem Solving
EK–CSEPG–MA
EK–BA350–CG
EK–BA350–UG
EK–350LA–UG
EK–CIXCD–UG
EK–DEMFA–IP
DEC FDDIcontroller/Futurebus+ Installation Guide
DEC FDDIcontroller/PCI User Information
DEC LANcontroller 400 Installation Guide
DSSI VAXcluster Installation/Troubleshooting Manual
EtherWORKS Turbo PCI User Information
KZPSA PCI to SCSI User’s Guide
RF Series Integrated Storage Element User Guide
StorageWorks RAID Array 200 Subsystem Family
Installation and Configuration Guide
StorageWorks RAID Array 200 Subsystem Family
Software User’s Guide for OpenVMS AXP
StorageWorks RAID Array 200 Subsystem Family
Software User’s Guide for DEC OSF/1
Operating System Manuals
Alpha Architecture Reference Manual
DEC OSF/1 Guide to System Administration
Guide to Installing DEC OSF/1
OpenVMS Alpha Version 6.2 Upgrade and Installation Manual
Engineering Specifications
TurboLaser System Bus (TLSB) Specification
TurboLaser EV5 Dual-Processor Module Specification
DECchip 21164 Functional Specification
DC287 Ethernet Controller 21040 Engineering Specification
21041-AA Integrated FDDI Controller Advanced Information
PCI NVRAM Engineering Specification
NCR 53C810 PCI–SCSI I/O Processor Data Manual
The computer system is an AlphaGeneration server very similar to but
with twice the performance of DEC 7000/10000 systems. It is built around
the TLSB bus and supports the OpenVMS Alpha and Digital UNIX operating systems. It is manufactured in two models: AlphaServer 8200 and AlphaServer 8400. The AlphaServer 8400 features nine nodes, while AlphaServer 8200 supports only five nodes.
The system uses three types of modules:
•CPU modules, each containing one or two DECchip 21164 CPUs
•Memory modules
•I/O ports that interface to other I/O buses (XMI, Futurebus+,and PCI)
NOTE: Unless otherwise specified, all discussions in this manual apply to both Al-
phaServer systems.
1.1 Configuration
The system provides a wide range of configuration flexibility:
•A 9-slot system centerplane bus that supports up to nine CPU, mem-
•The system supports from one to 12 DECchip 21164 CPUs. Each CPU
•The system supports a range of memory sizes from 128 Mbytes to 14
•The system supports up to three I/O ports, providing up to 12 I/O chan-
•The system supports an integrated I/O port providing direct access to
ory, or I/O nodes, and can operate at speeds ranging from 10 ns (100
MHz) to 30 ns (33.33 MHz).
has a 4-Mbyte backup cache. The CPU module design supports a range
of processor clocks from 7.0 ns (142.9 MHz) to 2.8 ns (357 MHz).
Gbytes. Memory is expandable using 128-Mbyte, 256-Mbyte, 512Mbyte, 1-Gbyte, and 2-Gbyte modules.
nels. Each I/O channel connects to one of the following:
— XMI, for attaching legacy XMI I/O devices for high performance
— Futurebus+, for attaching high-performance third-party peripherals
— PCI, for attaching low-cost, industry-standard peripherals, and for
compatibility with other DECchip 21164 platforms offered by Digital
two twisted-pair (10BaseT) Ethernet ports, one FDDI port, and four
SCSI ports. The integrated I/O port can also connect to one XMI,
Overview 1-1
Futurebus+, or PCI bus. The local I/O options on the integrated I/O
port appear to software as a PCI bus connected to a hose.
Figure 1-1 shows a block diagram of the 8400 system.
Figure 1-1AlphaServer 8400 System Block Diagram
TLSB I/O
Port
Module
XMI
Interface
FBUS+
Interface
XMI
Interface
PCI
Interface
CPU,
MEM, or
I/O Module
TLSB Bus; 40-bit address path, 256-bit data path
CPU or
MEM
Module
To/from XMI
To/from Futurebus+
To/from XMI
To/from PCI
CPU,
MEM, or
I/O Module
CPU or
MEM
Module
CPU,
MEM, or
I/O Module
CPU or
MEM
Module
CPU,
MEM, or
I/O Module
CPU or
MEM
Module
BXB0813.AI
1.2 Bus Architecture
The system bus, the TLSB, is a limited length, nonpended, pipelined synchronous bus with separate 40-bit address and 256-bit data buses. The
TLSB supports a range of cycle times, from 10 to 30 ns. At 10 ns, the
maximum bandwidth available is 2.1 Gbytes/sec.
The TLSB runs synchronously with the CPU clock, and its cycle time is an
integer multiple of the CPU clock. Memory DRAM cycle time is not synchronous with the TLSB clock. This permits memory access times to be
adjusted as the CPU clock is adjusted.
The TLSB supports nine nodes. One node (slot 8) is dedicated to I/O. This
node has special arbitration request lines that permit the node to always
arbitrate as the highest priority or the lowest priority device. This scheme
guarantees the node a maximum upper bound on memory latency. Any of
the other eight nodes can be a CPU or memory node. Four of these remaining nodes can be I/O ports.
Access to the address bus is controlled by a distributed arbitration scheme
implemented by all nodes on the bus. Access to the data bus is governed
by the order in which address bus transactions occur. Address and data
1-2 Overview
bus transactions may be overlapped, and these transactions may be overlapped with bus arbitration. Arbitration priority rotates in a round-robin
scheme among the nodes. A node in the slot dedicated to I/O follows a special arbitration algorithm so that it cannot consume more than a certain
fraction of the bus bandwidth.
The TLSB supports a conditional write-update cache protocol. This protocol allows a node to implement a write-back cache while also offering a
very efficient method for sharing writable data. All bus data transfers are
naturally aligned, 64-byte blocks.
With this protocol, a CPU cache retains the only up-to-date copy of data.
When this data is requested, the CPU with the most recent copy returns it.
Memory ignores the transaction. Special TLSB signal lines coordinate this
operation.
The TLSB uses parity protection on the address bus. One parity bit protects the address, and one bit protects the command and other associated
fields.
The data bus is protected by ECC. An 8-bit ECC check code protects each
64 bits of data. The generator and ultimate user of the data calculate ECC
check codes, report, and correct any errors detected. TLSB bus interfaces
check (but do not correct) ECC to aid in error isolation. For example, an
I/O device calculates ECC when DMA data is written to memory. When a
CPU reads this data, the TLSB interface on the CPU module checks and
notes any errors, but the DECchip 21164 actually corrects the data prior to
using it.
The ECC check code corrects single-bit errors. It detects double-bit errors,
and some 4-bit errors, in each 64-bit unit of data.
1.3 CPU Module
The CPU module contains one or two DECchip 21164 microprocessors. In
dual-processor modules, each processor operates independently and has
its own backup cache. A single interface to the TLSB is shared by both
CPU chips. The interface to console support hardware on the CPU module
is also shared by both microprocessors. The main sections of the CPU
module are:
•DECchip 21164
•Backup cache
•TLSB interface
•Console support hardware
A simple block diagram of the CPU module is given in Chapter 3.
1.3.1 DECchip 21164
The DECchip 21164 microprocessor is a CMOS-5 (0.5 micron) superscalar,
superpipelined implementation of the Alpha architecture. A brief listing of
the DECchip 21164 features is given in Chapter 3. DECchip 21164 implements the Alpha architecture together with its associated PALcode. Refer
Overview 1-3
to the DECchip 21164 Functional Specification for a complete description
of the DECchip 21164 and PALcode.
1.3.2 Backup Cache
Each backup cache (B-cache) is four Mbytes in size. In a dual-processor
module there are two independent backup caches, one for each CPU. Each
B-cache is physically addressed, direct-mapped with a 64-byte block and
fill size. The B-cache is under the direct control of the DECchip 21164.
The B-cache conforms to the conditional write-update cache coherency protocol as defined in the TurboLaser System Bus Specification.
The CPU module contains a duplicate copy of each B-cache tag store used
to maintain systemwide cache coherency. The module checks the duplicate
tag store on every TLSB transaction and communicates any required
changes in B-cache state to the DECchip 21164.
The CPU module also maintains a victim buffer for each B-cache. When
the DECchip 21164 evicts a cache block from the B-cache, the victim buffer
holds it. The DECchip 21164 writes the block to memory as soon as possible.
1.3.3 TLSB Interface
The CPU module uses six gate arrays to interface to the TLSB. The MMG
gate array orders requests from both DECchip 21164 processors. The ADG
gate array contains the TLSB interface control logic. It handles TLSB arbitration and control, monitors TLSB transactions, and schedules data movements with either processor as necessary to maintain cache coherency.
Four identical DIGA gate arrays interface between the 256-bit TLSB data
bus and the 128-bit DECchip 21164 processors. See Chapter 3 for brief
discussions of the gate arrays.
1.3.4 Console Support Hardware
The CPU module console support hardware consists of:
•Two Mbytes of flash EEPROM used to store console and diagnostics
software. A portion of this EEPROM is used to store module and system parameters and error log information.
•One UART used to communicate with the user and power supplies.
•Battery-powered time-of-year (TOY) clock.
•One green LED to indicate CPU module self-test status.
•A second console UART for each processor, for engineering and manu-
facturing debug use.
An 8-bit Gbus, controlled by the ADG gate array, is provided to access the
console support hardware.
1.4 Memory Module
Memory modules are available in the following sizes: 128 Mbytes, 256
Mbytes, 512 Mbytes, 1 Gbyte, and 2 Gbytes. Sizes up to 1 Gbyte are sup-
1-4 Overview
ported by a single motherboard design. The 2-Gbyte memory option uses
a different motherboard and SIMM design.
A maximum of seven memory modules may be configured on the TLSB (in
a system with one CPU module and one I/O module). Thus, the maximum
memory size is 14 Gbytes, using 2-Gbyte modules.
Memory operates within the 10–30 ns TLSB cycle time range. To keep
memory latency low, the memory module supports three different DRAM
cycle times. As TLSB cycle time is decreased (slowed down), the memory
module cycle time can be increased (sped up) to ensure that data latency
remains relatively constant, independent of TLSB cycle time.
Each memory module is organized into two banks of independently accessible random memory. Bank interleaving occurs on 64-byte boundaries,
which is the TLSB data transfer size.
Different size memory modules can be interleaved together. For example,
four 128-Mbyte modules can be combined to appear as a single 512-Mbyte
module, and this set can be interleaved with a 512-Mbyte module. In this
case, the five modules are four-way interleaved.
Memory is protected by a 64-bit ECC algorithm. An 8-bit ECC check code
protects each 64 bits of data. This algorithm allows correction of single-bit
failures and the detection of double-bit and some nibble failures. The same
algorithm is used to protect data across the TLSB and within the CPU
module caches. ECC is checked by the memory when data is read out of
memory. It is also checked when data is received from the TLSB, prior to
writing data into the memory. Memory is designed so that a single failing
DRAM cannot cause an uncorrectable memory error.
The memory module does not correct ECC errors. If a data block containing a single-bit ECC error is written by a CPU or I/O device to memory, the
memory checks the ECC and signals a correctable error, but it does not
correct the data. The data is written to the DRAMs with the bad ECC
code. Only CPU and I/O port modules correct single-bit ECC errors.
Refer to Chapters 4 and 5 for a thorough discussion of the memory module.
1.5 I/O Architecture
The I/O system components consist of:
•I/O port module (KFTHA)
•Integrated I/O port module (KFTIA)
•XMI bus adapter (DWLMA)
•Futurebus+ adapter (DWLAA)
•PCI bus adapter (DWLPA)
•Memory Channel interface (RM in register mnemonics)
The KFTHA and KFTIA modules reside on the TLSB and provide the interface between the TLSB and optional I/O subsystems.
The KFTHA provides connections for up to four optional XMI, Futurebus+,
or PCI buses, in any combination, through a cable called a hose.
The KFTIA provides a connection to one optional XMI, Futurebus+, or PCI
bus through a hose. It also contains an on-module PCI bus with connec-
Overview 1-5
tion to two 10BaseT Ethernet ports, one FDDI port, and three FWD and
one single-ended SCSI ports.
The DWLMA is the interface between a hose and a 14-slot XMI bus. It
manages data transfer between XMI adapters and the I/O port.
The DWLAA is the interface between a hose and a 10-slot Futurebus+ card
cage. It manages data transfer between Futurebus+ adapters and the I/O
port.
The DWLPA is the interface between a hose and a 12-slot, 32-bit PCI bus.
It manages data transfer between PCI adapters and the I/O port. The PCI
is physically implemented as three 4-slot PCI buses, but these appear logically to software as one 12-slot PCI bus. The PCI also supports the EISA
bus.
The Memory Channel interface connects a hose to a 100 MB/sec Memory
Channel bus. This bus is a memory-to-memory computer system interconnect, and supports up to 8 nodes. With appropriate fiber optic bridges, this
can be expanded to 64 nodes.
The TLSB supports up to three I/O ports of either type. The first (or only)
I/O port in the system is installed in the dedicated I/O TLSB slot (slot 8).
Any latency-sensitive devices should be configured to this I/O port. The
second I/O port, if present, should be installed in the highest number slot
accommodating an I/O port.
The I/O port uses mailbox operations to access CSR locations on the remote
I/O bus. Mailbox operations are defined in the Alpha System ReferenceManual. For PCI buses, direct-mapped I/O operations are also supported.
1.6 Software
1.6.1 Console
The system software consists of the following components:
•Console
•OpenVMS Alpha operating system
•Digital UNIX operating system
•Diagnostics
The following subsections provide brief overviews of the system software
components.
The console firmware supports the two operating systems as well as the
following system hardware:
•DECchip 21164 processor
•One or two processors per CPU module and up to 12 processors per
system
•Multiple I/O ports per system
•PCI I/O bus and peripherals
•Memory Channel
The console supports boot devices on the following I/O port adapters:
1-6 Overview
•KDM70 – XMI to SI disk/tape
•KZMSA – XMI to SCSI disk/tape
•KFMSB – XMI to DSSI disk/tape and OpenVMS clusters
•CIXCD-AC – XMI to CI HSC disk/tape and OpenVMS clusters
•DEMNA – XMI to Ethernet networks and OpenVMS clusters
•DEMFA – XMI to FDDI networks and OpenVMS clusters
•DEFAA – Futurebus+ to FDDI networks and OpenVMS clusters
Booting is suported from PCI SCSI disk, Ethernet, and FDDI devices.
1.6.2 OpenVMS Alpha
OpenVMS Alpha fully supports the system. Symmetrical multiprocessing,
OpenVMS clusters, and all other OpenVMS Alpha features are available
on the system. OpenVMS Alpha is released only on CD-ROM, which is
supported for initial system load through a SCSI device.
1.6.3 Digital UNIX
The system fully supports the Digital UNIX operating system, which is released only on CD-ROM. CD-ROM is supported for initial system load
through a SCSI device.
1.6.4 Diagnostics
The system diagnostic software is composed of:
•ROM-based diagnostics
•The loadable diagnostic execution environment
•Online exercisers
1.6.4.1ROM-Based Diagnostics
CPU module ROMs contain a complete set of diagnostics for the base system components. These diagnostics include CPU, memory, I/O port, and
generic exercisers for multiprocessing, memory, and disks.
The following diagnostics are included in the CPU module ROMs:
A subset of these diagnostics is invoked at system power-up. Optionally,
they may be invoked on every system boot. The subset can also be invoked
by the user through console command.
Note that any of the diagnostics listed above can be individually invoked
by the user through console command.
1.6.4.2Loadable Diagnostic Execution Environment
The loadable diagnostic executive is essentially a loadable version of the
ROM-based diagnostic executive. It supports loading from any device for
which a console boot driver exists. Once loaded, diagnostics are run and
monitored using the same commands as for the ROM-based diagnostics.
The LFU firmware update utility is a loadable program. This utility updates CPU console and diagnostic firmware, and firmware on I/O adapters.
1.6.4.3Online Exercisers
The VET online exerciser tool is available for the systems. This tool provides a unified exercising environment for the operating systems. This exerciser is on each operating system kit. It is invoked as a user-mode program.
The following VET exercisers are available:
•Load
•File
•Raw disk
•Tape
•Memory
•Network
1-8 Overview
2.1 Overview
Chapter 2
TLSB Bus
This chapter provides a brief overview of the TLSB bus. For more detailed
discussions and timing diagrams for the various bus cycles, refer to the
TurboLaser System Bus Specification.
The TLSB bus is a limited length, nonpended, synchronous bus with a
separate address and data path. Ownership of the address bus is determined using a distributed arbitration protocol. The data bus does not require an arbitration scheme. The data bus transfers data in the sequence
order in which command/addresses occur. The combination of separate address and data paths with an aggressive arbitration scheme permits a low
latency protocol to be implemented.
Because the address and data buses are separate, there is maximum overlap between command issues and data return. The TLSB also assumes
that the CPU nodes run the module internal clock synchronous to the bus
clock, eliminating synchronizers in the bus interface and their associated
latency penalties. The TLSB provides control signals to permit nodes to
control address and data flow and minimize buffering.
The TLSB operates over a range of 10 to 30 ns clock cycles. This corresponds to a maximum bandwidth of 2.1 Gbytes/sec and a projected minimum latency of 170 ns with a 10 ns clock cycle. Memory latency is reduced
by improving the DRAM access time. Because the address bus and data
bus are separate entities, the slot for passing data on the data bus is variable and directly affected by the DRAM access time. Therefore, any decrease in DRAM access time is reflected in a decrease in memory latency.
The AlphaServer 8400 has nine physical nodes on the TLSB centerplane,
numbered 0–8. CPU and memory modules are restricted to nodes 0–7. I/O
ports are restricted to nodes 4–8. These five nodes are on the back side of
the centerplane. AlphaServer 8200 supports the five backplane nodes
only. I/O modules are restricted to nodes 6, 7, and 8. Node 8 in both models is dedicated to the I/O module and has the special property of both high
and low priority arbitration request lines that are used to guarantee that
memory latency is no worse than 1.7 µs. An I/O port in any other node
uses the standard arbitration scheme, and no maximum latency is specified.
TLSB Bus 2-1
2.1.1 Transactions
2.1.2 Arbitration
A transaction couples a commander node that issues the request and a
slave node that sequences the data bus to transfer data. This rule applies
to all transactions except CSR broadcast space writes. In these transactions, the commander is responsible for sequencing the data bus. CPUs
and I/O nodes are always the commander on memory transactions and can
be either the commander or the slave on CSR transactions. Memory nodes
are slaves in all transactions.
Address bus transactions take place in sequence as determined by the winner of the address bus arbitration. Data bus transactions take place in the
sequence in which the commands appear on the address bus. All nodes internally tag the command with a four-bit sequence number. The number
increments as each command is acknowledged. To return data, the slave
node sequences the bus to start the transfer.
The address bus protocol allows aggressive arbitration where devices can
speculatively arbitrate for the bus and where the winner can no-op out the
command if the bus is not needed. The bus provides eight request lines for
the nodes that permit normal arbitration. Node 8 has high and low arbitration request lines that permit an I/O port to limit maximum read latency.
2.1.3 Cache Coherency Protocol
The TLSB supports a conditional write-update protocol that permits the
use of a write-back cache policy, while providing efficient handling of
shared data across the caches within the system.
2.1.4 Error Handling
The TLSB implements error detection and, where possible, error correction. Transaction retry is permitted as an implementation-specific option.
Four classes of errors are handled:
•Soft errors, hardware corrected, transparent to software (for example,
single-bit ECC errors).
•Soft errors requiring PALcode/software support to correct (for example,
cache tag parity errors, which can be recovered by PALcode copying
the duplicate tag to the main tag).
•Hard errors restricted to the failing transaction (for example, a doublebit error in a memory location in a user’s process. This would result in
the process being aborted and the page being marked as bad). The system can continue operation.
•System fatal hard errors. The system integrity has been compromised
and continued system operation cannot be guaranteed (for example,
bus sequence error). All outstanding transactions are aborted, and the
state of the system is unknown. When a system fatal error occurs, the
bus attempts to reset to a known state to permit machine check handling to save the system state.
2-2 TLSB Bus
Loading...
+ 353 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.