# Patent

## Title
Providing logical partitions with hardware-thread specific information reflective of exclusive use of a processor core

## Abstract

Techniques for simulating exclusive use of a processor core amongst multiple logical partitions (LPARs) include providing hardware thread-dependent status information in response to access requests by the LPARs that is reflective of exclusive use of the processor by the LPAR accessing the hardware thread-dependent information. The information returned in response to the access requests is transformed if the requestor is a program executing at a privilege level lower than the hypervisor privilege level, so that each logical partition views the processor as though it has exclusive use of the processor. The techniques may be implemented by a logical circuit block within the processor core that transforms the hardware thread-specific information to a logical representation of the hardware thread-specific information or the transformation may be performed by program instructions of an interrupt handler that traps access to the physical register containing the information.

## Background
The present Application is a Continuation of U.S. patent application Ser. No. 13/345,002, filed on Jan. 6, 2012 and claims priority thereto under 35 U.S.C. 120. The disclosure of the above-referenced parent U.S. Patent Application is incorporated herein by reference.


BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention is related to processing systems and processors, and more specifically to techniques for managing values of hardware thread specific information returned to logical partitions executed by hardware threads of a processor core.
2. Description of Related Art
In large scale computer systems, in particular in multi-user computer systems or so-called cloud computing systems in which multiple processors support multiple virtual operating systems and images, referred to as logical partitions (LPARs), a hypervisor manages allocation of resources to the LPARs, and the starting/stopping of LPARs at system startup/shutdown and context swaps. The LPARs are preferably isolated from each other when the system is used, for example, to support execution of different LPARs for different customers. Typically, the processor cores used in such a computer system support concurrent execution of multiple hardware threads, e.g., 8 or more hardware threads, which correspond to parallel execution pipelines within the processor core. Typically also, the hypervisor assigns a number of threads to each LPAR.
Status and other informational values within the processor are hardware thread-specific, i.e., the values may be either a value for each hardware thread number, be dependent on the thread trying to access the value, or may be the number of hardware threads that the processor supports.
It would be desirable to provide techniques for managing accesses to hardware thread-specific information that are independent of which LPAR is accessing the information and provides security between LPARS.
BRIEF SUMMARY OF THE INVENTION
The invention is embodied in a method, computer systems, processor core and computer program product that provide hardware thread-dependent status information in response to access requests. The information returned in response to the access requests is transformed if the requestor is a program executing at a privilege level lower than the hypervisor privilege level, so that each logical partition views the processor as though it has exclusive use of the processor core.
The method may be implemented by a logical circuit block within the processor that transforms the hardware thread-specific information to a logical representation of the hardware thread-specific information that reflects exclusive use of the processor core by threads of a given logical partition executed by the processor. Alternatively, the transformation may be performed by program instructions of an interrupt handler that traps access to the physical register of the processor core that contains the information. The interrupt handler either transforms the contents of the register directly, or performs the transformation via a look-up in memory of a table that contains previously transformed thread-specific information.
The foregoing and other objectives, features, and advantages of the invention will be apparent from the following, more particular, description of the preferred embodiment of the invention, as illustrated in the accompanying drawings.



BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING
The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives, and advantages thereof, will best be understood by reference to the following detailed description of the invention when read in conjunction with the accompanying Figures, wherein like reference numerals indicate like components, and:
FIG. 1 is a block diagram illustrating a processing system in which techniques according to an embodiment of the present invention are practiced.
FIG. 2 is a block diagram illustrating details of a processor core 20 in accordance with an embodiment of the present invention.
FIG. 3 is a block diagram illustrating details of logical thread information block 50 within processor core 20 of FIG. 2, in accordance with an embodiment of the present invention.
FIG. 4 is a flowchart depicting a method in accordance with another embodiment of the present invention.



