LPC Device Emulation for Concurrent Guest and Host Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing virtualization systems struggle to provide efficient access to low pin count (LPC) hardware devices due to locking schemes that prevent simultaneous access by guest and host operating systems, leading to inefficient resource usage and performance bottlenecks.

Innovation Solution

A virtualization system that emulates LPC devices as PCIe devices within a hypervisor, allowing guest and host processes to send control messages using different address formats, enabling simultaneous access and reducing the need for locking mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If locking schemes are used to prevent simultaneous access to LPC hardware devices by guest and host operating systems, then access conflicts are avoided, but resource usage efficiency deteriorates and performance bottlenecks occur

Engineering Contradiction:
Improveaccess conflict preventionVSAvoidresource usage efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent creates a virtual LPC device that copies the functionality of the physical LPC device within the virtualized environment. This virtual device allows the guest operating system to access LPC hardware resources without directly competing with the host OS for the same physical device, thereby eliminating access conflicts while maintaining reliable device operation and improving overall resource utilization efficiency

Inventive Principle:
Principle #26Copying

2Reliability

If locking schemes are used to control access to LPC hardware devices, then simultaneous access conflicts are prevented, but performance deteriorates due to access bottlenecks

Engineering Contradiction:
Improveaccess conflict preventionVSAvoidaccess speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent introduces a virtual LPC device as an intermediary layer between the guest operating system and the physical LPC hardware device. This intermediary handles all access requests from the guest OS, translating and managing them appropriately without requiring the host OS to impose locking mechanisms. The result is maintained access conflict prevention while significantly improving access speed by eliminating locking overhead and bottlenecks

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If LPC devices are accessed through traditional virtualization methods with locking mechanisms, then access safety is maintained, but resource utilization efficiency deteriorates

Engineering Contradiction:
Improveaccess safetyVSAvoidresource utilization efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the access paths to LPC devices by creating separate virtualization layers for different device types. PCIe devices continue to use traditional address translation methods, while LPC devices are accessed through a dedicated virtual LPC device interface. This segmentation allows safe access control for LPC devices without imposing locking mechanisms on the entire system, thereby maintaining access safety while improving overall resource utilization efficiency

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12596563B2Physical hardware device access via emulation
Publication Date: 2026.04.07 JUNIPER NETWORKS INC
  • US12596563B2 patent drawing
  • US12596563B2 patent drawing
  • US12596563B2 patent drawing

AI summary

A virtualization system may receive, by a physical hardware device driver of a kernel of a guest OS of the virtualization system and from a process of the guest OS, one or more control messages to control a physical hardware device. The virtualization system may determine, by the physical hardware device driver and based on the second-type physical hardware device address included in the one or more control messages, a first-type physical hardware device address associated with the physical hardware device. The virtualization system may update, by the physical hardware device driver, the one or more control messages to include the first-type physical hardware device address, and may send, by the physical hardware device driver and to an emulated physical hardware device of a hypervisor of a host OS of the virtualization system, the one or more control messages.