Invalidating storage, clearing buffer entries

This invention relates, in general, to processing within a computing environment, and in particular, to one or more of invalidating storage, clearing buffer entries and an instruction therefor.

Existing computing environments use virtual storage which is normally maintained in auxiliary storage to increase the size of available storage. When a page of virtual storage is referenced, the virtual address used in referencing the page is translated by dynamic address translation to a real storage address. If the translation is successful, then the virtual storage is valid; otherwise, it is invalid. A page of virtual storage is indicated as valid or invalid by an invalid bit in a page table entry, which entry includes a real storage address if the page is valid.

Pages of storage can be invalidated a page at a time. For instance, in a computing environment based on the z/Architecture, offered by International Business Machines Corporation, an instruction, referred to as an Invalidate Page Table Entry (IPTE) instruction, is used to invalidate a page of storage. Invalidation includes setting an invalid indicator in a control structure, associated with virtual storage and located in physical main storage, to indicate that a virtual address of a location in the virtual storage cannot be translated by dynamic address translation to a physical main storage address, also called a real address. Further, the instruction is used to clear internal machine buffer entries associated with the page, which entries may be used during dynamic address translation to avoid accessing the control structures in physical main storage. For instance, in the z/Architecture, there are Translation Lookaside Buffers used during dynamic address translation of virtual addresses to real addresses. When a page of storage is invalidated, the corresponding buffers are also cleared of entries associated with that page.

There are also instructions that enable the purging of entire Translation Lookaside Buffers. For instance, in the z/Architecture, an instruction, referred to as a Compare and Swap and Purge (CSP) instruction, purges all entries of Translation Lookaside Buffers.

<patcit id="pcit0001" dnum="US5946717A"><text>US-A-5946717</text></patcit> (Uchibori Katsuaki) 31 August 1999, and "Enterprise Systems Architecture/390 Principles of Operation" SA22-7201-07, [Online] 31 July 2001, XP002294122, retrieved from the Internet on 2004-08-24, URL: http://publibz.boulder.ibm.com/epubs/p df/dz9ar007.pdf&gt;, describe computing environments which implement invalidation of table entries and clearing of buffers.

Thus, although there are instructions to invalidate a page of storage and clear buffers of entries associated with that page, and instructions to clear entire buffers, there still exists a need for instructions that can selectively invalidate various sizes of units of storage and/or clear buffers of entries associated therewith. For example, a need exists for an instruction that enables the specification of a selected unit of storage greater than a page to be invalidated and/or have buffer entries associated therewith cleared. A further need exists for an instruction that enables the clearing of buffer entries for selected units of storage, without affecting buffer entries for other units of storage.

The present invention provides a method of invalidating storage of a computing environment as claimed in claim 1.

Preferably, the present invention provides a method of invalidating storage of a computing environment is provided. The method includes, for instance, specifying a unit of storage to be invalidated, the unit of storage including a plurality of pages of storage, and wherein the specifying includes providing a descriptor of the unit of storage; and invalidating the unit of storage.

Preferably, the present invention provides a method of facilitating the clearing of buffers of a computing environment is provided. The method includes, for instance, identifying a unit of storage for which clearing of one or more entries of one or more buffers is to be performed, wherein the unit of storage includes a plurality of pages of storage; and clearing one or more entries of the one or more buffers associated with the identified unit of storage, wherein one or more entries associated with another unit of storage are not cleared.

Preferably, an instruction to be executed within a computing environment is provided. The instruction includes, for instance, an operation code to identify an instruction to be executed; an invalidation designation to specify information associated with a unit of storage to be invalidated, the unit of storage including a plurality of pages of storage; another designation to specify additional information for use by the instruction; and a clearing designation to specify information associated with one of the unit of storage and another unit of storage for which one or more entries of one or more buffers are to be cleared, wherein one or more components of one or more of the invalidation designation, the another designation and the clearing designation are configurable as no-operations.

Preferably, an instruction to be executed within a computing environment is provided. The instruction includes, for instance, an operation code to identify an instruction to be executed; and at least one of the following: a first invalidation designation to specify information associated with a unit of storage to be invalidated, the unit of storage including a plurality of pages of storage; a second invalidation designation to specify additional information associated with the unit of storage to be invalidated; and a clearing designation to specify information associated with one of the unit of storage and another unit of storage for which one or more entries of one or more buffers are to be cleared, wherein the information specified by the clearing designation is not associated with at least one other unit of storage for which one or more entries are not to be cleared.

System and computer program products corresponding to the above-summarized methods are also described and claimed herein.

Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention.

The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which: <ul id="ul0001" list-style="none" compact="compact"><li>FIG. 1 depicts one embodiment of a computing environment incorporating and using one or more aspects of the present invention;</li><li>FIG. 2 depicts one embodiment of further details associated with a controller of FIG. 1, in accordance with an aspect of the present invention;</li><li>FIG. 3 depicts one embodiment of a host computer that can emulate another computer, in accordance with an aspect of the present invention;</li><li>FIG. 4 depicts one embodiment of the logic associated with invalidating storage, in accordance with an aspect of the present invention;</li><li>FIG. 5 depicts one embodiment of the logic associated with clearing buffer entries, in accordance with an aspect of the present invention;</li><li>FIG. 6a depicts one embodiment of a format of an Invalidate Dynamic Address Translation Table Entry (IDTE) instruction, in accordance with an aspect of the present invention;</li><li>FIG. 6b depicts one embodiment of the fields associated with general register R1 of the IDTE instruction of FIG. 6a, in accordance with an aspect of the present invention;</li><li>FIG. 6c depicts one embodiment of the fields associated with general register R2 of the IDTE instruction of FIG. 6a, in accordance with an aspect of the present invention;</li><li>FIG. 6d depicts one embodiment of the fields associated with general register R3 of the IDTE instruction of FIG. 6a, in accordance with an aspect of the present invention;</li><li>FIGs. 7a-7b depict one embodiment of the logic associated with the IDTE instruction, in accordance with an aspect of the present invention;</li><li>FIG. 8a depicts one embodiment of the fields of general register R1 being used for an alternative operation of the IDTE instruction, in accordance with an aspect of the present invention;</li><li>FIG. 8b depicts one embodiment of the fields of general register R2 being used for an alternative operation of the IDTE instruction, in accordance with an aspect of the present invention;</li><li>FIG. 8c depicts one embodiment of the fields of general register R3 being used for an alternative operation of the IDTE instruction, in accordance with an aspect of the present invention; and</li><li>FIG. 9 depicts one embodiment of the logic associated with the alternative operation of the IDTE instruction, in accordance with an aspect of the present invention.</li></ul>