DETAILED DESCRIPTION OF THE INVENTION
The present invention relates to processor cores and processing systems in which hardware thread-dependent stored within processor cores is transformed when accessed by logical partitions (LPARs) that access the information. The transformation is performed such that it appears to each LPAR that the LPAR has exclusive use of the processor core. For example, if a processor core supports 8 hardware threads and the threads are apportioned equally between two LPARs being executed by the processor core, then requests for the number of hardware threads supported by the processor will be returned as 4 when the LPAR accesses that information. Similarly, arrays of hardware thread-specific information or words containing fields of thread-specific information will be modified to contain only 4 entries commencing at zero (or other base thread number used by the processor). Transformation of the hardware thread-specific information is triggered by an access from a privilege level lower than the hypervisor privilege level, so that when the hypervisor accesses the hardware thread-specific information, the hardware thread-specific information for all hardware threads is returned. The transformation of hardware-thread specific register values can be performed by a logical circuit, or by an interrupt handler that traps access to the register and returns the transformed value, which may be retrieved from a table in memory, or computed directly by the interrupt handler.
Referring now to FIG. 1, a processing system in accordance with an embodiment of the present invention is shown. The depicted processing system includes a number of processors 10A-10D, each in conformity with an embodiment of the present invention. The depicted multi-processing system is illustrative, and processing system in accordance with other embodiments of the present invention include uni-processor systems having symmetric multi-threading (SMT) cores. Processors 10A-10D are identical in structure and include cores 20A-20B and local storage 12, which may be a cache level, or a level of internal system memory. Processors 10A-10B are coupled to main system memory 14, a storage subsystem 16, which includes non-removable drives and optical drives, for reading media such as a CD-ROM 17 forming a computer program product and containing program instructions implementing a hypervisor for controlling multiple logical partitions (LPAR) for execution by processors 10A-10D, and also operating systems each of which has at least one supervisory thread for managing the operating system scheduler and other services, and also containing executable programs that implement applications and services executing within the logical partitions. The illustrated processing system also includes input/output (I/O) interfaces and devices 18 such as mice and keyboards for receiving user input and graphical displays for displaying information. While the system of FIG. 1 is used to provide an illustration of a system in which the processor architecture of the present invention is implemented, it is understood that the depicted architecture is not limiting and is intended to provide an example of a suitable computer system in which the techniques of the present invention are applied.
Referring now to FIG. 2, details of processor cores 20A-20B of FIG. 1 are illustrated in depicted core 20. Core 20 includes an instruction fetch unit (IFU) 22 that fetches one or more instruction streams from cache or system memory and presents the instruction stream(s) to an instruction decode unit 24. A global dispatch unit 25 dispatches the decoded instructions to a number of internal processor pipelines. The processor pipelines each include a register mapper 26, one of issue queues 27A-27D, and an execution unit provided by branch execution unit (BXU) 28, condition result unit (CRU) 29, fixed-point unit load-store unit (FXU/LSU) 30 or floating point units (FPUs) 31A-31B. Registers such as counter register (CTR) 23A, condition register (CR) 23B general-purpose registers (GPR) 23D, and floating-point result registers (FPR) 23C provide locations for results of operations performed by the corresponding execution unit(s). A global completion table (GCT) 21 provides an indication of pending operations that is marked as completed when the results of an instruction are transferred to the corresponding one of result registers 23A-23D. Register mappers 26 allocate storage in the various register sets so that concurrent execution of program code can be supported by the various pipelines. FXU/LSU 30 is coupled to a data cache 44 that provides for loading and storing of data values in memory that are needed or modified by the pipelines in core 20. Data cache 44 is coupled to one or more translation look-aside buffers (TLB) 45 that map real or virtual addresses in data cache 44 to addresses in an external memory space.
Exemplary processor core 20 also includes a logical thread information block 50 that, in the illustrative example and for convenience of illustration, contains all of the hardware-thread specific registers within processor core 20. While the hardware-thread specific registers may generally be co-located with other registers or in any location, in the depicted embodiment of processor core, they are organized with other logic that controls access by FXU/LSU 30 to the hardware thread-dependent status information within core 20, by both the hypervisor and by the LPARs and applications executed within the LPARs. Exemplary hardware thread-dependent status information includes thread identification register (TIR) 41 and thread status register (CR) 42, along with an inter-thread message delivery status register 43. Table I below lists the exemplary hardware thread-specific status registers and their function and physical register contents/ranges. Table I, also shows the logical ranges/contents that will be returned to an LPAR that attempts to access the physical hardware thread-specific register, either by the control logic described below with reference to FIG. 3 or by the interrupt handling software described below with reference to FIG. 4.











TABLE I







Physical
Logical
Logical Value Transform


Register Name
Function/Meaning
Value range
Value Range
algorithm







