SOFTWARE CONTROL OF HARDWARE INTERRUPTIONS

Abstract: A computer system that has means for processing (266) interrupt requests that are generated both by hardware interrupt request generators (260..., 265) and by control software (264). A common register array is provided having locations for the general registers and the control registers and having specifically interrupt register locations (261) for storing interrupt requests. The hardware generators (260..., 265) store the interrupt requests into the interrupt register locations (261). Similarly, the control software (264) reads and writes to the interrupt register locations (261) whereby interrupt requests can be generated and terminated in a unified manner under software and hardware control.

Description: SOFTWARE CONTROL OF HARDWARE INTERRUPTIONS CROSS-REFERENCE TO RELATED APPLICATIONS BACKGROUND OF THE INVENTION The present invention relates to the field of computers and particularly to computers having central processing units (CPU's) that operate in accordance with the IBM ESA/390 architecture and particularly to computers that have software control of hardware interruptions. In existing computer systems there are two layers of architectures, the outer and the inner layers. The outer layer is the architectural layer which is defined, for example, in a specification such as the Principles of Operation (POO) for the IBM ESA/390. At this layer, an interruption is an unexpected transfer of control. The inner layer mainly implements the interruptions. Many interruptions for a CPU may exist concurrently. Therefore, the inner layer maintains a list of those interruptions that are pending in a register, so they may be processed in the order defined by the outer architecture. The inner layer must be able to set bits in the interruption register as they arise, and also be able to clear the bits as the interruptions are serviced. Various interruptions can be generated by different modules/functions in a computer system. Different classes of interruptions have been defined at the outer layer in the existing computer systems such as External, I/O, Machine Check, Program, Supervisor Call, and Restart interruptions. An interruption signal/level is used to set an appropriate bit in the interrupt register, related to a specific interruption. Next there is an interrupt mask which only permits the allowed interruptions to be seen by the priority encoder. The priority encoder examines the pending interruptions in order to specify which one has the highest priority and needs to be serviced next. After the interruption is serviced, the appropriate bit in the interrupt register is cleared. Once a bit associated with an interruption is set, Control Software can not reset it. However, the bit can be reset as a part of a CPU Reset or an IPL (Initial Program Loading) operations, or by hardware after the interruption is serviced. ESA/390 architecture computers are controlled in part by a Program Status Word (PSW) . The program-status word (PSW) includes the instruction address, condition code, and other information used to control instruction sequencing and to determine the state of the computer. The active or controlling PSW is called the current PSW. It governs the program currently being executed. The CPU has an interruption capability, which permits the CPU to switch rapidly to another program in response to exception conditions and external stimuli. When an interruption occurs, the CPU places the current PSW in an assigned storage location, called the old-PSW location, for the particular class of interruption. The CPU fetches a new PSW from a second assigned storage location. This new PSW determines the next program to be executed. When it has finished processing the interruption, the interrupting program may reload the old PSW, making it again the current PSW, so that the interrupted program can continue. The status of the CPU can be changed by loading a new PSW or part of a PSW. Control is switched during an interruption of the CPU by storing the current PSW, so as to preserve the status of the CPU, and then loading a new PSW . A new or modified PSW becomes active (that is, the information introduced into the current PSW assumes control over the CPU) when the interruption or the execution of an instruction that changes the PSW is completed. A storage key is associated with each 4K-byte block of storage that is available in the configuration. The storage key has the following format. ACC F R C i i i i i i i i i i 1 1 1 1 1 1 0 4 6 The bit positions in the storage key are allocated as follows: Access-Control Bits (ACC) : If a reference is subject to key-controlled protection, the four access-control bits, bits 0-3, are matched with the four-bit access key when information is stored, or when information is fetched from a location that is protected against fetching. Fetch-Protection Bit (F) : If a reference is subject to key-controlled protection, the fetched protection bit, bit 4, controls whether key-controlled protection applies to fetch-type references are monitored and that fetching with any access key is permitted; a one indicates that key- controlled protection applied to both fetching and storing. No distinction is made between the fetching of instructions and of operands. Reference Bit (R) : The reference bit, bit 5 normally is set to one each time a location in the corresponding storage block is referred to either for storing or for fetching of information. Change bit (C) : The change bit, bit 6, is set to one each time information is stored at a location in the corresponding storage block. Protection Protection facilities are provided to protect the contents of main storage from destruction or misuse by programs that contain errors or are unauthorized. Key- controlledprotectio , access-list-controlledprotection, page protection, and low-address protection are forms of protection available in ESA/390. Key-Controlled Protection When key-controlled protection applies to a storage access, a store is permitted only when the storage key matches the access key associated with the request for storage access; a fetch is permitted when the keys match or when the fetch-protection bit of the storage key is zero. The keys are said to match when the four access- control bits of the storage key are equal to the access key, or when the access key is zero. Fetch-Protection-Override Control Bit 6 of control register 0 is the fetch-protection- override control. When the bit is one, fetch protection is ignored for locations at effective addresses 0-2047. An effective address is the address which exists before any transformation by dynamic address translation or prefixing. However, fetch protection is not ignored if the effective address is subject to dynamic address translation and the private-space control, bit 23, is one in the segment-table designation used in the translation. Fetch protection override has no effect on accesses which are not subject to key-controlled protected. Access-List-Controlled Protection In the access-register mode, bit 6 of the access- list entry, the fetch-only bit, controls which types of operand references are permitted to the address space specified by the access-list entry. When the entry is used in the access-register-translation part of a reference and bit 6 is zero, both fetch-type and store- type references are permitted, and an attempt to store causes a protection exception to be recognized and the execution of the instruction to be suppressed. Page Protection The page-protection facility controls access to virtual storage by using the page-protection bit in each page-table entry. It provides protection against improper storing. One of the instructions that is able to modify part of a PSW is the Set PSW Key From Address (SPKA) instruction. The ESA/390 architecture requires the SPKA instruction to load the architecturally defined PSW "access key" from four bits extracted from the effective address of the SPKA instruction. The access key is used to limit the access of future instructions to certain storage areas to aid in providing protection and privacy of information. In the problem state, the execution of the SPKA instruction is subject to control by the PSW-key mask in control register 3. When the bit in the PSW-key mask corresponding to the PSW-key value is set is one, the SPKA instruction is executed successfully. When the selected bit in the PSW-key mask is zero, a privileged- operation exception is recognized. In the supervisor state, any value for the PSW key is valid. During execution of the SPKA instruction, the Condition Code remains unchanged. The format of the SPKA instruction permits the program to set the PSW key either from the general register designated by the B 2 field or from the D 2 field in the instruction itself. When one program requests another program to access a location designated by the requesting program, the SPKA instruction can be used by the called program to verify that the requesting program is authorized to make this access, provided the storage location of the called program is not protected against fetching. The called program can perform the verification by replacing the PSW key with the requesting-program PSW key before making the access and subsequently restoring the called-program PSW key to its original value. Caution must be exercised, however, in handling any resulting protection exceptions since such exceptions may cause the operation to be terminated. One well-known computer operating with the IBM ESA/390 architecture is the Amdahl 5995-A computer. In that computer, the I-Unit pipeline is a six stage pipeline consisting of stages D, A, T, B, X, and W that process instructions. One of the functions of the D stage is to collate the necessary information to reference storage in the A, T, and B stages. This D-stage function includes the generation of the effective address and selection of the access key to be used by the reference. The A, T, and B stages fetch operands/data using the current valid key that is defined by the architecture, PSW KEY A . One of the functions of the W (write) stage is to write results of operations to architecturally defined registers or storage. The W stage in the pipeline comes after the fetch-operands/data stages (A, T, and B) and the arithmetic functions stage (X) . The access key used is the key, PSW KEY A , from the architecturally defined PSW register. After the access key in the PSW has been updated in the W stage, the new key, PSW N is available for future operations/instructions and the new key becomes the architecturally defined key, PSW KEY A . The ESA/390 architecture requires that the new key be effective starting from the instruction immediately following the SPKA instruction. The new PSW key can be used in a subsequent D segment while being updated in the W segment. The fetching of any instruction following a SPKA instruction is subject to key fetch protections and hence must wait until the SPKA instruction has updated the key in the PSW register. If a storage-reference instruction (an instruction that references storage) immediately follows a SPKA instruction, the fetching of data by that storage- reference instruction must wait until after the SPKA instruction has updated the access key in the PSW register, that is, must wait until the architecturall defined key, PSW KEY A , has been updated with the new value, PSW N from the SPKA instruction. In computer systems, a system control program (SCP) is responsible for resource management and often uses architectural registers. Computer systems under control of the control program operate in User State and in Control State. In User State, user programs and vendor-provided operating systems execute. IBM system control programs (CP's) run in User State. Certain instructions and facilities of User State may be emulated by Control State software. Control State is for -controlling system resources and they may be shared by multiple domains and provide emulation when necessary. Emulation may be used for enhancing the IBM ESA/390 architecture or may be used so that User State programs that run on one manufacturer's machines having one set of hardware may run on another manufacturer's machines with different hardware. Control State operation is based on the IBM ESA/390 architecture. Entry to Control State from User State is vectored, invoked by Control Interceptions that require assistance by Control State software. Transitions from User State to Control State occur under a number of conditions. For example, a transition may occur when an instruction occurs that is defined as an emulated instruction when an instruction occurs for which a specific interception control is set, when an interruption occurs for which a specific interception control is set, when an interruption occurs that is defined as a mandatory Control Interception. The SCP in some environments operates the machine hardware and multiplexes the physical resources of the computing system into multiple logical entities called virtual machines, each of which is a simulation of a computer dedicated to the servicing of a single user or (in the case of a server) a single application. Virtual machines are software entities that can be easily configured to running a particular program rather than to a user. A virtual machine configured in this manner is referred to as a virtual machine server. By virtualizing, operating systems can link guest systems together without the need for guest-specific actual hardware. Also, operating systems allow multiple guest systems to share devices and other resources to simplify configuration and maintenance. Resource management (SCP) and user management (CMS) are separate. When a CMS user logs on to the system, the SCP (system control program) creates a virtual machine for that user that includes, among other things, storage address space. An address space is a sequence of addresses that starts at one address and extends up to a value that varies according to size. Storage management is an important task of the supervisor or host which must create, share, and otherwise manage address spaces, gain and relinquish access to an address spaces, and map data on external devices. Virtual machines running in the ESA/390 architecture have at least one address space, the primary address space, given to the user by the SCP when the user logs on to the system. The size of this address space is determined from the entry describing that user in the user directory, or from a subsequent DEFINE STORAGE command. After logging on, if authorized in the user directory, a user may create other address spaces and share them with other logged-on users. Before a program can actually read or write data in a nonprimary address space, it must invoke an SCP service to add an entry designating that address space to its access list. Each virtual configuration has its own access list having entries that determine which address spaces the virtual CPUs in that configuration can reference at any one time. The number of entries in the access list is controlled by information in the user's directory entry. When a program adds an address space to its access list, SCP selects an unused entry in the access list, fills it in as requested by the program, and returns a four-byte access-list-entry token (ALET) to the program. A program uses this ALET to make direct references to the address space. The access-list entry thus allocated remains allocated until the program explicitly removes the entry, or until the virtual machine goes through a virtual-machine-reset operation. Interpretive-Execution The IBM Interpretive Execution Facility (IEF) allows a computer system running under a host System Control Program (SCP) to interpret a virtual machine called the guest. The term "host" refers to the real machine together with the SCP running on the real machine. The host manages real-machine resources and provide services to the guest programs which execute in an interpreted machine. The interpreted and host machines execute guest and host programs, respectively. For a transfer of control from a guest virtual machine back to its host System Control Program (SCP), an "interception" occurs. In the existing computer architecture, when a guest issues a START INTERPRETIVE EXECUTION (SIE) instruction, the instruction is intercepted and emulated by the host program at a significant performance cost. Through emulation, the host provides the functions of a selected architecture which may be available on some other real machine or which may be available only in the virtual- machine environment. Privileged and problem-program instruction execution, address translation, interruption handling, timing and other functions are interpreted so that those functions are executed in the context of the virtual machine. With the addition of special-purpose hardware, interpreted execution can approach speeds that are comparable to native-mode execution, that is, execution by a non-interpretive version of the architecture. In the virtual-machine environment, the guest program has access to all the functions defined for the designated architecture either through an interpretive- execution facility or by the host system control program. For VM/ESA, the control program CP provides functions through simulation. Simulation generally executes guest functions transparently so that the guest program is unaware as to whether a function is performed by the machine or the host except that simulation usually requires more time. When an SIE instruction is executed, the operand of the SIE instruction containing the State Description is fetched to obtain information about the current state of the guest. When execution of SIE ends, information representing the state of the guest, including the guest program status word (PSW) , is saved in the state description before control is returned to the host. The information in the state description, as used and modified by the host during simulation, allows the guest to start and stop execution with valid information. The state description also determines the mode and other environmental conditions in which the guest is to execute. While in interpretive-execution mode the host, in order to be protected from interference by guests or interference among guests, allocates portions of the real-machine resources to the virtual machine. Guest storage is confined to a portion of host real storage or to host virtual address spaces controlled by the host system. Host enabled and disabled states generally are undisturbed by execution of the guest. A complete and logically separate set of control registers is maintained by the machine for use by the host and another set for each guest is maintained for use by the guest. Other registers are shared between the host and guests. In some cases, the host intercepts operations normally performed by the machine. The state description includes control bits settable by the host to cause intercept operations under specific conditions. When the specific condition are met, the machine returns control to host simulation. Intervention controls capture the introduction of an enabled state into the PSW, so that the host can present an interruption which it holds pending for the guest. Intervention controls may be set asynchronously by the host on another real processor while interpretation proceeds. The machine periodically refetches the controls from storage, so that updated values will be recognized. Guest interruptions can thereby be made pending without prematurely disturbing interpretation. Guest Storage Preferred-storage mode and pageable-storage mode are provided for in the interpretive-execution architecture. In preferred-storage mode, a contiguous block of host absolute storage is assigned to the guest and in pageable-storage mode, dynamic address translation (DAT) at the host level is used to map guest main storage. In preferred-storage mode, the lower addresses of the machine storage are dedicated to the guest and only one guest can obtain production mode performance. In the pageable-storage mode, the host has the ability to scatter the real storage of pageable-storage- mode guests to usable frames anywhere in host real storage by using the host DAT, and to page guest data out to auxiliary storage. This method provides flexibility when allocating real-machine resources while preserving the expected appearance of a contiguous range of absolute storage for the guest. A virtual-machine environment may require DAT twice, once at guest level, to translate a guest virtual address into a guest real address, and then, for a pageable guest, at the host level, to translate the corresponding host virtual address to a host real address. Multiple High-performance Guests The Multiple Domain Facility™ (MDF™) available on Amdahl computers provided concurrent execution of two or more operating systems with high performance on a single shared central computing complex. Such operation permits the reassignment of resources dynamically with minimal performance penalty for a variety of different architectures or systems. In the existing systems, the software and hardware generated interruptions do not go through a consolidated mechanism before they are examined and serviced. Furthermore, there is no integrated set of priorities for the order in which the hardware and software interruptions are serviced. Accordingly, there is a need for an improved computer system having inprovements interruption handling. SUMMARY OF THE INVENTION The present invention is a computer system that has means for processing interrupt requests that are generated both by hardware interrupt request generators and by control software. The computer system has a plurality of architectur¬ ally defined registers including general registers used to store user information and including control registers used for control functions. A common register array is provided having locations for the general registers and the control registers and having specifically interrupt register locations for storing interrupt requests. The hardware generators store the interrupt requests into the interrupt register locations. Similarly, the control software reads and writes to the interrupt register locations whereby interrupt requests can be generated and terminated under software and hardware control. In general the computer system of the present invention has two layers of architectures, the outer and the inner layers. The outer layer is the architectural definition defining interruptions as unexpected transfers of control. The inner layer implements the interruptions. Since many interruptions may exist concurrently, the inner layer maintains a list of those interruptions that are pending in a register, so they may be processed in the order defined by the outer layer architecture. The inner layer sets interrupt requests in the interrupt register as they arise and clears the interrupt requests as the interruptions are processed. Various interruptions can be generated by different modules and functions in a computer system. Different classes of interruptions are defined at the outer layer such as External, I/O, Machine Check, Program, Supervisor Call, and Restart interruptions. An interrupt mask only permits the unmasked interrupt requests to be processed by a priority encoder. The priority encoder examines the pending interrupt requests to determine their priority and the order by which they will be processed. After the interrupt request is processed, the interrupt request in the interrupt register is cleared. In the present invention, the Control Software is logically between the inner and outer layers. The Control Software, which is like the outer layer, is given direct access to the interrupt register that is used by the hardware interrupt mechanism. The Control Software can read the status of the interrupt register and can also set interrupt requests in the register to make the hardware interrupt processor cause interruptions. Thus a unified process is utilized for generation of interruptions by hardware and software. Both can set appropriate bits in the interruption register to signify a pending interruption. Furthermore, a unified set of priorities for interruptions are defined that include both the hardware and software generated interrupt requests. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 depicts an overall block diagram of a computer system incorporating the present invention. FIG's. 2, 3 and 4 depict detailed block diagrams of the FIG. 1 system. FIG's. 5A and 5B depict a block diagram of the I- Fetch data and control circuitry that forms part of the FIG. 1 system. FIG. 6 depicts a detailed block diagram of the register array complex. FIG. 7 depicts a block diagram of a multiple CPU system using multiple CPU's of the FIG. 1 type. FIG. 8 provides a block diagram of the software controlled interrupt unit. DESCRIPTION OF THE PREFERRED EMBODIMENTS Overall Computer System - FIG. 1 In FIG. 1, a computer system compatible with the Amdahl 5995-A computer operating in accordance with the ESA/390 architecture is shown. The computer system of FIG. 1 includes an instruction unit (I-unit) 5, a storage unit (S-Unit) 4, an execution unit (E-Unit) 13, system control units 7, I/O units 9, main store 8, and a service processor 6. The instruction unit 5 includes an operand address unit 11, an instruction data register 10, an I-fetch unit 14, a register array 17, and an I-unit control 3. The storage unit 4 includes an SU Op Pipe 12 and an SU I-Fetch Pipe 15. The FIG. 1 system features two machine states, User State and Control State. In User State, supersets of the IBM ESA/390 architecture are supported. Some User State operations may be emulated by Control State software. The architecture provides support for Control State Software to implement the "Multiple Domain Facility" (MDF) . MDF provides for multiple computing systems to exist in User State on one processor complex. This operation is accomplished by providing each virtual computing system (domain) with its own private main storage, channels, operator console, and optionally expanded storage, while multiplexing all domains on the CPU resources available to the processor complex. A "Domain" is a set of resources such as CPU's, main storage and channels available to a User State control program(CP) . A domain program is a User State program. A domain consists of both domain-native and guest resources. The terms "User", "User State", and "LP (Logical Processor)" also refer to both domain-native and guest resources, although LP usually is used to refer to a domain CPU. A "Guest" is a resource that requires the presence of a supporting 'host' domain control program. A guest program is one that runs in an environment consisting of a specific set of guest resources. When a CPU operates in guest mode (User State or Control State) , domain resources accessed by a program are guest resources (for example, guest PSW) by default. In Control State, access to other resources is under program control which is sometimes called interpretive-execution mode. Domain Mode Control <A> indicates whether a CPU operates in guest mode or not. "Domain-native" is a resource that does not require the presence of a domain control program. A domain-native program is one that runs in an environment consisting of domain-native resources. A CPU is in domain-native mode if it is not in guest mode; in this mode, domain resources accessed by a program are domain-native resources (for example, domain-native PSW) by default. In Control State, access to other resources is under program control. A "Host" is a domain program that supports guest resources. The term "host" is meaningful when discussed in the context of a guest. Host resources may behave differently when the CPU is in guest mode. The term "host mode" may sometimes be used interchangeably with "domain-native" mode. User programs and vendor-provided operating systems run in User State. IBM SCPs run in User State. User State may be in either System/370 or ESA/390 mode. Certain instructions and facilities of User State may be emulated by Control State software. Control State is for controlling system resources and they may be shared by multiple domains and may provide emulation. Emulation is often used for enhancing the IBM ESA/390 architecture or for enabling User State programs that run on one manufacturer's machines to run on another manufacturer's machines. Control State operation is based on the IBM ESA/390 architecture. Entry to Control State from User State is vectored, invoked by Control Interceptions that require assistance by Control State software. Transitions between User State and Control State occur under a number of conditions. For example, transitions occur when an instruction occurs that is defined as an emulated instruction, when an instruction occurs for which a specific interception control is set, when an interruption occurs for which a specific interception control is set, and when an interruption occurs that is defined as a mandatory Control Interception. In the FIG. 1 system, there are two types of units of operation, the domain unit of operation (DUO) and the machine unit of operation (MUO) . In the FIG. 1 system, the System Communication Interface (SYSCOM) provides a means of communication among Control State software and various processing units within a system. These processing units include I/O Processors (IOPs), service processors (SVPs), and CPUs. The means of communication is through passing data in control blocks in the HSA, and informing the recipient via a signaling mechanism. In FIG. 1, the service processor (SVP) 6 is provided to assist in configuration of the system, machine check handling, operator facilities, and other model-dependent functions. The FIG. 1 system includes a facility to permit asynchronous communication between TCMPs using messages. The message processing facility and the instructions to support them are collectively known as the TCMP unification facility (TUF) . TUF is distinguished from a local area network. The TUF assembles large single system images by linking TCMPs. The resulting complexes are used for transaction processing in large enterprises. In the FIG. 1 system, the architectural register sets are defined as follows: access registers (AR) , floating point registers (FR) , general registers (GR) , Control State and domain AR MAP registers (MR) , register array (RA) , and vector registers (VR) . Other individual registers, such as the program status word (PSW), are also defined. Using the GR as an example, the following notation is used to identify subsets of a register set. To specify register x of the set of GRs, the notation GRx is used if x is a number; the notation GR(x) is used if x is a variable (for example, GR(R1) means the general register designated by the Rl operand) . To specify the consecutive bit positions beginning with w and ending with z, the notation <w:z> is used. A string of bits is specified by listing the bits, separated by commas as in <x, w:z, ...>. To specify bit string y of register x of the set of GRs, the notation GRx<y> or GR(x)<y> is used. Bit string y may consist of only 1 bit. To specify bit string y within field F of register x of the set of GRs, the notation GRx.F<y> or GR(x).F<y> is used. Bit string y may consist of only 1 bit. Bit positions given for y are with respect to the field F (for example, DAC.DABR_ctl<0>\&) . In the FIG. 1 system, the various ones of the architectural registers are implemented in a register array. The registers in the register array are set forth in the following TABLE 1. TABLE 1 - CPU Register Array RA NOs. OX Control State General Registers IX Control State Parameters 2X DAC/CI Parameters/Control State VBPA 3X Control State AR MAP Registers 4X Domain-Native General Registers 5X Domain Counters/Domain Parameters 6X Domain Parameters/Domain VBPA 7X Domain AR MAP Registers 8X Domain-Native Control Registers 9X Domain Parameters AX Access Registers BX Access Registers CX Guest Control Registers DX Guest Parameters EX Guest Parameters FX Reserved for Control State Software In FIG. 1, the main Store 8 contains a system storage area where Control State software and the Hardware System Area (HSA) reside, and domain storage area(s), one for each domain. Each storage area is a separate address space, or address dimension, that is, for example, up to 2 GB in size. Mapping of these address spaces to physical main storage is via blocks of storage that are 2 MB or larger. "Expanded Storage". Control State software and domains may each optionally have its own expanded storage. Mapping of Control State or domain expanded storage areas to physical expanded storage is similar to main storage mapping. "Shared Global Storage". The architecture can support a large single system image that is composed of multiple tightly coupled (i.e., shared main memory) multiprocessors (TCMP) . Shared global storage (SGS) permits data to be shared between TCMPs by functionally connecting the SGS to the main storage of each of the TCMPs. A domain in a TCMP can share all or a portion of SGS with a domain in another TCMP. Mapping of domain SGS to physical SGS is similar to the expanded storage and main storage mapping. In the FIG. 1 system, the register array (RA) Complex 17 includes 256 word registers that are under control of Control State instructions. A specific RA register is identified by an 8-bit operand field in these instructions. Defined RA registers have two identifications: the functional name (for example GRO) and their register offset in the register array (for example RA(CO)). In addition to using one of the RA-manipulation instructions, some RA registers can be accessed directly by unique instructions that manipulate the functional registers (for example domain CRs can be loaded using the LCTL instruction) . For such registers, there may be a preference in the means of access. For example, loading the RA copy of the system prefix has no effect on prefixing; the SPX instruction should be used. Note that the RA registers are not necessarily changed by an instruction addressing the register; some (for example the User State Old PSWs) can be changed due to an interruption or CI. The RA contains most architecturally-defined registers and controls, including Control State prefix, domain-native prefix, guest prefix, DAC, feature control bits, general and control registers. The architectural registers that are not in the same physical register array are listed as follows: The Control State PSW is not in the RA. The host PSW to be saved in the interpretive-execution mode is also not maintained in the RA; it is saved in the LPSD. (Note that although the domain-native and guest PSWs are provided in the RA for CSSW to inspect and modify, the instruction-address field (bits 33:63) is invalid). The host GRs 14 and 15 defined to be saved in the interpretive-execution mode are not maintained in the RA; they are saved in the LPSD. (Note that the User State and Control State GRs are in the RA) . There is one set of FRε provided in User State, and they are not contained in the register array. In FIG. 1, main storage 8 contains (1) a system storage area (SSA) where Control State Software (CSS) [both instructions and data] resides and where the Hardware System Area (HSA) resides, and (2) domain storage areas (DSA), one for each domain. Mapping of these address spaces to physical main storage is via blocks of storage that are, for example, 2 MB or larger. A domain's storage area is accessed using domain addresses. In User State, addresses are domain addresses of the current domain. In Control State, CPU generated addresses are generally system addresses. However, under the control of the Domain Access Controls register, some operand effective addresses are treated as domain addresses. In Control State, CSSW can select either User PSW<AS> and PSW<T> to determine the mode of accessing main storage, or it may choose to use another set of three bits to determine the mode of accessing main storage, which can be different from the current one, as specified by the user PSW. Detailed System - FIG's. 2. 3. 4 In FIG's. 2, 3 and 4, further details of the computer system of FIG. 1 are shown with an orientation as depicted in the lower right-hand corner of FIG. 1. The computer system operates in a pipelining fashion where operation is divided into a number of segments including P, A, T, B, R segments and D, A, T, B, X, and W segments. The units of FIG's. 2, 3, and 4 operate generally over the D, A, T, B, X, and W segments after a current instruction is loaded into the IDR register 65. To load an instruction, the P segment performs priority resolution, the A segment performs instruction address presentation, the T segment performs TLB lookup and cache tag matching, and the B segment loads the current instruction into the IDR register 65. In FIG. 2, the I-Unit 5 fetches instructions into the instruction data register (IDR) 65 which are to be processed in a pipeline fashion. Up to six instructions, for example instruction I 17 I 2 , I 3 , I 4 , I s , and I 6 can be processing in the FIG's. 2, 3, and 4 units in the D, A, T, B, X, and W segments. In FIG. 2, the I-fetch unit 14 fetches instructions and stores them into the IDR 65 and delivers them to the storage unit Op Pipe 12 and the storage unit I-fetch pipe 15 to maintain a flow of instructions to be executed. The units of FIG. 2 cooperate with the register array 17 for controlling the flow of instructions and operands in the pipeline execution of the computer system. The I-fetch unit 14 pre-fetches each instruction into the instruction data register IDR 65 so that when the D segment commences, the I-fetch unit 14 has finished for the current instruction, for example instruction I-,, and is pre-fetching subsequent instructions for example instructions I 2 , I 3 , I 4 , I 5 , l e and I 7 . The I-fetch unit 14 during prefetching interacts with the storage unit 4 during the P, A, T, B, R segments that all precede the D, A, T, B, X, and W segments. In FIG. 2 , the IDR 65 provides information to the operand address unit 11. The operand address unit 11 determines addresses information to be processed by instructions. The addresses of operands are passed to the storage unit of operand pipe 12 which fetches the operands which are to be operated upon and delivers them to the execution unit 13. The execution unit 13 performs arithmetic and logical functions on the operands such as add, multiply, divide, move, or, and shift. After prefetching, the D segment is the decode cycle for instruction decoding of the instruction in IDR register 65. The A segment is address presentation for the S- unit 4. The T segment is a translation TLB lookup and cache tag match cycle. The TLB is a translation look¬ aside buffer. The B segment is the buffer cycle when, if a correct translation occurred in the TLB and if the line of data addressed is in the cache, the data is accessed and latched into the operand word register OWR (46, 49, 52) . The X segment is for execution in the E-Unit 13 which takes data from the OWR, executes on the data and places the result in the result register (48, 51, 54). The W segment is for writing the results to the location specified by the instruction, for example, to an internal register in register array 17 or back to main storage 8. Referring to FIG.'s 2, 3, and 4 the instruction buffer register 65 is loaded by the I-fetch unit 14. The instruction buffer register 10 in turn loads the IDR register 65 in four fields, Dl, D2, D3 and D4. The contents of the register 65 are selected to read the system or user general purpose registers 66 (GPR's) . The contents of the general purpose registers are selected into the three-input adder 89. After the SPKA instruction is latched into the IDR 65, the data address in the DAR register 68, valid in the D segment, is staged through the address registers in the A, T, B, X and W segments using the registers DAR 68, AAR 75, TAR 81, BAR 43, XAR 44, and WAR 45, respectively. In one alternate embodiment, the registers AAR 75, TAR 81, BAR 43 are eliminated and the equivalent information is obtained from other registers. Conceptually, however, these registers still exist even in the alternate embodiment. Following the ESA/390 architecture, an operand storage address consists of three components, a base, an index and a displacement. The base, index and displacement values from GPR' s 66 are added in adder 89 to form the effective address which is latched into the ARSLT and/or AEAR registers 73 and 71. The adder 89 forms the effective address and it is placed into the AEAR effective address register 71 and into the ARSLT result register 73. The contents of the effective address register 71 are present in the A segment and are used, among other things, as part of the access to the storage unit Op pipe 12 to obtain an operand from the storage unit. The contents are also stored into the T operand address registers 1 and 2, T0AR1 79 and T0AR2 80 in the T segment. The contents of one of the registers 79 or 80 are passed to the B segment operand address registers, BOAR 87. The storage unit Op pipe 12 includes a register 90 which is loaded with the PSW Key which is to be used for key protection checking when the storage unit is accessed. The key from the register 90 is compared in comparator 91 with a key from the OP TLB unit 84 to determine if a key match exits. The other portions of the TLB including the OP tags 85 and OP buffer 86 are also compared in comparator 92 to generate a TLB MATCH signal. If the key match from comparator 91 is not asserted, meaning that the key from register 91 does not match the key from the TLB unit, then the TLB match signal is not asserted meaning that a protection key violation has ' occurred. If the keys do match and all the other required matches are also present, the TLB match signal is asserted indicating that, among other things, no key protection violation has occurred. If the instruction being processed is a SPKA instruction, for example, then the processing during the X segment will cause a new PSW including a new PSW Key N to be stored through the RR result registers 48, 51 and 54 to the register array complex 17. The PSW will be loaded directly into the register array 56 and also will be stored into the PSW Key shadow register 95. The PSW register 95 holds a duplicate copy of PSW Key stored in the register array 56. Once the D-cycle of a SPKA instruction is complete, the effective address latched in the AEAR register 71 will be moved down the pipeline to provide a new PSW N in the W segment provided nothing prevents the new PSW N from being written. Instruction Fetch Platform - FIG. 5 In FIG. 5, further details of the I-Fetch Unit 14 of FIG. 1 are shown. In FIG. 5, the IDR Register 65 of FIG. 2 is expanded and is shown together with the circuitry for loading the IDR 65 with a sequence of instructions such as shown in TABLE A above. In FIG. 5, the IDR 65 is loaded from the storage unit cache 200 or the FDR's 201. Selection of instructions into the FDR's 201 is under control of the selector 202 which in turn is controlled by the FDR control 221. Selection of instructions from the cache 200 or the FDR's 201 is under control of the selection gates 204 and 205 which in turn are controlled by the IFCDB control 222. Selection of instructions from the FDR's 201 is under control of the selection gate 203 which in turn is controlled by the FDR control 221. Selection gate 206 controls selection of the selected output of selector 205 into the IB1 buffer register 210. Selector 206 is under the control of the IB1 control 223. The selection from the buffer register IB1 or from the selector 205 is under control of the selector 207 which in turn is controlled by the IB0 control 224. The selected instruction selected by selector 207 is latched in the buffer register IB0 211. Selection of the contents of the IB0 register 211 by selector 208 is under control of the HW select control 227 and selector 208 in turn feeds the selector 213 which is under control of the IFDB control 228. The output from selector 213 or from the cache through selector 204 is under control of selector 214 which in turn is controlled by the IDR select control 229. The selected instruction from selector 214 is input to the IDR 65 which is staged through the IDR 65 stages IDR, AIDR, TIDR, BIDR, XIDR, WIDR, and ZIDR labeled 65-1, 65-2, 65-3, 65-4, 65-5, 65- 6 and 65-7, respectively. The output form the ZIDR stage of the IDR 65 is selected by the selectors 237 and 238 is the DBUS of the Op Address Unit of FIG. 2. In FIG. 5, a decoder 270 decodes the instruction length count, ILC, from the instruction in the D-segment instruction data register (IDR) . The ILC is latched into the AILC register 271 and staged to the TILCR register 272 for the T-segment. The T-segment ILC, TILC, is added in adder 273 to the contents of the BNSIAR register 275 to form the next sequential instruction address (NSIA) which is stored back into the BNSIAR register 275. When a branch or other condition (BR) indicates that the next instruction in the sequence determined by adding the ILC to the current instruction is not the next instruction, the BNSIAR is loaded directly from the BOAR 87 of FIG. 2 under control of selector 274. The B-segment next sequential instruction address, BNSIA, is determined one instruction flow ahead of the current instruction in the pipeline. The BNSIA in the BNSIAR is a predicted value based on instruction length count. In FIG. 5, control of the selection of which instructions to feed into the IDR register 65 is under the selection controls 221 through 229 in control unit 242. These controls receive status information from status unit 245 which is loaded by the S-unit Fetch Status 244. Status unit 245 also provides status to the IFETCH state machine 243. The S-unit Fetch Status 244 loads the FDR status 231, IB1 status 232, IBO status 233, IDR status 234, EXDR status 235 and the BUBBLE UP STATUS 236 in the status unit 245. The different status and control conditions and related circuits for a main frame computer are extensive, and many of the details related thereto are not relevant to the present invention, but such details can be found, for example, in the Amdahl 5995-A computers. The particular control and status conditions which are relevant for selecting instructions in connection with the present invention will be described in detail hereinafter. Register Array Complex - FIG. 6 In FIG. 6, further details of the register array complex 17 of FIG. 1 are shown. In FIG. 6, the ram complex 281 is like that shown in the above-identified cross-referenced application entitled MEMORY HAVING CONCURRENT READ AND WRITING FROM DIFFERENT ADDRESSES. The PSW register uses the same data in lines DI_H and DI_L which are the RRH and RRL lines, RRout, from the result register. Similarly, the read address lines RA_1 and RA_2, the write address lines WRA, the even and odd write strobes WR_EVE and WR_ODD, and the control lines CTRL are as shown in the cross-referenced application. The selectors 282 and 283 are like the selectors 24 and 25 in FIG. 3 of the cross-referenced application with the addition of the PSW inputs. The RAM complex 17 can concurrently read and write to different addresses. As described in detail in the cross-referenced application, the RAM complex includes two RAMs, each having an address selector. The RAM complex includes a data out multiplexer for selecting outputs from one of the RAM's. The RAM complex includes a tag array storing an array of tag bits, one for each address in the RAM's. The tag bits are used to control the address selectors and multiplexer. A single bit tag is provided in the tag array for each entry in the RAM's. The tag marks which one of the two RAM's has the valid data for the corresponding specific address tag. During a RAM read cycle, the tag routes the read address through the address selector for the correct one of the RAM's. The correct RAM is read using the read address and a staged copy of the tag controls the data out selector to select data from the correct RAM for the data out bus. During a concurrent read and write cycle, the tag selects the read addresses for one RAM and selects the write address for the other RAM. A write enable signal, is provided for the write RAM. The tag for the write address is then updated in the tag array to point to the write RAM. With the ability to read and write concurrently to different addresses, enhanced performance results by using only a single operation to concurrently read and write to the ♦ same address in the RAM complex. Multiple CPU System - FIG. 7 In FIG. 7, a multiple CPU embodiment of the FIG. 1 system is shown. The FIG. 7 system includes a service processor 6, I/O Unit 9, a main store 8, system control unit 7 and a plurality of CPU's including CPU(O), ..., CPU(n-l) . Each of the CPU's includes a register array including the register arrays RA(0), ..., RA(n-l) . The .register arrays in each of the CPU's of FIG. 7 are like the register array complex 17 of FIG. 1 and of FIG. 6. Each register array RA(0), ..., RA(n-l) in the CPU's of FIG. 7 includes 256 word registers that are under control of Control State instructions. A specific RA register is identified by an 8-bit operand field in these instructions. Defined RA registers have two identifications: the functional name (for example GRO) and their register offset in the register array (for example RA(CO)). In addition to using one of the RA- anipulation instructions, some RA registers can be accessed directly by unique instructions that manipulate the functional registers (for example domain CRs can be loaded using the LCTL instruction). For such registers, there may be a preference in the means of access. For example, loading the RA copy of the system prefix has no effect on prefixing; the SPX instruction should be used. Note that the RA registers are not necessarily changed by an instruction addressing the register; some (for example the User State Old PSWs) can be changed due to an interruption or Control Interception (CI). Each RA contains architecturally-defined registers and controls, including Control State prefix, domain-native prefix, guest prefix, DAC, feature control bits, general and control registers . The Control State PSW is store in the PSW register in the RA complex as described in connection with FIG. 6. The host PSW to be saved in the interpretive-execution mode is saved in the storage data block (SDB) of main store 8. The host GRs 14 and 15 defined to be saved in the interpretive-execution mode are also saved in the SDB. The User State and Control State GRs are in the RA's. In main storage 8, the system storage area (SSA) stores the Control State Software (CSS) [both instructions and data] and the Hardware System Area (HSA), and (2) domain storage areas (DSA) , one for each domain. Mapping of these address spaces to physical main storage is via blocks of storage and a domain's storage area is accessed using domain addresses. In User State, addresses are domain addresses of the current domain. In Control State, CPU generated addresses are generally system addresses. However, under the control of the Domain Access Controls register, some operand effective addresses are treated as domain addresses. In Control State, CSSW can select either User PSW<AS> and PSW<T> to determine the mode of accessing main storage, or it may choose to use another set of three bits to determine the mode of accessing main storage, which can be different from the current one, as specified by the user PSW. Interrupt Unit - FIG. 8 In FIG. 8, the interrupts are generated in the machine of FIG. 1 with different classes 1, 2, ... , n as represented by interrupt generators 260, ..., 265. The interrupt generators 260, ..., 265 are the conventional hardware interrupt generators of the FIG. 1 system. The interrupts are stored into the interrupt registers 261 and are output through the interrupt mask 261 to the interrupt priority encoder 263 which enables the interrupt processor 266. The interrupt processor 266 is the conventional hardware in the FIG. 1 system for processing interrupts. In FIG. 8, the control software 264 is able to write directly into the interrupt register 261 thus enabling both the hardware interrupt requests from generators 260, ..., 265 and software generated interrupts from control software 264 to be handled in a common, unified manner. Examples of the operation of the FIG. 8 unit and the FIG. 1 system are given in the following TABLE 2. TABLE 2 Control State User State Receive request for Interrupt Key interruption (rupt) Check User State masks If enabled, perform software simulation of rupt Return to User If disabled in PSW, set up mon¬ itoring of PSW If disabled in CR, set up moni¬ toring of CR Return to User State Execute Enable for rupt < Verify enable state of User If enabled, perform software simulation of rupt Return to User Receive Request for Interrupt Key Set DPIR bit in RA Return to User Execute Enable for rupt Hardware deliver rupt In TABLE 2, various operations are performed by control state software using the register array complex 17 of FIG. 1 which is directly accessable by control state software 264. One particular register in array complex 17 used in the Control State by control state software is, by way of example, the Domain Pending Interruption Register (DPIR) which is register 58 in the TABLE 1 register complex array. The Domain Pending Interruption Register (DPIR) enables control state software (CSSW) to manipulate and monitor User State PER, Address Compare, and certain external and repressible machine check interruption conditions. The DPIR register stored by an RA instruc¬ tion indicates whether any of the associated domain interruptions is pending. An RA instruction that loads a DPIR bit with 0 effectively clears the associated pending interruption. An RA-instruction that loads a DPIR bit with one effectively creates the associated pending interruption. In User State, certain CPU-specific interruption conditions (External, I/O, and Repressible Machine Check DPIR Controls) are defined to be pending for the logical processor (LP) when the bit in the DPIR associated with the condition is 1. When the LP becomes enabled for such interruptions, as defined in the IBM ESA/390 architec¬ ture, the interruption occurs and the associated DPIR bit is set to 0. These DPIR bits are set either by the CPU upon detection of the associated event, or by CSSW in Control State. The following DPIR bits are set only by CSSW: MA, IK, TS, TF, ED, TD, SV, VF. The IT bit may be set by CSSW and is always set by the CPU in System/370 User State when an interval timer interruption condition is recognized. In User State, if the LP is enabled for the associated event, an interruption will occur and the DPIR bit is set to 0. The DPIR PI bit is provided as a read-only summary of any MP synchronization conditions or any pending store PER, external, I/O, repressible machine check or stop interruption conditions that exist for the LP. It may be read by CSSW and will accurately reflect whether (PI = 1) or not (PI = 0) there are any MP synchronization conditions or any pending store PER, external, I/O or Repressible Machine check or stop interruptions for the LP. This includes both Control State and User State pending interruptions. Control State interruptions that are indicated by the PI bit have been conditioned by the appropriate USSIM bit. Setting the bit with an RA instruction has no effect on LP operations. The DPIR<PI> bit is used to monitor inter¬ ruptions that become pending during the emulation of an interruptible instruction. The PI bit reflects the interruption status at the time that it is stored. A conceptually prior interruption condition, caused by a preceding instruction, such as setting the CPU Timer with a negative value, may or may not be indicated by the PI bit. While the invention has been particularly shown and described with reference to preferred embodiments thereof it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.

