Sable CPU Module Specification

Sable CPU Module Specification Sable CPU Module Specification

people.freebsd.org
from people.freebsd.org More from this publisher
20.02.2013 Views

Copyright © 1993 Digital Equipment Corporation. • BC_TAG holds results of external cache tag probe if external cache was enabled for this transaction C.8.1.2 BIU: tag address parity error • recognized at end of tag probe sequence • lookup uses predicted parity so transaction misses the external cache • BC_TAG holds results of external cache tag probe • machine check if enabled by ABOX_CTL[MCHK_EN] • BIU_STAT: BC_TPERR set • BIU_ADDR holds address C.8.1.3 BIU: tag control parity error • recognized at end of tag probe sequence • transaction forced to miss external cache • BC_TAG holds results of external cache tag probe • machine check if enabled by ABOX_CTL[MCHK_EN] • BIU_STAT: BC_TCPERR set • BIU_ADDR holds address C.8.1.4 BIU: system transaction terminated with CACK_HERR • machine check if enabled by ABOX_CTL[MCHK_EN] • BIU_STAT: BIU_HERR set, BIU_CMD holds cReq_h[2..0] • BIU_ADDR holds address C.8.2 Response to Multiple Errors This section describes the 21064’s response to multiple hardware errors, that is, to errors which occur after an initial error and before execution of the PALcode exception handler associated with that initial error. The 21064 error reporting hardware consists of two sets of independent error reporting registers. • BIU_STAT[7..0] and BIU_ADDR contain information about the following hardware errors: • Correctable or uncorrectable errors reported with CAck_h[2..0] by system components • Tag probe parity errors in the tag address or tag control fields • BIU_STAT[14..8], FILL_ADDR and FILL_SYNDROME contain error information about data fill errors. Cobra Specific ( Privileged Architecture Library Code ) PALcode 241

Copyright © 1993 Digital Equipment Corporation. The BC_TAG register contains information which can relate to any of the error conditions listed above. Each of the above two sets of error registers can contain information about either corrected or uncorrected hardware errors. When a hardware error occurs information about that error is loaded into the appropriate set of error registers and those registers are locked against further updates until PALcode explicitly unlocks them. If a second error occurs between the time that an initial error occurs and the time that software unlocks the associated error reporting registers, information about the second is lost. When the 21064 recognizes the second error it still posts the required corrected read interrupt or machine check, however it does not overwrite information previously locked in an error reporting register. If the second hardware error is not correctable and the error reporting register normally associated with this second error is already locked, the 21064 will set a bit to indicate that information about an uncorrecable hardware error was lost. Each set of error reporitng registers has a bit to report these fatal errors. For example, BIU_STAT[FATAL1] is set by hardware to indicate that a tag probe parity error or HARD_ERROR terminated external transaction occurred while BIU_ STAT[6..0], BIU_ADDR and BC_TAG were already locked due to some previous error. Similarly, BIU_STAT[FATAL2] is set by hardware to indicate that a primary cache fill received either a parity or single or dobule bit EDC error while BIU_STAT[13..8], FILL_ADDR, FILL_SYNDROME, and BC_TAG were already locked. 242 Cobra Specific ( Privileged Architecture Library Code ) PALcode

Copyright © 1993 Digital Equipment Corporation.<br />

The BC_TAG register contains information which can relate to any of the error conditions<br />

listed above.<br />

Each of the above two sets of error registers can contain information about either<br />

corrected or uncorrected hardware errors. When a hardware error occurs information<br />

about that error is loaded into the appropriate set of error registers and those<br />

registers are locked against further updates until PALcode explicitly unlocks them.<br />

If a second error occurs between the time that an initial error occurs and the time<br />

that software unlocks the associated error reporting registers, information about the<br />

second is lost.<br />

When the 21064 recognizes the second error it still posts the required corrected read<br />

interrupt or machine check, however it does not overwrite information previously<br />

locked in an error reporting register. If the second hardware error is not correctable<br />

and the error reporting register normally associated with this second error is already<br />

locked, the 21064 will set a bit to indicate that information about an uncorrecable<br />

hardware error was lost. Each set of error reporitng registers has a bit to report<br />

these fatal errors.<br />

For example, BIU_STAT[FATAL1] is set by hardware to indicate that a tag probe<br />

parity error or HARD_ERROR terminated external transaction occurred while BIU_<br />

STAT[6..0], BIU_ADDR and BC_TAG were already locked due to some previous error.<br />

Similarly, BIU_STAT[FATAL2] is set by hardware to indicate that a primary cache<br />

fill received either a parity or single or dobule bit EDC error while BIU_STAT[13..8],<br />

FILL_ADDR, FILL_SYNDROME, and BC_TAG were already locked.<br />

242 Cobra Specific ( Privileged Architecture Library Code ) PALcode

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

Saved successfully!

Ooh no, something went wrong!