TIR (Thread
Contains the thread 
0-N where
0-M, where
TIR - base[LPAR]


Identification
number of the
N = number
M = number



Register)
accessing process
of threads
of threads





minus 1
allocated to






the LPAR






minus 1



Thread
Indicates whether a 
Contains a
Contains
shl(base[LPAR]) & mask


Execution
thread is active
bit for each
left-aligned



Status Register
(executing)
of threads
bits for each 



(CR)

0-N
of threads 0-M



Inter-thread
Indicates whether
Contains a
Contains
shl(base[LPAR]) & mask


message
messages have
bit for each
left-aligned



delivery status 
been delivered to
of threads
bits for each



registers
target thread
0-N
of threads 0-M









TIR 41 is a register that returns the value of the hardware thread number of the thread that is accessing TIR 41. In order to provide a logical equivalent to the LPAR that simulates exclusive use of processor core 20 by a hardware thread, the thread number must be normalized to range of hardware thread numbers that belong to the LPAR. For simplicity and the sake of illustration, it is assumed herein that the threads allocated for executing an LPAR are consecutively numbered and extend from a base hardware thread number: base[LPAR] to base[LPAR]+M, where M is one less than the number of threads allocated for the LPAR.

Transforming the value of TIR 41 merely requires subtracting base[LPAR] from the thread number in TIR 41. As an example, for a case in which LPAR #1 is allocated hardware threads 0-2 and thus has base[LPAR]=0, and LPAR #2 is allocated hardware threads 3-7, and thus has base[LPAR]=3, when physical thread 5 (of LPAR #2) accesses TIR 41, the logical value that should be returned by hardware or software implementing the present invention is 2 (i.e., physical thread 5 minus base[LPAR], which is 2). Thus the transformation of the physical thread-specific information to logical thread-specific information makes it appear to LPAR #2 that the range of TIR 41 values extends from 0 through 4, which would be the result of exclusive use of a processor core that supports five hardware threads. CR 42 is a register that contains the execution state (live/dead) of each hardware thread, with a bit for each hardware thread supported by processor core 20. Assuming that all bits are numbered from left to right starting at zero, when an LPAR accesses CR 42, the value returned contains a bit for each of the threads allocated for the LPAR, so the physical value of CR 42 is shifted left by base[LPAR] bit positions to obtain the logical value of CR 42 returned to the LPAR and is further masked with a mask value that contains a 1 bit for each hardware thread allocated to the LPAR. So, for the example given above, CR 42, when accessed by a thread of LPAR #2, which has a base[LPAR]=3, would be shifted left by three bit positions and masked. The logical value of CR 42 for LPAR #2 is a 5 bit field that contains bits 3 through 7 of CR 42 that is masked with mask 11111000 to remove information that may have been shifted in from the right. LPAR #1, which has base[LPAR]=0 receives a 3 bit field that contains only bits 0 through 2 of CR 42, which is the un-shifted value of CR 42 (since base[LPAR]=0) masked with mask=11100000 to remove bits corresponding to physical threads 3-7. Transforming the value of inter-thread message delivery status register 43 is the same as the transformation for control register CR 42 described above. Inter-thread message delivery status register 43 contains bits that indicate whether a message has been delivered to another thread. The register contains a bit for each of the other threads, so that messages to each other thread from the thread accessing the register can be tracked. In order to transform the value of inter-thread message delivery status register 43, the actual value of inter-thread message delivery status register 43 is shifted left by the number of bits specified by base[LPAR]. Thus, in the example given above, LPAR #2 receives a value for inter-thread message delivery status register 43 that is a 5-bit field containing the bits for threads 3-7, which is shifted left by 3 bits and masked with a value of 11111000 to remove information that may have been shifted in from the right. Similarly, LPAR #1 receives a value for inter-thread message delivery status register 43 that is a 3-bit field containing the bits for threads 0-2, which is not shifted and is masked with a value of 11100000 to remove information about physical threads 3-7. When sending messages between threads, the program instructions executed by the LPARs use logical thread numbers. If a logical thread number to which a message is sent is outside of the range of thread numbers allocated for executing the LPAR originating the message, an error is reported. Messaging to threads that are not allocated for executing the LPAR are thus blocked to prevent communication with a thread of another LPAR.
Referring now to FIG. 3, details of logical thread information block 50 of FIG. 2 are shown, in accordance with an embodiment of the present invention. While there are many different ways to implement logical thread information block 50, the circuit depicted in FIG. 3 provides one example. Within logical thread information block 50, hardware thread-dependent information status registers are represented by a register 51 and it is understood that the inputs outputs and circuits required to perform the transformations described above will be duplicated as needed for each such status register 51. A selector 53 selects the output of status register 51 except when status register 51 is being accessed by a non-hypervisor process (control signal/hyp=1). Logical-AND gate 54 provides the selection signal to selector 53, which, when status register 51 is accessed by a non-hypervisor process, selects the output of transform logic 52, which performs the transformations described above with reference to FIG. 2.
Referring now to FIG. 4, a method of providing hardware thread-dependent status information to LPARs is illustrated in a flowchart, in accordance with an alternative embodiment of the present invention. The method illustrated in FIG. 4 does not require implementation of logical thread information block 50 in processor core 20, and provides an alternative mechanism for transforming the physical hardware thread-dependent register values to values that simulate exclusive use of processor core 20 by each of the LPARs. As illustrated in FIG. 4, when a program accesses a register containing hardware-thread specific information (step 60), if the accessing process is the hypervisor (decision 61), the physical register value is returned (step 62). However, if the accessing process is not the hypervisor (decision 61), i.e., the accessing process belongs to one of the LPARs, a hardware interrupt is triggered to trap the access (step 63). Processor core 20 has programmatic control of the return address to which the interrupt service handler will return and sets the return address to the address of the instruction following the instruction that attempted to access the hardware thread-dependent register. The logical register value is obtained by either programmatically performing operations similar to those performed by the logic described above with reference to FIG. 3, or, the transformation can be performed in advance and maintained every time one of the thread-dependent status information registers is updated in memory, so that the logical hardware thread-dependent register values can be retrieved (step 64) and then returned in response to the access (step 65), which is generally performed by writing the target register or memory location specified by the accessing instruction with the transformed hardware thread dependent information. Until the system is shutdown or optionally if an LPAR actually does have full and exclusive use of the processor core (decision 65), the process of steps 60-65 is repeated.
As noted above, portions of the present invention may be embodied in a computer program product, which may include firmware, an image in system memory or another memory/cache, or stored on a fixed or re-writable media such as an optical disc having computer-readable code stored thereon. Any combination of one or more computer readable medium(s) may store a program in accordance with an embodiment of the invention. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
In the context of the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
While the invention has been particularly shown and described with reference to the preferred embodiments thereof, it will be understood by those skilled in the art that the foregoing and other changes in form, and details may be made therein without departing from the spirit and scope of the invention.