In accordance with an aspect of the present invention, a specified portion of storage (e.g., virtual storage) is invalidated. As examples, a segment of storage, which includes a plurality of pages of storage, or a region of storage, which includes a plurality of segments of storage, is selected to be invalidated. The invalidation is facilitated by the setting of invalidation indicators located in data structure entries corresponding to the units of storage to be invalidated. In a further aspect of the present invention, buffer entries (e.g., Translation Lookaside Buffer entries) associated with the storage being invalidated, or other storage, are cleared. Yet further, in another aspect of the present invention, buffer entries associated with selected address spaces are cleared from buffers without affecting buffer entries of non-selected address spaces, and without performing invalidation. In one example, an instruction, referred to herein as an Invalidate Dynamic Address Translation (DAT) Table Entry (IDTE) instruction, from the IBM® z/Architecture is used to perform one or more of the above operations.

One embodiment of a computing environment 100 incorporating and using one or more aspects of the present invention is described with reference to FIG. 1. Computing environment 100 is based, for instance, on the z/Architecture offered by International Business Machines Corporation, Armonk, New York. The z/Architecture is described in an IBM® publication entitled, "z/Architecture Principles of Operation," IBM Publication No. SA22-7832-00, December 2000, (IBM^® is a registered trademark of International Business Machines Corporation, Armonk, New York, U.S.A. Other names used herein may be registered trademarks, trademarks or product names of International Business Machines Corporation or other companies.) In one example, a computing environment based on the z/Architecture includes an eServer zSeries, offered by International Business Machines Corporation, Armonk, New York.

As one example, computing environment 100 includes a central processor complex (CPC) 102 coupled to a controller 120. Central processor complex 102 includes, for instance, one or more partitions 104 (e.g., logical partitions LP1-LPn), one or more central processors 106 (e.g., CP1-CPm), and a hypervisor 108 (e.g., a logical partition manager), each of which is described below.

Each logical partition 104 is capable of functioning as a separate system. That is, each logical partition can be independently reset, initially loaded with an operating system, if desired, and operate with different programs. An operating system or application program running in a logical partition appears to have access to a full and complete system, but in reality, only a portion of it is available. A combination of hardware and Licensed Internal Code (commonly referred to as microcode) keeps a program in a logical partition from interfering with a program in a different logical partition. This allows several different logical partitions to operate on a single or multiple physical processors in a time sliced manner. In this particular example, each logical partition has a resident operating system 110, which may differ for one or more logical partitions. In one embodiment, operating system 110 is the z/OS operating system, offered by International Business Machines Corporation, Armonk, New York.

Central processors 106 are physical processor resources that are allocated to the logical partitions. For instance, a logical partition 104 includes one or more logical processors, each of which represents all or a share of a physical processor resource 106 allocated to the partition. The logical processors of a particular partition 104 may be either dedicated to the partition, so that the underlying processor resource is reserved for that partition; or shared with another partition, so that the underlying processor resource is potentially available to another partition.

Logical partitions 104 are managed by hypervisor 108 implemented by microcode running on processors 106. Logical partitions 104 and hypervisor 108 each comprise one or more programs residing in respective portions of central storage associated with the central processors. One example of hypervisor 108 is the Processor Resource/Systems Manager (PR/SM), offered by International Business Machines Corporation, Armonk, New York.

Controller 120, which is coupled to the central processor complex, includes centralized logic responsible for arbitrating between different processors issuing requests. For instance, when controller 120 receives a request, it determines that the requester is the master processor for that request and that the other processors are slave processors; it broadcasts messages; and otherwise, handles requests. One example of a controller is described in <patcit id="pcit0002" dnum="US6199219B"><text>U.S. Patent No. 6,199,219</text></patcit>. Further details are also described with reference to FIG. 2. FIG. 2 depicts one example of a controller 200 coupled to a plurality of central processors (CPUs) 201. In this example, two central processors are depicted. However, it will be understood that more than two processors may be coupled to controller 200.

Controller 200 includes various controls including, for instance, system serialization controls 202. The system serialization controls are used to ensure that operations that are to be serialized, such as invalidate instructions, are serialized, in that only one such instruction is in progress at one time in the computing environment. It also monitors the sequence of events for that operation.

Controller 200 is coupled to each central processor via various interfaces. For instance, an interface 204 is used by the Licensed Internal Code in a central processor to send "control" commands to the controller, which specify an action to be taken, and to send "sense" commands, which return information from the controller. Another interface is a response bus 206, which is used to return information from the controller for the "sense" commands. The response bus is also used to communicate command status for "control" commands, and may be set from a plurality of sources within the controller, including the system serialization controls. A central processor can use this interface to sense the state of the system serialization controls in controller 200.

