Diagnostic architecture for use with an interface between an operating system and platform firmware

• US 6,938,243 B1
• Filed: 09/22/2000
• Issued: 08/30/2005
• Est. Priority Date: 09/22/2000
• Status: Expired due to Term

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Stone, Roderick W., Zeevi, Josef
• Primary Examiner(s): Ingberg, Todd
• Assistant Examiner(s): Nahar, Qamrun
• Application Number:
  US09/668,316
• Time in Patent Office: 1,803 Days
• Field of Search: 717/124, 717/126, 717/105, 717/175, 714/27
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3672 Test management

Abstract

A method performed by a computer system is provided. The method includes detecting a test module interface associated with a test module and calling a function identified by the test module interface to cause a test configuration of the test module to be created.

Claims

1. A method performed by a computer system comprising:

providing a test module for dynamically reinstalling an associated test module interface at anytime without rebooting the computer system, in response to a device change associated with the test module;

in response, unloading the test module associated with the changed device and causing its test module interface to be reinstalled without rebooting the computer system;

using a registration module to register uses of the test module by a plurality of programs so that no other program attempts can access information associated with the test module after it unloads;

in response to the test module seeking to unload, accessing the registration module to determine what other programs are registered as using the test module;

notifying each of the programs to stop using the test module;

each program responding that they have stopped using the test module or are still using the test module;

the test module causing itself to unload in response to programs responding that using the test module is stopped; and

the test module cancelling unloading in response to programs responding that the test module is being used, whereby the test module may unload at a later time.

2. The method of claim 1, further comprising:

calling a function identified by a test module interface to cause a first test configuration of the test module to be created;

detecting a test routine associated with the test module using the first test configuration; and

causing the test routine to be executed.

3. The method of claim 2, further comprising:

in response to detecting the change,

calling the function to cause a second test configuration of the test module to be created.

4. The method of claim 1, further comprising:

registering a use of the test module by a program.

5. The method of claim 4, further comprising:

unloading the test module; and

informing the program of the unloading prior to unloading the test module.

6. The method of claim 5, further comprising:

conveying a defer signal from the program to the test module; and

in response to the defer signal, canceling the unloading of the test module.

7. A computer system comprising:

a processor;

a memory coupled to the processor;

a test module dynamically reinstalling its test module interface at any time without rebooting the computer system, in response to a device change associated with that test module;

in response, the test module associated with the changed device being unloaded and causing its test module interface to be reinstalled without rebooting the computer system;

a registration module being used to register uses of the test module by a plurality of programs so that no other program attempts to access information associated with the test module after it unloads;

means for accessing the registration module to determine what other programs are registered as using the test module;

means for notifying each of the programs to stop using the test module;

means for each program to respond that they have stopped using the test module or are still using the test module;

means for the test module to cause itself to unload in response to programs responding that using the test module is stopped; and

means for the test module to cancel unloading in response to programs responding that the test module is being used, whereby the test module may unload at a later time.

8. The computer system of claim 7, wherein the system:

calls a function identified by a test module interface to cause a first test configuration of the test module to be created;

detects a test routine associated with the test module using the first test configuration; and

causes the test routine to be executed.

9. The computer system of claim 8, wherein the function identified by the test module interface is called to cause a second test configuration of the test module to be created.

10. The computer system of claim 7, wherein a use of the test module by the program is registered.

11. The computer system of claim 10, wherein the test module is unloaded;

and

the program is notified of the unloading prior to unloading the test module.

12. The computer system of claim 11, wherein a defer signal is conveyed from the program to the test module;

and

in response to the defer signal, the unloading of the test module is canceled.