## Claims

1. A method of providing hardware thread-specific information in a multi-threaded processor supporting a number of hardware threads for executing processes within multiple logical partitions, the method comprising:
maintaining the hardware thread specific information in an internal register circuit within the multi-threaded processor;
a currently-executing one of the processes detecting access to the hardware thread-specific information;
control logic within the processor determining whether or not a privilege level of the currently-executing process indicates that the currently-executing process is a process within a given one of the multiple logical partitions; and
responsive to the control logic within the processor determining that the privilege level of the currently-executing process indicates that the currently-executing process is a process within a given one of the multiple logical partitions not having full access to the hardware thread-specific information, the control logic within the processor selectively transforming the hardware thread-specific information to generate a transformed register value that indicates exclusive use of the multi-threaded processor by hardware threads executed for processes of the given logical partition, while masking hardware-thread specific information present in the internal register circuit corresponding to one or more hardware threads of the multi-threaded processor that are assigned to execute processes of another logical partition other than the given logical partition, and responding to the access with the transformed register value.

2. The method of claim 1, wherein the determining further determines that the privilege level of the currently-executing process corresponds to a hypervisor that manages the multiple logical partitions, and wherein the method further comprises responsive to determining that the currently-execution process is a process of the hypervisor, formatting the hardware thread-specific information in a manner that shows all of the hardware thread-specific information in the internal register circuit for all of the number of hardware threads supported by the multi-threaded processor.

3. The method of claim 1, wherein the transforming is performed by a circuit comprising:
a logic block that generates the a logical register value from the hardware thread-specific information in the internal register circuit to simulate the exclusive use of the multi-threaded processor by the given partition, wherein the logical register value differs from an actual value in the internal register circuit; and
a data selector coupled to the logic block that selects an output of the logic block to provide the logical register value as the transformed register value to the currently-executing process in response to the access.