A further interface is interface 208, which is used by the controller to send commands to each CPU. This may also be controlled from a plurality of sources within the controller, including system serialization controls 202. A yet further interface is interface 210, which provides signals to cache controls 212 of central processor 201. Cache controls 212 process commands, in response to the signals. In one example, cache controls 212 process commands that affect one or more buffers, such as Translation Lookaside Buffers (TLBs) 213, as described in further detail below.

In addition to cache controls 212, central processor 201 includes various other controls, including, for instance, interrupt controls 220 and execution controls 222. In response to particular events, interrupt controls 220 cause an internal interruption to be pending in the CPU, which in turn, causes execution controls 222 to suspend program instruction processing, at the next interruptible point. In response to the interruption, execution controls 222 invokes a Licensed Internal Code routine to set a broadcast operation allowed latch 224 to enable cache controls 212 to process pending commands.

Central processor 201 also includes a CPU quiesced latch 226 that indicates whether or not the central processor is quiesced.

The above described computing environment is only one example. For example, one or more partitions can be running in different architecture modes. Further, as another example, the environment need not be based on the z/Architecture, but instead, can be based on other architectures offered by Intel, Sun Microsystems, as well as others. Moreover, an environment may include an emulator (e.g., software or other emulation mechanisms), in which a particular architecture or subset thereof is emulated. In such an environment, one or more emulation functions of the emulator can implement one or more aspects of the present invention, even though a computer executing the emulator may have a different architecture than the capabilities being emulated. As one example, in emulation mode, the specific instruction or operation being emulated is decoded, and an appropriate emulation function is built to implement the individual instruction or operation.

Further details of an emulation environment are described with reference to FIG. 3. As one example, a host computer 300 is capable of emulating another architecture, computer and/or processing capabilities of another computer. For instance, host computer 300 is based on an Intel architecture; a RISC architecture, such as PowerPC; a SPARC architecture, offered by Sun Microsystems; or another architecture, and is capable of emulating the z/Architecture of IBM® or another architecture of IBM® or another entity.

Host computer 300 includes, for instance, a memory 302 to store instructions and data; an instruction fetch unit 304 to fetch instructions from memory 302, and to optionally, provide local buffering for the fetched instructions; an instruction decode unit 306 to receive Instructions from instruction fetch unit 304 and to determine the type of instructions that have been fetched; and an instruction execution unit 308 to execute the instructions. Execution may include loading data into a register from memory 302; storing data back to memory from a register; or performing some type of arithmetic or logical operation, as determined by the decode unit.

In one example, each unit described above is implemented in software. For instance, the operations being performed by the units are implemented as one or more subroutines within emulator software. In another example, one or more of the operations are implemented in firmware, hardware, software or some combination thereof.

Further, although FIG. 3 is described with reference to emulation, the environment of FIG. 3 need not be an emulation environment. In another example, instructions are executed in a native environment, and the operations are implemented in hardware, firmware, software or some combination thereof.

A computing environment may include virtual storage, as well as main storage. Virtual storage may far exceed the size of main storage available in the configuration and is normally maintained in auxiliary storage. Virtual storage is considered to be composed of blocks of addresses, called pages. The most recently referred to pages of virtual storage are assigned to occupy blocks of physical main storage. As a user refers to pages of virtual storage that do not appear in main storage, the virtual pages are brought in to replace the pages in main storage that are less likely to be used. The swapping of pages in storage may be performed by the operating system without the user's knowledge.

The addresses used to designate locations in virtual storage are referred to as virtual addresses. A block of sequential virtual addresses spanning, for instance, up to 4k bytes, is referred to as a page. Similarly, a block of sequential virtual pages spanning, for instance, up to 1M bytes is referred to as a segment; and a block of sequential virtual segments spanning, for instance, up to 2G bytes, is referred to as a region. Further, a sequence of virtual addresses associated with virtual storage pointed to by an address space control element (ASCE) is called an address space. Address spaces may be used to provide degrees of isolation between users. An address space can include one or more regions, one or more segments, one or more pages, or some combination thereof.

Associated with the different types of units of storage (e.g., regions, segments, pages) are data structures to be used in processing associated with the units of storage. For example, associated with regions are region tables; associated with segments are segment tables; and associated with pages are page tables. These tables are used, for instance, during translation (e.g., Dynamic Address Translation) of a virtual address to a real address that is used to access main storage. The tables to be used in translation, referred to herein as translation tables, are designated by an address space control element (ASCE). This is described in further detail in an IBM® publication entitled, "z/Architecture Principles of Operation," IBM Publication No. SA22-7832-00, December 2000. A unit of virtual storage that is not currently assigned to main storage is called invalid. The invalid state of a unit of virtual storage is indicated by an invalid indicator in the data structure associated with the unit.

The dynamic address translation mechanism is implemented, in one embodiment, such that the information derived from the translation tables (e.g., region tables, segment tables and/or page tables) through the DAT process is maintained in one or more buffers located within the processors, referred to herein as Translation Lookaside Buffers, in order to enhance performance of address translation. That is, during the translation, the buffers are checked for the needed information, and then, if the information is not in the buffers, one or more of the translation tables are accessed.

In one embodiment, a buffer entry is considered as one of three types: a TLB combined region-and-segment-table entry; a TLB page table entry; or a TLB real space entry, each of which is described below.

