Abstract: Technologies for system management interrupt (“SMI”) handling include a number of processor cores configured to enter a system management mode (“SMM”) in response to detecting an SMI. The first processor core to enter SMM and acquire a master thread lock sets an in-progress flag and executes a master SMI handler without waiting for other processor cores to enter SMM. Other processor cores execute a subordinate SMI handler. The master SMI handler may direct the subordinate SMI handlers to handle core-specific SMIs. The multi-core processor may set an SMI service pending flag in response to detecting the SMI, which is cleared by the processor core that acquires the master thread lock. A processor core entering SMM may immediately resume normal execution upon determining the in-progress flag is not set and the service pending flag is not set, to detect and mitigate spurious SMIs. Other embodiments are described and claimed.

Abstract: Methods, systems and computer program products are disclosed for enhanced system boot processing that is faster to launch an operating system, as certain devices such as user input hardware devices may not be initialized unless it is determined that a user-interruption to the boot process is likely. That is, although an interface for the devices is exposed, no initialization occurs unless a call to the interface occurs. Other embodiments are described and claimed.

Abstract: Technologies for system management interrupt (“SMI”) handling include a number of processor cores configured to enter a system management mode (“SMM”) in response to detecting an SMI. The first processor core to enter SMM and acquire a master thread lock sets an in-progress flag and executes a master SMI handler without waiting for other processor cores to enter SMM. Other processor cores execute a subordinate SMI handler. The master SMI handler may direct the subordinate SMI handlers to handle core-specific SMIs. The multi-core processor may set an SMI service pending flag in response to detecting the SMI, which is cleared by the processor core that acquires the master thread lock. A processor core entering SMM may immediately resume normal execution upon determining the in-progress flag is not set and the service pending flag is not set, to detect and mitigate spurious SMIs. Other embodiments are described and claimed.

Abstract: Methods, systems and computer program products are disclosed for enhanced system boot processing that is faster to launch an operating system, as certain devices such as user input hardware devices may not be initialized unless it is determined that a user-interruption to the boot process is likely. That is, although an interface for the devices is exposed, no initialization occurs unless a call to the interface occurs. Other embodiments are described and claimed.

Abstract: When transitioning from sleep mode to active mode, a processing system loads first stage resume content and second stage resume content into a volatile memory of the processing system. The first stage resume content may contain contextual data for a first program that was in use before the processing system transitioned to sleep mode. The second stage resume content may contain contextual data for another program that was in use before the processing system transitioned to sleep mode. The processing system may provide a user interface for the first program before all of the second stage resume content has been loaded into the volatile memory. Other embodiments are described and claimed.

Abstract: An embodiment of the present invention is a technique to process an input/output (I/O) transaction. An emulated device driver in a guest partition interacts with a virtual machine (VM) manager in processing an input/output (I/O) transaction on behalf of an application via an operating system (OS). The I/O transaction is between the application and a device. A device emulator in a service partition communicatively coupled to the emulated device driver interacts with the VM manager in processing the I/O transaction on behalf of a device specific driver via the OS. The device specific driver interfaces to the device.

Abstract: Systems and methods provide for emulating a host architecture in guest firmware. One aspect of the systems and methods comprises determining whether an emulated instruction would cause a transition into a legacy mode. A current execution context is converted into a legacy mode context, and the firmware emulator proceeds to a group of legacy mode instructions in a native mode for the processor. The firmware emulator detects an end instruction and converts the legacy context back to the guest firmware context.

Abstract: A method, apparatus and system enable bi-directional communications between a virtual machine monitor (“VMM”) and an Advanced Configuration & Power Interface (“ACPI”) compliant guest operating system. In one embodiment, a virtual machine (“VM”) may be designated as the owner of the host platform (“Policy VM”). The Policy VM may communicate with the VMM to control all configuration and power management decisions on the platform.

Abstract: In some embodiments, the invention involves saving limited context information when transitioning between virtual machines. A predetermined set of instructions and events cause a trap. A bit or flag is set to indicate that the event has occurred within a virtual machine. The virtual machine monitor determines whether specific register sets must be saved or restored upon a context switch, based on whether the flag has been set. Other embodiments are described and claimed.

Abstract: A method and related apparatuses facilitate the compression of firmware modules that follow a portable executable (PE) format. An example method includes an operation of storing a firmware module in memory, wherein the firmware module follows a PE format, thus having subdivisions that include an MS-DOS header. The method also includes an operation of flattening the firmware module by replacing existing content within at least one field within the MS-DOS header with fill data that is more compressible than the existing content. For example, fill data may be loaded into an MS-DOS stub field within the MS-DOS header. Alternatively, the method may flatten the firmware module by ensuring that fill data occupies all fields within the MS-DOS header except for an lfanew field and an e-magic field. In some embodiments, additional or alternative operations to flatten the firmware module may be performed, such as loading fill data into one or more fields within an optional file header of the firmware module.