4. The method of claim 1, wherein the formatting is performed by:
generating a trap interrupt when the access to the hardware thread-specific information is detected by the detecting;
transforming, by the multi-threaded processor executing an interrupt service routine that services the trap interrupt, the hardware thread-specific information in the internal register circuit to simulate the exclusive use of the multi-threaded processor by the given partition to generate a logical register value that is different than an actual value in the internal register circuit; and
replacing a return value for the access to the hardware thread-specific information with the logical register value.

5. The method of claim 1, wherein the hardware thread-specific information is the number of hardware threads supported by the multi-threaded processor, and wherein the transformed register value contains a quantity of the number of the hardware threads that are assigned to the given partition instead of the number of hardware threads supported by the multi-threaded processor.

6. The method of claim 1, wherein the hardware thread-specific information is a value dependent on a logical hardware thread number of a particular hardware thread assigned to the given partition and specified by the access, and wherein the transforming comprises:
generating an actual hardware thread number from the logical hardware thread number;
retrieving the hardware thread-specific information for the particular hardware thread using the actual hardware thread number; and
including the retrieved hardware thread-specific information in the transformed register value.

7. A multi-threaded processor core, comprising:
one or more execution units for executing instructions of multiple hardware threads;
an instruction fetch unit for fetching the instructions of the multiple hardware threads;
an instruction dispatch unit for dispatching the instructions of the multiple hardware threads to the execution units;
a first register circuit containing hardware thread-specific information;
a logic circuit for determining whether or not a privilege level of a process accessing the first register circuit indicates that the process has full access to thread-specific information contained in the first register circuit, and responsive to determining that process does not have full access to the thread-specific information, selectively transforming the hardware thread-specific information to a logical representation of the hardware thread-specific information to reflect exclusive use of the multi-threaded processor core by hardware threads executed for processes of a given logical partition executed by the multi-threaded processor core to generate a transformed register value, while masking hardware-thread specific information present in the first register circuit corresponding to one or more hardware threads of the multi-threaded processor core that are assigned to execute processes of another logical partition other than the given logical partition, and presenting the transformed register value in response to the access.

8. The multi-threaded processor core of claim 7, wherein an output of the logic circuit is presented in response to the access when the first register circuit is accessed at a privilege level lower than a hypervisor privilege level, and wherein a value of the first register circuit is presented directly in response to the access when the first register circuit is accessed at the hypervisor privilege level.

9. The multi-threaded processor core of claim 8, further comprising a data selector for selecting the output of the logic circuit when the first register circuit is accessed from the privilege level lower than the hypervisor privilege level and selecting the first register circuit when the first register circuit is accessed from the hypervisor privilege level.

10. The multi-threaded processor core of claim 7, wherein the hardware thread-specific information is the number of hardware threads supported by the multi-threaded processor core, and wherein the logical representation of the hardware thread-specific information is a number of hardware threads assigned to the given logical partition.

11. The multi-threaded processor core of claim 7, wherein the hardware thread-specific information is a value dependent on a logical hardware thread number of a particular hardware thread assigned to the given logical partition and specified when accessing the first register circuit, and wherein the logic circuit generates an actual hardware thread number from the logical hardware thread number, retrieves the hardware thread-specific information for the particular hardware thread using the actual hardware thread number, and includes the retrieved hardware thread-specific information in the transformed register value.

12. A computer system comprising:
a memory for storing program instructions and data values; and
a multi-threaded processor coupled to the memory for executing the program instructions, wherein the multi-threaded processor comprises one or more execution units for executing instructions of multiple hardware threads, an instruction fetch unit for fetching the instructions of the multiple hardware threads, an instruction dispatch unit for dispatching the instructions of the multiple hardware threads to the execution units, a first register circuit containing hardware thread-specific information, and a logic circuit for determining whether or not a privilege level of a process accessing the first register circuit indicates that the process has full access to the thread-specific information contained in the first register circuit, and responsive to determining that process does not have full access to the thread-specific information, selectively transforming the hardware thread-specific information to a logical representation of the hardware thread-specific information to reflect exclusive use of the multi-threaded processor by hardware threads executed for processes of a given logical partition executed by the multi-threaded processor to generate a transformed register value, while masking hardware-thread specific information present in the first register circuit corresponding to one or more hardware threads of the multi-threaded processor that are assigned to execute processes of another logical partition other than the given logical partition, and responding to the access with the transformed register value.