A TLB combined region-and-segment-table entry (CRSTE) includes both the information obtained from the table entry or entries in real or absolute storage and the attributes used to fetch this information from storage. In one example, a TLB combined region-and-segment-table entry (CRSTE) includes the following fields: <ul id="ul0002" list-style="none"><li>TO The table origin in the address-space-control element used to form the entry;</li><li>RX The region index of the virtual address used to form the entry;</li><li>SX The segment index of the virtual address used to form the entry;</li><li>PTO The page table origin fetched from the segment table entry in real or absolute storage;</li><li>C The common segment bit fetched from the segment table entry in real or absolute storage; and</li><li>P The page protection bit fetched from the segment table entry in real or absolute storage.</li><li>V The validity bit indicates if the entry in the TLB is valid, and therefore, can be used for looking up subsequent entries.</li></ul>

A TLB page table entry includes the information obtained from the table entry or entries in real or absolute storage and the attributes used to fetch this information from storage. In one example, a TLB page table entry includes: <ul id="ul0003" list-style="none"><li>TO The table origin in the address-space-control element or TLB combined region-and-segment-table entry used to form the entry, depending on how the entry was formed;</li><li>PTO The page table origin used to form the entry;</li><li>PX The page index of the virtual address used to form the entry;</li><li>PFRA The page-frame real address fetched from the page table entry in real or absolute storage; and</li><li>P The page protection bit fetched from the page table entry in real or absolute storage.</li><li>V The validity bit indicates if the entry in the TLB is valid, and therefore, can be used for looking up subsequent entries.</li></ul>

At times, a unit of storage is to be invalidated. To facilitate this invalidation, the translation table associated with that storage unit is employed, as described herein. Further, responsive to invalidating the storage, corresponding buffer entries may also be cleared. For example, in order to invalidate a page of storage, an invalid bit of a page table entry is set. Additionally, in one example, the corresponding entries in one or more TLBs are atomically cleared. In one particular example, the invalidation and clearing of entries associated with pages of storage are performed by an Invalidate Page Table Entry (IPTE) instruction.

In addition to invalidating pages of storage, in accordance with an aspect of the present invention, segments of storage and/or regions of storage may be invalidated. As one example, segment and/or region tables are used in this invalidating. One embodiment of the logic associated with invalidating a particular unit of storage is described with reference to FIG. 4.

Initially, a region or segment table in which one or more entries is to be invalidated is identified, STEP 400. In one example, this includes the providing of a region table origin or a segment table origin. Then, an entry within the designated region or segment table is identified for invalidation, STEP 402, and the entry is invalidated, STEP 404. In one example, the identification is done by providing a region index or segment index (bits of a virtual address) that selects an entry within the identified table, and the invalidation includes setting an invalid indicator within the entry. Responsive to setting the invalid indicator, a corresponding unit of storage (e.g., a region or segment) is invalidated.

Thereafter, a determination is made as to whether there are more entries to be invalidated, INQUIRY 406. If there are more entries to be invalidated, then processing continues with STEP 402. Otherwise, processing is complete.

In addition to invalidating the one or more entries in a region or segment table and thus invalidating those units of storage, the corresponding entries (or other entries) may be cleared or purged from one or more buffers on one or more processors within the environment. One embodiment of the logic associated with this clearing is described in further detail with reference to FIG. 5.

Initially, a determination is made as to whether a region or segment table origin is being specified, INQUIRY 500. If a region or segment table origin is specified, then one or more buffers are cleared of an entry specified by the region or segment index that matches the region or segment origin, STEP 502. Subsequently, a determination is made as to whether there are more entries to be cleared, INQUIRY 504. If so, then processing continues with STEP 502. Otherwise, processing is complete.

Returning to INQUIRY 500, if the region or segment table origin is not specified, then one or more buffers are cleared of an entry specified by the region or segment index, STEP 508. Thereafter, a determination is made as to whether there are more entries to be cleared, INQUIRY 510. If there are more entries to be cleared, then processing continues with STEP 508. Otherwise, processing is complete.

In one example, the invalidation and clearing are performed by one instruction. The instruction invalidates the selected entries of a segment or region table and atomically purges at least the corresponding entries (or other entries) from the TLBs on the processors of the configuration. In one example, the entries are purged from all TLBs on all processors, whether physical, virtual or emulated by software. If a multi-level TLB structure exists, then all levels are purged, in one example. If multiple logical partitions exist in the system, then TLB entries on this and other processors that were formed for the logical partition that the current IDTE instruction is being executed in, are purged.

This instruction can be implemented in many architectures and may be emulated. As examples, the instruction can be executed in hardware by a processor; or by emulation of the instruction set including this instruction, by software executing on a computer having a different native instruction set. In one particular example, the instruction is implemented in the z/Architecture, and is referred to herein as an Invalidate Dynamic Address Translation (DAT) Table Entry (IDTE) instruction.

IDTE provides, for instance, an invalidation and clearing option, in which one or more regions or segments of storage are invalidated via one or more entries of a region table or segment table, and at least the corresponding entries (or other entries) from the TLBs (e.g., all the TLBs) in the configuration are purged. The instruction specifies a minimum set of TLB entries to be purged. In a further implementation, more or even all TLB entries may be purged upon execution of the IDTE instruction.

One embodiment of the format of an Invalidate DAT Table Entry (IDTE) instruction is described with reference to FIG. 6a. In one example, an IDTE instruction 600 includes, for instance, an operation code 602 designating the Invalidate DAT Table entry instruction (e.g., 'B98E'x), and a plurality of registers 604-608. Each of the registers is described in further detail below with reference to FIGs. 6b-6d.