Claims: CLAIMS 1. A computer system including means for process¬ ing interrupt requests, hardware means for generating interrupt requests, interrupt register means for storing interrupt requests, control software for reading and writing to said interrupt register means whereby interrupt requests can be generated and terminated under software control. 2. A computer system that has means for processing interrupt requests, has a plurality of architecturally defined registers including general registers used to store user information and including control registers used for control functions, said computer system includ¬ ing, a common register array having locations for said general registers and said control registers and having interrupt register means for storing interrupt requests, hardware means for generating interrupt requests for storage in said interrupt register means, control software for reading and writing to said interrupt register means whereby interrupt requests can be generated and terminated under software control. 3. The computer system of Claim 2 wherein said hardware means for generating interrupt requests includes means for generating interrupt requests of a plurality of classes. 4. The computer system of Claim 2 wherein said computer system includes mask means for masking interrupt requests in said interrupt register means whereby interrupt requests from said hardware means and interrupt requests from said control software are mask by said mask means. 5. The computer system of Claim 4 including an interrupt priority encoder for encoding in common interrupt requests from said hardware means and interrupt requests from said control software.

Inventors: CONNELL JEFFERSON JOSEPH, JOHNSON VERNON R, LIPMAN PETER H, MAIER ROBERT MARTIN, CONNELL, JEFFERSON, JOSEPH, JOHNSON, VERNON, R., LIPMAN, PETER, H., MAIER, ROBERT, MARTIN
Applicants: AMDAHL CORP, AMDAHL CORPORATION
Application year: 1992
Main classification: G06F13
IPC codes: G06F13