Driver framework component for synchronizing interactions between a multi-threaded environment and a driver operating in a less-threaded software environment

• US 7,406,698 B2
• Filed: 12/30/2003
• Issued: 07/29/2008
• Est. Priority Date: 12/30/2003
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Richardson, John J.
• Primary Examiner(s): An; Meng-Ai
• Assistant Examiner(s): WU, QING YUAN
• Application Number:
  US10/749,787
• Publication Number:
  US 20050144330A1
• Time in Patent Office: 1,673 Days
• Field of Search: 719/315, 719/318, 719/321, 719/328, 710/200, 707/8
• US Class Current: 719/321
• CPC Class Codes: G06F 9/526 Mutual exclusion algorithms
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/545 where tasks reside in different layers, e.g. user- and kernel-space

Abstract

The present invention relates to a system and methodology to facilitate automatic interactions between a highly threaded software environment such as an operating system kernel and a module operating in a less threaded environment. This is achieved by supplying adapter objects that employ various automated locking components to synchronize interactions between the environments such as processing of events or interrupts that may be generated in the system. In one aspect, a driver management system is provided that includes a driver framework component (DFC) that is separate from a driver or other type module, wherein the DFC generates objects that facilitate seamless interactions between the driver and a highly threaded system. A presentation component associated with the DFC selectively exposes objects to the driver in a multi-threaded environment.

Claims

1. A computer storage medium having stored thereon a driver management system executable by a processor comprising:

a driver framework component (DFC) that is separate from a driver, the DFC comprising;

a presentation component that selectively exposes adapter objects to the driver in a multi-threaded environment, the adapter objects synchronize interactions between the driver and the multi-threaded environment according to a hierarchical locking model selected by the driver at configuration time, the hierarchical locking model determines a primary synchronization object level at which locks are applied during synchronization, the available synchronization object levels include at least one of a driver level, a device level, or a queue level.

2. The driver management system of claim 1, further comprising an operating system kernel that operates or performs in a multi-threaded software environment.

3. The driver management system of claim 2, the driver operates in a less-threaded software environment than the operating system kernel.

4. The driver management system of claim 1, at least one of the adapter objects includes internal state data and one or more sets of locks for managing interactions between the driver and the DFC.

5. The driver management system of claim 4, the at least one adapter object includes an internal object state lock that provides synchronization for modifications to the internal state data.

6. The driver management system of claim 5, the internal object state lock is acquired and released for short time intervals in response to an event from a system that modifies the at least one adapter object, or an API call from a software module or driver.

7. The driver management system of claim 5, the DFC automatically optimizes the sharing of internal object state locks between its internal I/O paths.

8. The driver management system of claim 4, the at least one adapter object includes a presentation lock that is acquired when events are presented through event handler callbacks into a less threaded software module.

9. The driver management system of claim 8, when the event handler callback returns, the presentation lock is automatically released.

10. The driver management system of claim 1, at least one adapter object employs a series of reference counts, request deferrals, or other programming components to facilitate object lifetime and event exposure to a less threaded software module.

11. The driver management system of claim 1, the adapter objects are employed for request dispatch, locking, or synchronization.

12. The driver management system of claim 1, the DFC automatically manages synchronization and race conditions that occur in a driver environment.

13. The driver management system of claim 12, the DFC provides a flexible configuration model in which a driver designer can select an amount of synchronization desired depending on device requirements or performance goals.

14. The driver management system of claim 1, the driver registers a set of callback functions to the adapter objects during initialization of the driver.

15. The driver management system of claim 1, the DFC raises events that occur such as Delayed Procedure Calls (DPC'"'"'s), I/O cancellation events, plug and play events, or power management events.

16. The driver management system of claim 1, at least one adapter object is associated with at least one of a request object, a driver object, a device object, and a queue object.

17. The driver management system of claim 16, at least one of the objects is owned or derived from at least one other object.

18. The driver management system of claim 1, at least one adapter object including at least one of a spinlock, a shared lock, and a FAST_MUTEX.

19. The driver management system of claim 1, at least one adapter object allows the driver to specify an optional context memory allocation to be associated with the adapter object, the driver stores its primary data structure in the context memory to facilitate interaction with the data structure according to the DFC'"'"'s hierarchical locking model.

20. The driver management system of claim 1, the hierarchical locking model includes a non-synchronization model that places the entire burden of synchronization on the driver.

21. The driver management system of claim 1, further comprising at least one of a synchronous and an asynchronous threading model.

22. The driver management system of claim 1, further comprising at least one of a lock for inter-object communications, a lock verifier, a lock organizer, and an automatic child-locking component.