Method and system for maintaining thread-relative metrics for trace data adjusted for thread switches

• US 6,539,339 B1
• Filed: 09/09/1999
• Issued: 03/25/2003
• Est. Priority Date: 12/12/1997
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Berry, Robert Francis, Levine, Frank Eliot, Urquhart, Robert J., Edmark, Ronald OʼNeal
• Primary Examiner(s): WACHSMAN, HAL D
• Application Number:
  US09/393,087
• Time in Patent Office: 1,293 Days
• Field of Search: 702/182-188, 702/119, 702/122, 702/123, 702/176-179, 702/FOR.103, 702/FOR.104, 702/FOR.134, 702/FOR.135, 702/FOR.139, 702/FOR.170, 702/FOR.171, 714/38, 714/45, 717/128, 717/130, 717/124, 717/126, 717/127, 717/131, 717/132, 717/133, 717/116, 712/244
• US Class Current: 702/186
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2201/865 Monitoring of software

Abstract

A method and system for maintaining a thread-relative metric for trace data using device driver support is provided. A profiling process may detect a current event, and in response to the current event, may request an elapsed metric since a preceding event. The profiling process then receives a thread-relative elapsed metric and may output a trace record for the current event in which is stored a metric equal to the received thread-relative elapsed metric. In response to a notification of an occurrence of the current event, a device driver computes the thread-relative elapsed metric by: determining a current thread; retrieving a stored metric for the preceding event of the current thread; obtaining a current metric; and computing the thread-relative elapsed metric as a difference between the current metric and the stored metric.

Claims

1. A method for processing for events detected while profiling all instrumented program executed by a virtual machine in a data processing system, the method comprising the computer-implemented stops of:

in response to an occurrence of current event, receiving a request for a number of bytecodes executed by a thread running in the virtual machine since a preceding event;

computing the number of bytecodes executed by the thread running in the virtual machine since the preceding event; and

returning, in response to the request, the number of bytecodes executed by the thread running in the virtual machine since the preceding event, wherein the step of computing the number of bytecodes executed by the thread running in the virtual machine since the preceding event further includes;

retrieving a stored bytecode count for the thread;

obtaining a current bytecode count for the thread;

computing a difference between the current bytecode count and the stored bytecode count; and

adding the computed difference to the number of bytecodes executed by the thread running in the virtual machine sine the preceding event.

2. The method of claim 1 further comprising:

storing the current bytecode count for subsequent retrieval.

3. A data processing system for processing events detected while profiling an instrumented program executed by a virtual machine in the data processing system, the data processing system comprising:

receiving means for receiving, in response to an occurrence of a current event, a request for a number of bytecodes executed by a thread running in the virtual machine since a preceding event;

first computing means for computing the number of bytecodes executed by the thread running in the virtual machine since the preceding event, and

returning means for returning, in response to the request, the number of bytecodes executed by the thread running in the virtual machine since the preceding event, wherein the first computing means further includes;

retrieving means for retrieving a stored bytecode count for the thread;

obtaining means for obtaining a current bytecode count for the thread;

second computing means for computing a difference between the current bytecode count and the stored bytecode count; and

adding means for adding the computed difference to the number of bytecodes executed by the thread running in the virtual machine since the preceding event.

4. The data processing system of claim 3 further comprising:

storing means for storing the current bytecode count for subsequent retrieval.

5. The data processing system of claim 3 further comprising applying means for applying, in response to a determination of completion of the profiling the instrumented program, remaining bytecode counts to corresponding threads.

6. A computer program product in a computer-readable medium for use in a data processing system for processing events detected while profiling an instrumented program executed by a virtual machine in the data processing system, the computer program product comprising:

first instructions for receiving, in response to an occurrence of a current event, a request for a number of bytecodes executed by a thread running in the virtual machine since a preceding event;

second instructions for computing the number of bytecodes executed by the thread running in the virtual machine since the preceding event; and

third instructions for returning, in response to the request, the number of bytecodes executed by the thread running in the virtual machine since the preceding event, wherein the second instructions further include;

instructions for retrieving a stored bytecode count for the thread;

instructions for obtaining a current bytecode count for the thread;

instructions for computing a difference between the current bytecode count and the stored bytecode count; and

instructions for adding the computed difference to the number of bytecodes executed by the thread running in the virtual machine since the preceding event.

7. The computer program product of claim 6 further comprising:

instructions for storing the current bytecode count for subsequent retrieval.