Referring to FIG. 6b, register 606, which is general register R1, has, for instance, a format of an address space control element with a table origin (e.g., bits 0-51), and a designation type control (bits 60 and 61) used. Bits 52-59, 62 and 63 are ignored. In particular, R1 includes, for instance, a region table or segment table origin for invalidation 610, which designates the translation table of which one or more entries are to be invalidated; and a designation type control (DT) 612, which specifies the type of that table (e.g., region table or segment table).

Register 608 (FIG. 6c), which is general register R2, includes a region first index 614, specifying a first level region table; a region second index 616, specifying a second level region table; and a region third index 618, specifying a third level region table. That is, to accommodate large virtual addresses, three levels of region tables are used. Register R2 also includes a segment index 620, which is an index into a segment table; a mode indicator 621, which determines the function to be performed; and an additional entries indicator 622, which indicates how many entries are to be invalidated. For example, bits 53-63 of general register R2 include a binary integer specifying the number of additional table entries to be invalidated. In one example, the number of entries to be invalidated is 1-2048, corresponding to a value in bits 53-63 of 0-2047. Bits 44-51 of general register R2 are zeros; otherwise, a specification exception is recognized. Thus, bits 0-43 of general register R2 have the format of the region index and segment index of a virtual address. The part of bits 0-43 used by DAT to select an entry in the type of table designated by general register R1 is called an Effective Invalidation Index, and is described in further detail below.

Register 604 (FIG. 6d), which is general register R3, has, for instance, a format of an address-space-control element with the table origin, bits 0-51, being used, if it is non-zero. This table origin is used to select TLB entries to be cleared, and the type of table it designates is independent of bits 60 and 61 of general register R1. Bits 52-63 of general register R3 are ignored. If R3 is zero, the entire contents of general register 0 are ignored. In one example, the entries to be cleared can be the same or different than the entries that are invalidated.

One embodiment of the logic associated with an invalidation and clearing operation is described with reference to FIGs. 7a-7b. In one example, an invalidation and clearing operation is specified when bit 52 of general register R2 is zero. With this operation, the designated region table entry or segment table entry in storage or a range of entries beginning with the designated entry, is invalidated, and the translation lookaside buffers (TLBs) in the CPUs of the configuration are cleared of the associated entries (or other entries). In one example, all levels of the buffers, if they are multi-level, in all CPUs are cleared.

Referring to FIG. 7a, initially, a region table or segment table origin designating a region table or segment table from which one or more entries are to be invalidated is specified, STEP 700. In one example, this is specified in general register R1. Additionally, a table entry in storage to be invalidated is selected, STEP 702. In one example, a table entry is designated by adding the table origin in general register R1 and the effective invalidation index in general register R2 and following various rules, as described herein.

Bits 60 and 61 of general register R1 specifies a table type and an effective invalidation index, as follows: <tables id="tabl0001" num="0001"><table frame="bottom"><tgroup cols="3" colsep="0"><colspec colnum="1" colname="col1" colwidth="41mm" /><colspec colnum="2" colname="col2" colwidth="34mm" /><colspec colnum="3" colname="col3" colwidth="62mm" /><thead><row><entry><b>Bits 60 and 61 of Reg. R1</b></entry><entry align="center"><b>Table Type</b></entry><entry align="center"><b>Effective invalidation Index in Reg. R2</b></entry></row></thead><tbody><row rowsep="0"><entry morerows="1">11</entry><entry morerows="1">Region first table</entry><entry>Region first index</entry></row><row rowsep="0"><entry>   (bits 0-10)</entry></row><row rowsep="0"><entry morerows="1">10</entry><entry morerows="1">Region second table</entry><entry>Region second index</entry></row><row rowsep="0"><entry>   (bits 11-21)</entry></row><row rowsep="0"><entry morerows="1">01</entry><entry morerows="1">Region third table</entry><entry>Region third index</entry></row><row rowsep="0"><entry>   (bits 22-32)</entry></row><row rowsep="0"><entry morerows="1" rowsep="1">00</entry><entry morerows="1" rowsep="1">Segment table</entry><entry>Segment index</entry></row><row rowsep="0"><entry>   (bits 33-43)</entry></row></tbody></tgroup><tgroup cols="3" rowsep="0"><colspec colnum="1" colname="col1" colwidth="41mm" /><colspec colnum="2" colname="col2" colwidth="34mm" /><colspec colnum="3" colname="col3" colwidth="62mm" /><tbody><row><entry namest="col1" nameend="col3" align="justify">(The part of bits 0-43 to the right of the effective invalidation index is ignored.)</entry></row></tbody></tgroup></table></tables>

With reference to the above table, when bits 60 and 61 have the value 11 binary, the region first index portion of R2, in conjunction with the region first table origin of R1, is used to select an entry in a region first table. The table origin is treated as a 64-bit address.

The 64-bit address of the region first table entry in real or absolute storage is obtained by appending twelve zeros to the right of bits 0-51 of the region first table designation and adding the region first index with three rightmost and fifty leftmost zeros appended. This addition is performed according to the rules for 64-bit address arithmetic, regardless of the current addressing mode, specified by bits 31 and 32 of the current Program Status Word (PSW). When a carry out of bit position zero occurs during the addition, it is ignored. The address formed from these two components is a real or absolute address. All 64 bits of the address are used regardless of whether the current PSW specifies the 24-bit, 31-bit or 64-bit addressing mode.

In one example, the entire region first table entry is fetched concurrently from storage, as observed by other CPUs. The fetch access to the entry is subject to key-controlled protection, and the store access is subject to key-controlled protection and low-address protection. When the storage address generated for fetching the region first table entry designates a location which is not available in the configuration, an addressing exception is recognized and the unit of operation is suppressed.

