Platform Controller Reset Port Emulation for Virtual Machines
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In computer systems implementing virtualization, emulating a keyboard controller reset port using a hypervisor consumes processor resources and can be slowed down by malicious or malfunctioning virtual machines issuing unnecessary writes to the reset port, affecting system performance.
Innovation Solution
Offloading reset port emulation to a platform controller separate from the hypervisor, which provides a secure and efficient way to handle reset port activations by using PCI functions and SR-IOV to bypass the hypervisor's emulation layer, reducing processor resource consumption and managing reset operations independently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the hypervisor emulates the keyboard controller reset port, then the virtual machine can access the reset port, but the processor resources are consumed and system performance is reduced
Solution Approach 1:
The patent extracts the keyboard controller emulation functionality from the hypervisor and relocates it to a dedicated platform controller. This separation removes the performance burden from the hypervisor while preserving reset port functionality for virtual machines, directly resolving the contradiction between adaptability and productivity.
Solution Approach 2:
The platform controller acts as an intermediary between the virtual machines and the system reset functionality. It receives reset port access requests from virtual machines and handles them without requiring hypervisor involvement, thus maintaining accessibility while improving system performance by eliminating the emulation overhead.
2Adaptability or versatility
If malicious or malfunctioning virtual machines issue unnecessary writes to the reset port, then the reset port is activated, but the hypervisor emulation is slowed down and system performance is affected
Solution Approach 1:
By extracting the reset port emulation from the hypervisor to a platform controller, the system isolates the reset handling functionality. This prevents malicious or malfunctioning VMs from directly impacting hypervisor performance, as the platform controller independently manages reset operations without requiring hypervisor intervention.
Solution Approach 2:
The platform controller provides self-service capability for handling reset port operations. It independently processes reset requests from virtual machines without requiring hypervisor mediation, thereby improving system reliability by preventing hypervisor slowdowns while maintaining full reset functionality.
3Adaptability or versatility
If the hypervisor handles reset port operations, then virtual machines can reset, but processor overhead increases
Solution Approach 1:
The patent extracts reset port emulation from the hypervisor and places it in a platform controller, eliminating the need for processor-intensive emulation operations. This maintains virtual machine reset capability while significantly reducing processor overhead and energy consumption.
Solution Approach 2:
The patent replaces the software-based hypervisor emulation mechanism with a hardware-based platform controller implementation. This substitution eliminates the computational overhead of software emulation while preserving reset functionality, thereby reducing processor overhead and energy usage.
Data Source
AI summary
In some examples, a storage medium stores information relating to reset ports associated with respective virtual machines (VMs) of a plurality of VMs. A controller detects, based on the information, an activation of a first reset port associated with a first VM of the plurality of VMs. In response to the detecting, the controller provides an indication of the activation of the first reset port to a hypervisor that is separate from the controller, the indication to cause the hypervisor to reset the first VM.