GATHERING STATE INFORMATION FOR AN APPLICATION AND KERNEL COMPONENTS CALLED BY THE APPLICATION

• US 20090183174A1
• Filed: 01/11/2008
• Published: 07/16/2009
• Est. Priority Date: 01/11/2008
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Subhraveti, Dinesh Kumar
• Granted Patent: US 8,209,707 B2
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: G06F 9/4484 Executing subprograms

Abstract

Provided are a method, system, and article of manufacture for gathering state information for an application and kernel components called by the application. An implementation of a component to execute in a kernel space is instantiated in a user space. An application invokes a call to the component in the kernel space. The call to the component in the kernel space is invoked and an implementation of the component in the user space is invoked to execute the call in the user space. State information related to the execution of the call to the component in the user space to include in checkpoint information for the application is gathered.

Claims

1. A method, comprising:

instantiating an implementation of a component to execute in a kernel space in a user space;

invoking, by an application, a call to the component in the kernel space;

intercepting the call to the component in the kernel space;

invoking an implementation of the component in the user space to execute the call in the user space; and

gathering state information related to the execution of the call to the component in the user space to include in checkpoint information for the application.

2. The method of claim 1, wherein the checkpoint information includes system information related to operations of the application and the execution of the calls to the implementation of the component in the user space, and a state of memory regions used by the application.

3. The method of claim 1, further comprising:

translating the intercepted call to a format compatible with implementation of component in the user space, wherein the translated call is invoked to the implementation of the component.

4. The method of claim 1, wherein the implementation of the component in the user space comprises a subsystem that executes in the user space, and wherein the state information of the subsystem related to the call from the application is gathered for the checkpoint information.

5. The method of claim 1, further comprising:

loading and initializing the application;

loading an agent in response to loading the application, wherein the agent intercepts the application calls to the component in the kernel space and invokes the call to the implementation of the component in the user space.

6. The method of claim 5, wherein the agent instantiates the implementation of the component executing in a kernel space in the user space.

7. The method of claim 5, wherein intercepting the call comprises:

modifying, by the agent, the call made by the application to invoke the implementation of the component in the user space to execute the call in the user space.

8. The method of claim 1, wherein the component comprises a network communication data structure residing in the kernel space that is used to process network communication packets, and wherein the implementation of the component in the user space comprises the network communication data structure in the user space used to process the network communication packets.

9. The method of claim 1, wherein the component comprises a graphics engine residing in the kernel space that is used to calls to a graphics engine to render graphics, and wherein the implementation of the component in the user space comprises a graphics subsystem in the user space used to process the calls to the graphics engine and render graphics.

10. A system, comprising:

at least one processor;

a memory including an application;

a computer program in the memory executed by the processor to perform operations, the operations comprising;

instantiating in the memory an implementation of a component to execute in a kernel space in a user space;

invoking, by the application, a call to the component in the kernel space;

intercepting the call to the component in the kernel space;

invoking an implementation of the component in the user space to execute the call in the user space; and

gathering state information related to the execution of the call to the component in the user space to include in checkpoint information for the application.

11. The system of claim 10, wherein the checkpoint information includes system information related to operations of the application and the execution of the calls to the implementation of the component in the user space, and a state of memory regions used by the application.

12. The system of claim 10, wherein the implementation of the component in the user space comprises a subsystem that executes in the user space, and wherein the state information of the subsystem related to the call from the application is gathered for the checkpoint information.

13. The system of claim 10, further comprising:

loading and initializing the application;

loading an agent in response to loading the application, wherein the agent intercepts the application calls to the component in the kernel space and invokes the call to the implementation of the component in the user space.

14. The system of claim 13, wherein the agent instantiates the implementation of the component executing in a kernel space in the user space.

15. The system of claim 13, wherein intercepting the call comprises:

modifying, by the agent, the call made by the application to invoke the implementation of the component in the user space to execute the call in the user space.

16. The system of claim 10, wherein the component comprises a member of a set of components:

a network communication data structure residing in the kernel space that is used to process network communication packets, and wherein the implementation of the component in the user space comprises the network communication data structure in the user space used to process the network communication packets; and

a graphics engine residing in the kernel space that is used to calls to a graphics engine to render graphics, and wherein the implementation of the component in the user space comprises a graphics subsystem in the user space used to process the calls to the graphics engine and render graphics.

17. An article of manufacture comprising at least one of a computer readable storage medium having code and a hardware device having hardware logic executed to communicate with a memory and an application and perform operations, the operations comprising:

instantiating an implementation of a component in the memory to execute in a kernel space in a user space;

invoking, by the application, a call to the component in the kernel space;

intercepting the call to the component in the kernel space;

invoking an implementation of the component in the user space to execute the call in the user space; and

gathering state information related to the execution of the call to the component in the user space to include in checkpoint information for the application.

18. The article of manufacture of claim 17, wherein the checkpoint information includes system information related to operations of the application and the execution of the calls to the implementation of the component in the user space, and a state of memory regions used by the application.

19. The article of manufacture of claim 17, further comprising:

translating the intercepted call to a format compatible with implementation of component in the user space, wherein the translated call is invoked to the implementation of the component.

20. The article of manufacture of claim 17, wherein the implementation of the component in the user space comprises a subsystem that executes in the user space, and wherein the state information of the subsystem related to the call from the application is gathered for the checkpoint information.

21. The article of manufacture of claim 17, wherein the operations further comprise:

loading and initializing the application; and

loading an agent in response to loading the application, wherein the agent intercepts the application calls to the component in the kernel space and invokes the call to the implementation of the component in the user space.

22. The article of manufacture of claim 21, wherein the agent instantiates the implementation of the component executing in a kernel space in the user space.

23. The article of manufacture of claim 21, wherein intercepting the call comprises:

modifying, by the agent, the call made by the application to invoke the implementation of the component in the user space to execute the call in the user space.

24. The article of manufacture of claim 17, wherein the component comprises a network communication data structure residing in the kernel space that is used to process network communication packets, and wherein the implementation of the component in the user space comprises the network communication data structure in the user space used to process the network communication packets.

25. The article of manufacture of claim 17, wherein the component comprises a graphics engine residing in the kernel space that is used to calls to a graphics engine to render graphics, and wherein the implementation of the component in the user space comprises a graphics subsystem in the user space used to process the calls to the graphics engine and render graphics.