When bits 60 and 61 have the value 10 binary, the region second index of R2, in conjunction with the region second table origin of R1, is used to select an entry from the region second table. The region second table lookup process is similar to the region first table lookup process. When no exceptions are recognized, the entry fetched from the region second table designates the beginning and specifies the offset and length of the corresponding region third table.

When bits 60 and 61 have the value of 01 binary, the region third index portion of R2, in conjunction with the region third table origin of R1, is used to select an entry from the region third table. The region third table lookup process is similar to the region first table lookup process. When no exceptions are recognized, the entry fetched from the region third table designates the beginning and specifies the offset in length of the corresponding segment table.

When bits 60 and 61 have the value 00 binary, the segment index portion of R2, in conjunction with the segment table origin of R1, is used to select an entry from the segment table. The segment table lookup process is similar to the region first table lookup process. When no exceptions are recognized, the entry fetched from the segment table designates the beginning of the corresponding page table.

The entire table entry is fetched concurrently from storage, in one example. Subsequently, the entry is invalidated. STEP 704. In one example, the entry is invalidated by setting bit 58 of the entry to 1 binary. By invalidating this entry, the corresponding unit of storage is invalidated.

Thereafter, a determination is made as to whether more entries are to be invalidated, INQUIRY 706. In one example, this determination is made by checking bits 53-63 of general register R2. If bits 53-63 of general register R2 are not all zeros, then more entries are to be invalidated. Thus, a 1 is added to the previous used value of the effective invalidation index and processing continues with STEP 700. This is repeated so that a number of entries one more than the number specified by bits 53-63 are invalidated. A carryout of the leftmost bit position of the effective invalidation index is ignored, and wraparound in the table occurs in this case. The contents of general register R2 remain unchanged.

Subsequent to invalidating the one or more entries, in accordance with a further aspect of the present invention, this CPU clears selected entries from its TLB and signals the other CPUs in the configuration to clear selected entries from their TLBs, STEP 708. In one example, each TLB is cleared of at least those Combined Region and Segment Table entries (CRSTEs) that meet the following conditions:

The effective invalidation index and the bits to the left of it in general register R2, and the same part of the region-and-segment-index field in the TLB entry, match. (In one embodiment, if these fields include segment-index fields, either CRSTEs may be cleared regardless of their region-index fields or all CRSTEs may be cleared. If the fields do not include segment-index fields, all CRSTEs may be cleared.) Note that when multiple table entries are invalidated due to bits 53-63 of general register R2, then the effective invalidation index is incremented, and a carry out of the left-most bit position of the index is lost.

Either R3 is zero or the table-origin field in general register R3 matches the table-origin field in the TLB entry.

If the invalidated entry is a segment-table entry, the page-table-origin field in the invalidated entry matches the page-table-origin field in the TLB entry. (In one embodiment, a TLB entry may be cleared regardless of the page-table origin in the entry.)

Each TLB is also cleared of at least those page table entries in which the page-table-origin field matches the page-table-origin field in (1) the invalidated segment-table entry, if a segment-table entry was invalidated, or (2) any combined region-and-segment-table entry that was cleared (it is in the set that is to be cleared) in the same TLB. (In another embodiment, the implementation may clear a page-table entry regardless of the page table origin in the entry. That is, it may clear all page table entries.)

One embodiment of the logic associated with clearing entries from a TLB is described with reference to FIG. 7b. As one example, this is a continuation of the processing performed by IDTE, and it is performed atomically to the invalidation as observed by this CPU and other CPUs in the system.

Referring to FIG. 7b, initially a determination is made as to whether R3 is zero, INQUIRY 720. If R3 is nonzero, then a region table or segment table origin for clearing is indicated in register R3 and, to clear a TLB entry, the region/segment table origin designated in register R3 is to match the region/segment table origin used to form the entry, STEP 722. If R3 is zero, the contents of register R3 (register 0) are ignored, and an entry is cleared regardless of the region/segment table origin used to form the entry, STEP 724.

The TLB is cleared on all processors in the system of those entries specified by the region/segment index specified in register R2, STEP 726. In one example, the TLB is cleared of at least those combined region and segment table entries in which, for instance, the effective invalidation index and the bits to the left of it in general register R2 and the same part of the region and segment index table in the TLB entry match. To clear an entry, the V bit is turned off, as one example.

Further, if a segment table entry is being invalidated, then the TLBs on all processors in the system are cleared of page table entries in which the page table origin in the entry is equal to the page table origin in the TLB, STEP 728. Further, if a segment table entry is being invalidated, TLBs are cleared of at least those page table entries in which the page table origin field matches the page table origin field in any CRSTE that was cleared (e.g., necessarily) in the same TLB, STEP 730. This clearing process is repeated for a number of entries one more than the number specified in additional entries field 622 of FIG. 6c, STEP 732.

Thereafter, a determination is made as to whether the invalidation and clearing operation is complete, INQUIRY 734. In one example, the IDTE instruction is not complete on the issuing processor until the designated TLB entries have been cleared on that CPU and all other CPUs in the system have completed any storage accesses using the TLB entry specified in this instruction. In one example, it is the quiesce controller that indicates to this issuing processor whether the other processors have completed their accesses. That is, the issuing processor is considered the master processor and any slave processors affected by the IDTE instruction indicate to the controller their state. Responsive to the controller receiving the appropriate state from the slave processors, it indicates completion to the master. Should processing be complete, then the instruction ends, STEP 736. Otherwise, the processor waits for a predetermined amount of time and checks the status, once again, or is signaled as to completion, INQUIRY 734.

In one embodiment, storing in the region or segment table entry and the clearing of TLB entries may or may not occur if the invalid bit was already one in the region or segment table entry.

