Method, system and apparatus for handling events for partitions in a socket with sub-socket partitioning

• US 8,635,380 B2
• Filed: 11/07/2008
• Issued: 01/21/2014
• Est. Priority Date: 12/20/2007
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Harikumar, Ajay, Thomas, Tessil, Simon, Biju Puthur
• Primary Examiner(s): Wong, Titus
• Application Number:
  US12/291,272
• Publication Number:
  US 20090164739A1
• Time in Patent Office: 1,901 Days
• Field of Search: 710/18
• US Class Current: 710/18
• CPC Class Codes: G06F 12/0806 Multiuser, multiprocessor or multiprocessing cache systems
• CPC Class Codes: G06F 2209/543 Local
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

In one aspect, the issues of events that may impact one or more partitions of sub-socket partitioning in one or more sockets can be handled. Specifically, events for partitions can be handled in a socket with sub-socket partitioning, wherein the events may include reset, interrupts, errors and reliability, availability, and serviceability (RAS) management.

Claims

1. A method comprising:

defining a plurality of partitions, within a processor socket including, configured on a die, a plurality of cores, a memory controller, a first level ring interconnect to interconnect the plurality of cores with a distributed last level cache (LLC), a fabric interface, a home agent coupled to the memory controller, and a second level interconnect to interconnect the home agent and the fabric interface for sub-socket partitioning;

receiving an event, wherein the event is a reset, interrupt, error, or reliability, availability, and serviceability (RAS) condition, wherein the reset is a partition specific reset of a specific partition; and

isolating the event to a partition within the processor socket.

2. The method of claim 1 wherein the partition specific reset is caused by a system service processor (SSP) coupled to the processor socket.

3. The method of claim 2 wherein the partition specific reset is performed by the SSP by first setting a reset enable bit of an impacted shared resource and then asserting a global system reset, wherein the specific partition includes at least one core and at least one input/output resource that are quiesced before asserting the global system reset.

4. The method of claim 2 wherein the partition specific reset is performed by software in a first partition initiating a write operation into a register into an input/output controller (ICH), wherein the write operation is trapped and sent to a first unique register of the ICH for the first partition, and to cause initiation of assertion of a first platform reset wire coupled to the SSP to cause the SSP to initiate the reset for the first partition.

5. The method of claim 1 wherein the partition specific reset is performed by an input/output hub (IOH) activating a reset wire to the processor socket and to an input/output device.

6. The method of claim 1 wherein the error is classified into either a partition specific notice or a system wide notice.

7. A system comprising:

a processor configured on a die within a socket and having a plurality of cores, a first level ring interconnect to couple the plurality of cores to a distributed last level cache (LLC), a fabric interface, a home agent coupled to a memory controller, and a second level interconnect to interconnect the home agent and the fabric interface;

a dynamic random access memory, coupled to the socket, to receive requests from the processor;

the processor to support sub-socket partitioning of the processor to utilize at least a first operating system and a second operating system within a first partition and a second partition;

the processor to receive an event and to isolate the event to either the first partition or the second partition within the socket, wherein the event is a reset, interrupt, error, or reliability, availability, and serviceability (RAS) condition, wherein the reset is a partition specific reset; and

a system service processor (SSP) coupled to the processor.

8. The system of claim 7 wherein the SSP is to facilitate the partition specific reset by first setting a reset enable bit of an impacted shared resource and then asserting a global system reset, wherein the specific partition includes at least one core and at least one input/output resource that are quiesced before asserting the global system reset.

9. The system of claim 7 further comprising an interrupt logic, coupled to the processor, to facilitate an interrupt, the interrupt logic including a mapping table to map a first tuple of a message signaled interrupt (MSI) identifier, an addressing mode, and an address to a second tuple of a node identifier, a partition identifier and an interrupt logic identifier.

10. The system of claim 9 wherein the interrupt logic is to issue the message with a partition identifier to determine whether a receiving core is in the same socket or a different socket.

11. A processor comprising:

a processor socket including, on a die;

a plurality of processor cores, a memory controller, a first level ring interconnect to interconnect the plurality of processor cores with a distributed last level cache (LLC), a fabric interface, a home agent coupled to a memory controller, and a second level interconnect to interconnect the home agent and the fabric interface, wherein the plurality of processor cores support sub-socket partitioning that allows a plurality of partitions within the processor socket, each of the partitions to execute a different operating system;

the processor to receive an event comprising a reset, interrupt, error, or reliability, availability, and serviceability (RAS) condition, wherein the reset is a partition specific reset of a specific partition; and

wherein an interrupt logic is coupled to the processor, to facilitate handling of the interrupt by isolating the interrupt to a partition of the plurality of partitions based at least in part on information in a mapping table of the interrupt logic.

12. The processor of claim 11 wherein the interrupt logic is to issue a message with a partition identifier to determine whether a receiving core is in the processor socket or a second processor socket.

13. The processor of claim 11 wherein the interrupt logic is to facilitate the interrupt.