Accelerator Initialization Protocol for Virtual Machine Resource Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtualized data processing systems that use an accelerator as a common shared resource for multiple applications are inflexible due to static connections between virtual machines and the accelerator, requiring specific drivers and incurring high processing costs for command transfer between operating systems.
Innovation Solution
A method and system for initializing input/output interfaces to a shared accelerator, involving a handshaking protocol between the processor and the accelerator, where capability information is written to a shared storage area, allowing dynamic management of virtual machine connections and eliminating the need for specific drivers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If static connections are used between virtual machines and the accelerator, then device compatibility is ensured, but system flexibility and dynamic management capability deteriorate
Solution Approach 1:
The patent implements dynamic connection management between virtual machines and the accelerator by allowing the hypervisor to dynamically allocate, deallocate, and reconfigure input/output interfaces and virtual machine connections at runtime. This enables the system to adapt to changing workload requirements while maintaining stable operational states during active connections, thus achieving both reliability and flexibility.
Solution Approach 2:
The patent creates a universal interface layer that can handle multiple types of virtual machine connections and accelerator configurations through a common initialization protocol. The hypervisor uses a standardized approach to manage different virtual machine types and accelerator resources, eliminating the need for device-specific static configurations while ensuring broad compatibility.
2Reliability
If specific device drivers are used for each interface type, then interface functionality is ensured, but system complexity and driver management overhead increase
Solution Approach 1:
The patent introduces the hypervisor as an intermediary layer between the virtual machines and the accelerator hardware. The hypervisor implements a standardized initialization protocol that mediates all communication and configuration, eliminating the need for multiple specific device drivers in the virtual machine guest operating systems. This single intermediary handles all interface functionality while simplifying the overall system architecture.
Solution Approach 2:
The hypervisor implements a universal initialization protocol that can handle multiple types of input/output interfaces and accelerator configurations through a single standardized interface. This universal approach replaces the need for multiple device-specific drivers, reducing driver management complexity while maintaining full interface functionality through the hypervisor's centralized control.
3Reliability
If command transfer between two operating systems is implemented, then accelerator access is enabled, but processing cost and system complexity increase
Solution Approach 1:
The patent extracts the command transfer overhead from the guest operating system by implementing direct hypervisor-to-accelerator communication paths. The hypervisor directly manages accelerator access and command submission, eliminating the need for complex inter-operating-system command transfer mechanisms. This extraction of the mediation function to a dedicated layer reduces processing overhead and improves efficiency.
Solution Approach 2:
The hypervisor serves as an efficient intermediary that directly manages accelerator access without requiring complex command transfer between operating systems. By implementing a standardized initialization protocol and direct communication paths, the hypervisor enables accelerator access with minimal processing overhead, improving productivity while maintaining reliable access capability.
4Stability of the object's composition
If fixed partitions are assigned to virtual machines, then connection stability is ensured, but dynamic resource management and flexibility deteriorate
Solution Approach 1:
The patent implements dynamic resource management by allowing the hypervisor to dynamically allocate, reconfigure, and deallocate input/output interfaces and accelerator resources based on changing workload requirements. Virtual machine connections remain stable during active operation, but the system can dynamically adjust allocations without requiring fixed partitions, thus achieving both connection stability and dynamic adaptability.
Solution Approach 2:
The patent uses preliminary initialization through a standardized protocol to establish stable connections before virtual machines begin operation. The hypervisor pre-configures input/output interfaces and establishes connection parameters in advance, ensuring connection stability. However, these connections can be dynamically reconfigured later, enabling flexible resource management while maintaining operational stability.
Data Source
AI summary
A data processing system includes one or more processors that each execute one or more operating systems that include one or more applications; an accelerator that provides a shared resource for a plurality of the applications; a storage area accessible by the processors and the accelerator; and one or more input/output interfaces for control of, or the submission of tasks to, the accelerator. To initialize one of the input/output interfaces, one of the one or more processors is capable of sending a first signal to the accelerator; the accelerator is capable of writing one or more selected pieces of information representative of one or more capabilities of the accelerator to the storage area and sending a second signal to the processor; the processor is capable of reading the one or more selected pieces of information from the storage area; and the accelerator is capable of configuring the input/output interface.