Although in the embodiment described above the clearing of the TLB entries is performed subsequent to invalidating the desired entries, in other embodiments, the clearing of TLB entries may occur after each invalidation, after a selected number of invalidations, etc.

In a further aspect of the present invention, the IDTE instruction can alternatively be used to purge TLB entries associated with an address space (e.g., designated by an Address Space Control Element (ASCE)). In one example, this option is indicated by setting bit 52 of general register R2 to 1. With this option, the contents of general register R1 are ignored (see FIG. 8a), as well as bits 0-43 and 53-63 of general register R2 (see FIG. 8b). The contents of general register R3 have the format of an address space control element with the table origin, bits 0-51, being used (FIG. 8c). Bits 52-63 of general register R3 are ignored. R3 may be zero or non-zero; that is any general register including register 0 may be designated. This operation does not perform any invalidation of storage, but it does clear from the TLBs of the CPUs in the configuration, at least those combined region-and-segment-table entries and page table entries in which the table origin field matches the table origin field in general register R3. (In a further embodiment, the implementation may clear a page table entry, regardless of the table origin in the entry. That is, it may clear all page table entries.)

One embodiment of the logic associated with a clearing by ASCE operation is described with reference to FIG. 9. Initially, a region table or segment table origin designating a region table or segment table for which corresponding TLB entries are to be cleared is specified, STEP 900. In one example, this is specified in bits 0-51 of general register R3. Thereafter, at least the combined region-and-segment table entries and page table entries corresponding to the table origin specified in R3 are cleared on all processors in the system, STEP 902.

Subsequently, a determination is made as to whether execution of the IDTE instruction is complete, INQUIRY 904. In one embodiment, the IDTE instruction is not complete on the issuing processor until the TLB entries corresponding to the specified parameters have been cleared on the issuing CPU and the other CPUs in the configuration have completed any storage accesses, including the updating of change and reference bits, by using TLB entries corresponding to the specified parameters. If the entries have been cleared and the storage accesses are complete, then execution of the IDTE instruction is complete, STEP 906. Otherwise, the processor waits for a predetermined amount of time and checks the status once again or is signaled as to completion, INQUIRY 904.

Described in detail above is processing associated with an IDTE instruction. In one embodiment, the operations do not necessarily have any effect on TLB real space entries. The following provides additional information, enhancements and/or embodiments associated with processing of one embodiment of an IDTE instruction. <ol id="ol0001" compact="compact"><li>1. The selective clearing of TLB entries may be implemented in different ways, depending on the model or selected embodiment. For instance, in general, more entries may be cleared than the minimum number specified. When the invalidation-and-clearing operation is performed, all combined region-and-segment table entries (CRSTEs) containing a segment index equal to an effective invalidation index that is a segment index may be cleared, or all CRSTEs may be cleared when the effective invalidation index is not a segment index. Further, a CRSTE or page table entry may be cleared regardless of the page table origin in the entry. When the clearing-by-ASCE operation is performed, a page table entry may be cleared regardless of the table origin in the entry. When either operation is performed, in one embodiment, the precise minimum number of entries required may be cleared.</li><li>2. An address-space control element may contain a real space token origin instead of a region-table or segment-table origin. A table origin in general register R3 is indistinguishable from a token origin in the register.</li><li>3. When the invalidation-and-clearing operation is specified, the clearing of TLB entries may make use of the page-table origin in a segment-table entry. Therefore, if the segment-table entry, when in the attached state, contained a page table origin that is different from the current value, copies of entries containing the previous values may remain in the TLB.</li><li>4. When the invalidation-and-clearing operation is specified, the address of the DAT-table entry for the IDTE is a 64-bit address, and the address arithmetic is performed by following the normal rules for 64-bit address arithmetic, with wraparound at 2⁶⁴ - 1. Also, offset and length fields are not used. Accordingly, the DAT tables are not to be specified to wrap from maximum storage locations to location 0, and the first designated entry and all additional entries specified by bits 63-63 of general register R3 should lie within the designated table.</li><li>5. The IDTE instruction is subject to interception under SIE. In one embodiment, the system is serialized such that the processor executing the IDTE instruction cannot begin the operation until the other processors have stopped using the TLB entries to be specified. Furthermore, the processor executing the IDTE instruction does not continue with further execution until the appropriate entries have been cleared from the TLBs of all processors in the system.</li><li>6. A serialization function is performed before the operation begins and again after the operation is completed. The serialization applies to this CPU; other CPUs are not necessarily serialized.</li></ol>

Described in detail above is one example of an instruction that can invalidate entries of a segment or a region table and atomically clear at least the corresponding entries (or other entries) from one or more translation lookaside buffers. Different opcodes, different fields, different registers or even no registers, different bits, etc. may be used. For instance, other instruction set architectures may define an equivalent instruction in somewhat different ways (e.g., different opcodes, different fields in the instruction, different registers used, etc.), but one or more aspects of the present invention still apply. Further, as described above, one or more aspects of the present invention apply equally well to a software emulation of a target architecture, such as IBM's z/Architecture. In this case, the TLBs discussed above may be an array or other data structure implemented by the software emulator to hold recent virtual to real address mappings. It may also be that the emulator software does not implement any structure analogous to a TLB. In this case, only the invalidation of entries in storage may apply.

Thus, an instruction is provided herein that is capable of invalidating storage, invalidating storage and atomically clearing buffer entries, or clearing buffer entries. Therefore, it is said that one or more registers of the instruction are configurable as no-operations (no-ops). That is, the information in those registers, if any, associated with a particular operation (e.g., invalidation, clearing, etc.) that is not being provided is ignored or indicates that the operation is not being performed.