Abstract: Systems and methods provide for emulating a host architecture in guest firmware. One aspect of the systems and methods comprises determining whether an emulated instruction would cause a transition into a legacy mode. A current execution context is converted into a legacy mode context, and the firmware emulator proceeds to a group of legacy mode instructions in a native mode for the processor. The firmware emulator detects an end instruction and converts the legacy context back to the guest firmware context.

Abstract: When transitioning from sleep mode to active mode, a processing system loads first stage resume content and second stage resume content into a volatile memory of the processing system. The first stage resume content may contain contextual data for a first program that was in use before the processing system transitioned to sleep mode. The second stage resume content may contain contextual data for another program that was in use before the processing system transitioned to sleep mode. The processing system may provide a user interface for the first program before all of the second stage resume content has been loaded into the volatile memory. Other embodiments are described and claimed.

Abstract: Provided are a method, system and program for effecting a processor operating mode change to execute device code. A processor receives a call while the processor is operating in a first mode, wherein the call is made to effect execution of device code to control a device. The processor determines whether the call is intended to change a processor operating mode from the first mode to a second mode. The state of the processor is selectively changed to a second mode in which the processor executes second mode instructions loaded in a protected section of memory inaccessible to an operating system in response to determining that the call is intended to change the processor operating mode. The second mode instructions execute the device code to control the device.

Abstract: Systems and methods provide for emulating a host architecture in guest firmware. One aspect of the systems and methods comprises determining whether an emulated instruction would cause a transition into a legacy mode. A current execution context is converted into a legacy mode context, and the firmware emulator proceeds to a group of legacy mode instructions in a native mode for the processor. The firmware emulator detects an end instruction and converts the legacy context back to the guest firmware context.

Abstract: When transitioning from sleep mode to active mode, a processing system loads first stage resume content and second stage resume content into a volatile memory of the processing system. The first stage resume content may contain contextual data for a first program that was in use before the processing system transitioned to sleep mode. The second stage resume content may contain contextual data for another program that was in use before the processing system transitioned to sleep mode. The processing system may provide a user interface for the first program before all of the second stage resume content has been loaded into the volatile memory. Other embodiments are described and claimed.

Abstract: During a process of transitioning a processing system from sleep mode to active mode, system firmware of the processing system may automatically determine whether an initialization task has been assigned to a component other than system firmware, based on data obtained from a resume descriptor stored in nonvolatile storage of the processing system. The system firmware may skip the initialization task if the initialization task has been assigned to a component other than the system firmware. For example, in one embodiment, the system firmware may determine whether the resume descriptor identifies one or more memory ranges. If so, the system firmware may forego initialization of at least one memory range identified in the resume descriptor when initializing a random access memory (RAM) of the processing system. Other embodiments are described and claimed.

Abstract: A method and apparatus to execute a pre-boot application within an emulated pre-boot environment to test functionality of the pre-boot application. The emulated pre-boot environment is executed within a user mode of an operating system (“OS”) during an OS runtime of the processing system. The pre-boot application interacts with a hardware device of the processing system via a kernel proxy agent. The kernel proxy agent executes in a kernel mode of the OS.

Abstract: In one embodiment a method includes accessing a hardware specific module with a request to perform an unmodified I/O (input/output) operation. The method also includes the hardware specific module accessing a processor specific module with a modified request to perform the I/O operation, the modified request suitable for use with a specific hardware component. The method further includes the processor specific module performing the modified I/O operation with the specific hardware component. The method may further include breaking operations into sub-operations that accomplish part of the operation, and use of transactions that may require multiple operations. Apparatus are also disclosed for implementing the method.

Abstract: An alternative boot methodology that begins with legacy-free firmware allows the peaceful coexistence of legacy-free and legacy option ROMs in a system. Legacy-free firmware provides a legacy-free boot path from system power up to operating system loading. This legacy-free boot path is independent of any legacy firmware. A legacy-free boot manager boots from an ordered list of OS loaders. If a legacy boot option is available, legacy-free drivers that have already been loaded may be stopped, and a legacy boot using legacy firmware may be initiated, without having to reboot the system.

Abstract: A method and apparatus for making and using a flexible hardware interface In one embodiment, the method includes accessing a hardware specific module with a request to perform an unmodified I/O (input/output) operation. The method also includes the hardware specific module accessing a processor specific module with a modified request to perform the I/O operation, the modified request suitable for use with a specific hardware component. The method further includes the processor specific module performing the modified I/O operation with the specific hardware component. The method may further include breaking operations into sub-operations that accomplish part of the operation, and use of transactions that may require multiple operations. Apparatus are also disclosed for implementing the method.