The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Aug. 24, 2010
Filed:
Jun. 14, 2004
John Worley, Fort Collins, CO (US);
Daniel J. Magenheimer, Fort Collins, CO (US);
Chris D. Hyser, Victor, NY (US);
Robert D. Gardner, Fort Collins, CO (US);
Thomas W. Christian, Fort Collins, CO (US);
Bret Mckee, Fort Collins, CO (US);
Christopher Worley, Fort Collins, CO (US);
William S. Worley, Jr., Aurora, CO (US);
John Worley, Fort Collins, CO (US);
Daniel J. Magenheimer, Fort Collins, CO (US);
Chris D. Hyser, Victor, NY (US);
Robert D. Gardner, Fort Collins, CO (US);
Thomas W. Christian, Fort Collins, CO (US);
Bret McKee, Fort Collins, CO (US);
Christopher Worley, Fort Collins, CO (US);
William S. Worley, Jr., Aurora, CO (US);
Hewlett-Packard Development Company, L.P., Houston, TX (US);
Abstract
In various embodiments of the present invention, execution-state transitions occur in a first portion of a system, and a cumulative execution state for each process is maintained by a second portion of the system so that, when a second-portion routine is called, the second-portion routine can determine whether or not the current execution state is suitable for execution of the second-portion routine. In various embodiments, a callpoint log, allocated and maintained for each process, stores the cumulative execution state for the process. In one embodiment, the first portion is an operating system, and the second portion is a secure kernel, with the cumulative execution state used by the secure kernel to prevent unauthorized access by erroneously or maliciously invoked operating-system routines to secure kernel routines. In another embodiment, the cumulative execution state is used as a debugging tool by the second-portion routines to catch errors in the implementation of the first-portion routines.