SYSTEMS AND METHODS FOR SECURE HOST RESOURCE MANAGEMENT

• US 20110107355A1
• Filed: 01/10/2011
• Published: 05/05/2011
• Est. Priority Date: 06/30/2005
• Status: Active Grant

• Current Assignee: David M. Durham, Hormuzd M. Khosravi, Priva Rajagopal, Tisson Mathew, Travis Schluessler
• Original Assignee: David M. Durham, Hormuzd M. Khosravi, Priva Rajagopal, Tisson Mathew, Travis Schluessler
• Inventors: Rajagopal, Priva, Mathew, Tisson, Khosravi, Hormuzd M., Schluessler, Travis, Durham, David M.
• Granted Patent: US 8,510,760 B2
• Time in Patent Office: Days
• US Class Current: 719/327
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: G06F 13/387 for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system

Abstract

Systems and methods are described herein to provide for secure host resource management on a computing device. Other embodiments include apparatus and system for management of one or more host device drivers from an isolated execution environment. Further embodiments include methods for querying and receiving event data from manageable resources on a host device. Further embodiments include data structures for the reporting of event data from one or more host device drivers to one or more capability modules.

Claims

1. A method, comprising:

querying at least one host device driver for event types supported by the at least one host device driver;

receiving the event types from the at least one device driver; and

caching the event types in a resource data record repository, where the resource data record repository is stored in an environment that is isolated from the host device.

2. The method of claim 1, wherein the at least one host device driver includes each host device driver on a host device.

3. The method of claim 2, further comprising:

receiving a request from a capability module for an event type;

determining which of the event types cached in the resource data record repository match the request; and

subscribing the capability module to the event types cached in the resource data record that matched the request.

4. The method of claim 3, further comprising receiving from the capability module at least one event threshold for the requested event type.

5. The method of claim 1, wherein the host device driver is a ring 3 software application.

6. The method of claim 1, wherein the host device driver is a ring 0 software application.

7. A machine-readable medium having machine executable instructions contained therein, which when executed perform the following operations:

receiving event management data from a host device driver;

determining if the event management data exceeds a threshold; and

sending the event management data to at least one capability module if the event exceeds a threshold value related to the event management data previously received from the capability module, where the at least one capability module is executed within an environment isolated from the host device driver.

8. The machine-readable medium of claim 7, wherein the event management data includes an event resource data record related to an event on a host device.

9. The machine-readable medium of claim 7, wherein the threshold is set by the at least one capability module prior to receiving the event management data from the host device driver.

10. The machine-readable medium of claim 7, wherein the host device driver is to communicate over a direct memory access channel.

11. The machine-readable medium of claim 7, wherein the host device driver is a ring 3 software application.

12. The machine-readable medium of claim 7, wherein the host device driver is to communicate with a mailbox interface module communicatively coupled to the at least one capability module through a management core.

13. The machine-readable medium of claim 7, wherein the host device driver is a ring 3 software application.

14. The machine-readable medium of claim 7, wherein the host device driver is to communicate with a mailbox interface module communicatively coupled to the at least one capability module through a management core.