
{
{    MONITOR FAULT HANDLERS - GENERAL:
{
{      For each monitor fault, corresponding to fault_id, a monitor
{      handler must be known to the monitor fault router.
{      router.
{
{      When a monitor fault is "received" by a task, the appropriate
{      fault handler is called by the fault router - current task
{      execution is preempted without regard to ring of execution. A
{      fault handler must be callable upto ring 13. The fault handler
{      is responsible for performing the necessary corrective action.
{      The specifics (structure) of a fault beyond ost$monitor_fault
{      are transparent to the monitor fault mechanism.
{
{      The general form of the interface to a fault handler is the
{      same for all fault identifiers.
{
{
{      EXAMPLE:
{
{   The purpose of this monitor fault is to process faults whose fault
{ identifiers are ppC$xxx, ...
{
{       ppP$handle_fault_xxx (FAULT, SAVE_AREA)
{
{ FAULT: (input) This parameter specifies the received monitor fault.
{
{ SAVE_AREA: (input) This parameter specifies the save area where the
{       fault occured.
{

  PROCEDURE [XREF] ppP$handle_fault_xxx (VAR fault: ost$monitor_fault;
    save_area: ^ost$stack_frame_save_area);

*copyc OST$MONITOR_FAULT
*copyc OST$STACK_FRAME_SAVE_AREA