Although a particular instruction is described above in which invalidation, invalidation and clearing, or clearing is provided, the instruction can be modified or other instructions can be implemented that just perform one or more aspects of the operations implemented by IDTE. For example, an instruction can just implement the invalidation of storage. As a further example, the instruction can just purge entries from buffers that are associated with particular segment or region tables. As yet a further example, an instruction can be implemented that just purges entries based on address space.

In a commercial implementation of the invalidation and/or clearing facility computer architected instruction format, the instructions are used by programmers, such as operating system programmers writing in assembler language. These instruction formats stored in a storage medium may be executed natively in a z/Architecture IBM Server, or alternatively, in machines executing other architectures. They can be emulated in the existing and in future IBM mainframe servers and on other machines of IBM (e.g., pSeries Servers and xSeries Servers). They can be executed in machines running Linux on a wide variety of machines using hardware manufactured by IBM, Intel, AMD, Sun Microsystems and others. Besides execution on the hardware under z/Architecture, Linux can be used, as well as machines which use emulation by Hercules, UMX, FXI or Platform Solutions, where generally execution is in an emulation mode.

In emulation mode, the specific instruction being emulated is decoded, and a subroutine is built to implement the individual instruction, as in a C subroutine or driver, or some other technique is used for providing a driver for the specific hardware, as is within the skill of those in the art after understanding the description of an embodiment of the invention. Various software and hardware emulation patents including, but not limited to, <patcit id="pcit0003" dnum="US5551013A"><text>U.S. Patent No. 5,551,013</text></patcit>, <patcit id="pcit0004" dnum="US6009261A"><text>U.S. Patent No. 6,009,261</text></patcit>, <patcit id="pcit0005" dnum="US5574873A"><text>U.S. Patent No. 5,574,873</text></patcit>, <patcit id="pcit0006" dnum="US6308255B"><text>U.S. Patent No. 6,308,255</text></patcit>, <patcit id="pcit0007" dnum="US6463582B"><text>U.S. Patent No. 6,463,582</text></patcit> and <patcit id="pcit0008" dnum="US5790825A"><text>U.S. Patent No. 5,790,825</text></patcit> illustrate a variety of known ways to achieve emulation of an instruction format architected for a different machine for a target machine available to those skilled in the art, as well as those commercial software techniques used by those referenced above.

Advantageously, one or more aspects of the present invention increase system performance. For instance, by selectively purging entries from buffers instead of completely purging the buffers, system performance is enhanced by not requiring unnecessary recreation of entries. That is, it requires 20+ to 100s of cycles to create a TLB entry, and selective purging avoids the unnecessary recreation of entries.

As a further advantage, if a full TLB purge is desired, then the implementation allows for over purging. Further, the TLB portion can be treated as a no-op, if, for instance, a TLB is not used. Advantageously, the IDTE instruction can be implemented in hardware, firmware, software or a combination thereof, or it may be used in an emulator of a target computer instruction set.

One or more aspects of the present invention are equally applicable to, for instance, virtual machine emulation, in which one or more pageable entities (e.g., guests) execute on one or more processors. As one example, pageable guests are defined by the Start Interpretive Execution (SIE) architecture, one example of which is described in an IBM publication entitled, "IBM System/370 Extended Architecture," IBM Publication No. SA22-7095 (1985).

Although SIE and the z/Architecture are mentioned above, one or more aspects of the present invention are equally applicable to other architectures and/or environments employing pageable entities or similar constructs.

Moreover, the various embodiments described above are just examples. Although a logically partitioned environment is described herein, this is only one example. Aspects of the invention are beneficial to many types of environments including other environments that have a plurality of zones, and non-partitioned environments. Further, there may be no central processor complexes, but yet, multiple processors coupled together. Yet further, one or more aspects of the invention are applicable to single processor environments.

Although particular environments are described herein, again, many variations to these environments can be implemented. For example, if the environment is logically partitioned, then more or fewer logical partitions may be included in the environment. Further, there may be multiple central processing complexes coupled together. These are only some of the variations that can be made. Additionally, other variations are possible. For example, although the controller described herein serializes the instruction so that one IDTE instruction executes at one time, in another embodiment, multiple instructions may execute at one time. Further, the environment may include multiple controllers. Yet further, multiple quiesce requests (from one or more controllers) may be concurrently outstanding in the system. Additional variations are also possible.

As used herein, the term "processing unit" includes pageable entities, such as guests; processors; emulators; and/or other similar components. Moreover, the term "by a processing unit" includes on behalf of a processing unit. The term "buffer" includes an area of storage, as well as different types of data structures, including, but not limited to, arrays; and the term "table" can include other than table type data structures. Further, the instruction can include other than registers to designate information. Moreover, a page, a segment and/or a region can be of sizes different than those described herein.

One or more of the capabilities of the present invention can be implemented in software, firmware, hardware, or some combination thereof. Further, one or more of the capabilities can be emulated.

One or more aspects of the present invention can be included in an article of manufacture (e.g., one or more computer program products) having, for instance, computer usable media. The media has embodied therein, for instance, computer readable program code means or logic (e.g., instructions, code, commands, etc.) to provide and facilitate the capabilities of the present invention. The article of manufacture can be included as a part of a computer system or sold separately.

Additionally, at least one program storage device readable by a machine embodying at least one program of instructions executable by the machine to perform the capabilities of the present invention can be provided.

The flow diagrams depicted herein are just examples. There may be many variations to these diagrams or the steps (or operations) described therein. For instance, the steps may be performed in a differing order, or steps may be added, deleted or modified.