Fujitsu Fujitsu SPARC64 V manual Action of asyncdataerror ADE Trap, Conditions that cause ADE trap

Models: Fujitsu SPARC64 V

1 255
Download 255 pages 53.5 Kb
Page 179
Image 179

TABLE P-11ASI_UGESR Bit Description (4 of 4)

Bit

Name

RW Description

5:4 INSTEND

3PRIV

2MUGE_DAE

1MUGE_IAE

0MUGE_IUGE

Other Reserved

RTrapped instruction end-method. Upon a single async_data_error trap without watchdog timeout detection, INSTEND indicates the instruction end- method of the trapped instruction pointed to by TPC as follows:

002: Precise

012: Retryable but not precise

102: Reserved

112: Not retryable

See Section P.4.3 for the instruction end-method for the async_data_error trap. When a watchdog timeout is detected, the instruction end-method is undefined.

RPrivileged mode. Upon a single async_data_error trap, the PRIV field is set as follows:

When the value of PSTATE.PRIV immediately before the single-ADEtrap is unknown because of an uncorrectable error in PSTATE, ASI_UGESR.PRIV is set to 1. Otherwise, the value of PSTATE.PRIV immediately before the single- ADE trap is copied to ASI_UGESR.PRIV.

RMultiple UGEs caused by DAE. Upon a single-ADE,MUGE_DAE is set to 0. Upon a multiple-ADEtrap caused by a DAE, MUGE_DAE is set to 1. Upon a multiple- ADE trap not caused by a DAE, MUGE_DAE is unchanged.

RMultiple UGEs caused by IAE. Upon a single-ADEtrap, MUGE_IAE is set to 0. Upon a multiple-ADEtrap caused by an IAE, MUGE_IAE is set to 1. Upon a multiple-ADEtrap not caused by an IAE, MUGE_IAE is unchanged.

RMultiple UGEs caused by I_UGE. Upon a single-ADEtrap, MUGE_IUGE is set to 0. Upon a multiple-ADEtrap caused by an I_UGE, MUGE_IUGE is set to 1. Upon a multiple-ADEtrap not caused by an I_UGE, MUGE_IUGE is unchanged.

R Always 0.

P.4.2 Action of async_data_error (ADE) Trap

The single-ADEtrap and the multiple-ADEtrap are generated upon the conditions defined in TABLE P-2on page 154. The actions upon their occurrence are defined in more detail in this section. For convenience, the shorthand ADE is used to refer to async_data_error.

1.Conditions that cause ADE trap:

An ADE trap occurs when one of the following conditions is satisfied:

When ASI_ERROR_CONTROL.UGE_HANDLER = 0 and I_UGEs and/or A_UGEs are detected, a single-ADEtrap is generated.

When ASI_ERROR_CONTROL.UGE_HANDLER = 1 and I_UGEs, IAE, and/or DAE are detected, a multiple-ADEtrap is generated.

2.State change, trap target address calculation, and TL manipulation.

168 SPARC JPS1 Implementation Supplement: Fujitsu SPARC64 V • Release 1.0, 1 July 2002

Page 179
Image 179
Fujitsu Fujitsu SPARC64 V manual Action of asyncdataerror ADE Trap, Conditions that cause ADE trap