13. The computer system of claim 12, wherein an output of the logic circuit is selected when the first register circuit is accessed at a privilege level lower than a hypervisor privilege level.

14. The computer system of claim 13, wherein the multi-threaded processor further comprises a data selector for selecting the output of the logic circuit when the first register circuit is accessed from the privilege level lower than the hypervisor privilege level and selecting the first register circuit when the first register circuit is accessed from the hypervisor privilege level.

15. The computer system of claim 12, wherein the hardware thread-specific information is the number of hardware threads supported by the multi-threaded processor, and wherein the logical representation of the hardware thread-specific information is a number of hardware threads assigned to the given logical partition.

16. The computer system of claim 12, wherein the hardware thread-specific information is a value dependent on a logical hardware thread number of a particular hardware thread assigned to the given logical partition and specified when accessing the first register circuit, and wherein the logic circuit generates an actual hardware thread number from the logical hardware thread number, retrieves the hardware thread-specific information for the particular hardware thread using the actual hardware thread number, and includes the retrieved hardware thread-specific information in the transformed register value.

17. A computer program product comprising a computer-readable storage medium that is not signal or propagating wave storing program instructions for execution by a computer system, wherein the program instructions are program instructions of a hypervisor for managing multiple logical partitions executing within a processor core, wherein the program instructions comprise:
program instructions of an interrupt handler to, responsive to a trap interrupt generated upon access to an internal register circuit of a processor integrated circuit that contains hardware-thread specific information, transform the hardware thread-specific information in the internal register circuit to reflect an exclusive use of the processor core by a given logical partition by generating a logical register value that is different than an actual value in the internal register circuit; and
program instructions of the interrupt handler to replace a return value for the access to the internal register circuit containing hardware thread-specific information with the logical register value, wherein the hardware thread-specific information is a value dependent on a logical hardware thread number of a particular hardware thread assigned to the given logical partition and specified by the access to the internal register circuit, and wherein the program instructions of the interrupt handler that transform the hardware thread-specific information in the internal register circuit comprise program
instructions for generating an actual hardware thread number from the logical hardware thread number, and retrieving the hardware thread-specific information for the particular hardware thread using the actual hardware thread number, and wherein the program instructions that replace the return value replace the return value with the retrieved hardware thread-specific information.

18. The computer program product of claim 17, wherein the hardware thread-specific information is the number of hardware threads supported by the processor core, and wherein the program instructions of the interrupt handler that transform the hardware thread-specific information in the internal register circuit return a quantity of the number of the hardware threads that are assigned to the given logical partition as the logical register value.

19. A computer system comprising:
a memory for storing program instructions and data values; and
a processor coupled to the memory for executing the program instructions, wherein the program instructions are program instructions of a hypervisor for managing multiple logical partitions executing within the processor, wherein the program instructions comprise program instructions of an interrupt handler to, respo trap interrupt generated upon access to a internal register circuit of the processor that contains hardware-thread specific information by a process not having full access to the hardware-thread specific information, selectively transform the hardware thread-specific information in the internal register circuit to reflect an exclusive use of the processor core by a given logical partition by generating a logical register value that is different than an actual value in the internal register circuit, and program instructions of the interrupt handler to replace a return value for the access to the internal register circuit containing the hardware thread-specific information with the logical register value, wherein the hardware thread-specific information is a value dependent on a logical hardware thread number of a particular hardware thread assigned to the given logical partition and specified by the access to the internal register circuit, and wherein the program instructions of the interrupt handler that transform the hardware thread-specific information in the internal register circuit comprise program instructions for generating an actual hardware thread number from the logical hardware thread number, and retrieving the hardware thread-specific information for the particular hardware thread using the actual hardware thread number, and wherein the program instructions that replace the return value replace the return value with the retrieved hardware thread-specific information.

20. The computer system of claim 19, wherein the hardware thread-specific information is the number of hardware threads supported by the multi-threaded processor, and wherein the program instructions that transform return a quantity of the number of the hardware threads that are assigned to the given logical partition as the logical register value.