Method and apparatus for diagnostic recording using transactional memory

• US 8,972,794 B2
• Filed: 02/26/2008
• Issued: 03/03/2015
• Est. Priority Date: 02/26/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Wilding, Mark Francis, Blainey, Robert James, Heller, Thomas J. Jr., Abrashkevich, Alexander
• Primary Examiner(s): Baderman, Scott
• Assistant Examiner(s): PATEL, JIGAR P
• Application Number:
  US12/037,214
• Publication Number:
  US 20090217104A1
• Time in Patent Office: 2,562 Days
• Field of Search: 714/45
• US Class Current: 714/45
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence

Abstract

A method (500) or a diagnostic recording device (400) having transactional memory and a processor coupled to the transactional memory can store (502) contents of a transaction log (40) of the transactional memory, detect (504) an exception event, and replay (506) last instructions that led up to the exception event using a debugger tool (80). The transactional memory can be hardware or software based transactional memory. The processor can also store the transaction log by storing the contents of the transaction log in a core file (302) which can include a stack (60), a register dump (70), a memory dump (75), and the transactional log. The debugger tool can be used to load up the core file, an executable file (95), and a library (90) to enable the diagnostic recording device to retrace transactions occurring at the diagnostic recording device up to the exception event.

Claims

1. A method of gathering diagnostic information in a hardware-based transactional memory system, comprising:

responsive to detecting an exception event has occurred in a first thread, invoking a system call of an operating system to access a portion, of a transaction log of a hardware-based transactional memory, that corresponds to the first thread, wherein the transaction log is stored in a hardware buffer of the hardware-based transactional memory, wherein the hardware-based transactional memory is configured to record recent memory accesses in the transaction log, wherein the portion of the transaction log includes recent memory accesses for the first thread, and wherein the transaction log is required for operation of the hardware-based transactional memory;

storing the portion of the transaction log in a core file, wherein the core file further comprises a stack trace, a register dump, and a memory dump; and

replaying a plurality of instructions that led to the exception event in the first thread via a debugger tool, using the portion of the transaction log stored within the core file.

2. The method of claim 1, wherein the exception event comprises at least one of a trap condition, a program check event, a trap event, a fault event, and an exception condition.

3. The method of claim 1, further comprising:

further responsive to detecting the exception event has occurred in the first thread, accessing the stack trace and the register dump relating to the first thread; and

storing the stack trace and the register dump in the core file.

4. The method of claim 3, wherein the stack trace and the register dump are stored as contents of the exception event, and wherein accessing the stack trace and the register dump further comprises accessing the contents of the exception event to retrieve the stack trace and the register dump.

5. The method of claim 1, wherein replaying the plurality of instructions that led to the exception event in the first thread via the debugger tool further comprises:

loading the core file into the debugging tool, together with an executable file for the first thread and one or more libraries associated with the first thread; and

retracing a plurality of instructions of the first thread leading up to the exception event, in order to view the impact of each of the plurality of instructions on the contents of the hardware-based transactional memory, using the portion of the transaction log within the core file.

6. A computer program product embodied in a computer-readable storage device, the computer program product comprising instructions executable by a data processing machine that cause the data processing machine to perform an operation for gathering diagnostic information in a hardware-based transactional memory system, comprising:

responsive to detecting an exception event has occurred in a first thread, invoking a system call of an operating system to access a portion, of a transaction log of a hardware-based transactional memory, that corresponds to the first thread, wherein the transaction log is stored in a hardware buffer of the hardware-based transactional memory, wherein the hardware-based transactional memory is configured to record recent memory accesses in the transaction log, wherein the portion of the transaction log includes recent memory accesses for the first thread, and wherein the transaction log is required for operation of the hardware-based transactional memory;

storing the portion of the transaction log in a core file, wherein the core file further comprises a stack trace, a register dump, and a memory dump; and

replaying a plurality of instructions that led to the exception event in the first thread via a debugger tool, using the portion of the transaction log stored within the core file.

7. The computer program product of claim 6, wherein the exception event comprises at least one of a trap condition, a program check event, a trap event, a fault event, and an exception condition.

8. The computer program product of claim 6, the operation further comprising:

further responsive to detecting the exception event has occurred in the first thread, accessing stack trace and the register dump relating to the first thread; and

storing the stack trace and the register dump in the core file.

9. The computer program product of claim 8, wherein the stack trace and the register dump are stored as contents of the exception event, and wherein accessing the stack trace and the register dump further comprises accessing the contents of the exception event to retrieve the stack trace and the register dump.

10. The computer program product of claim 6, wherein replaying the plurality of instructions that led to the exception event in the first thread via the debugger tool further comprises:

loading the core file into the debugging tool, together with an executable file for the first thread and one or more libraries associated with the first thread; and

retracing a plurality of instructions of the first thread leading up to the exception event, in order to view the impact of each of the plurality of instructions on the contents of the hardware-based transactional memory, using the portion of the transaction log within the core file.

11. A hardware-based transactional memory system, comprising:

a processor; and

a hardware-based transactional memory containing a program that, when executed by the processor, performs an operation for gathering diagnostic information, comprising;

responsive to detecting an exception event has occurred in a first thread, invoking a system call of an operating system to access a portion, of a transaction log of a hardware-based transactional memory, that corresponds to the first thread, wherein the transaction log is stored in a hardware buffer of the hardware-based transactional memory, wherein the hardware-based transactional memory is configured to record recent memory accesses in the transaction log, wherein the portion of the transaction log includes recent memory accesses for the first thread, and wherein the transaction log is required for operation of the hardware-based transactional memory;

storing the portion of the transaction log in a core file, wherein the core file further comprises a stack trace, a register dump, and a memory dump; and

replaying a plurality of instructions that led to the exception event in the first thread via a debugger tool, using the portion of the transaction log stored within the core file.

12. The hardware-based transactional memory system of claim 11, wherein the exception event comprises at least one of a trap condition, a program check event, a trap event, a fault event, and an exception condition.

13. The hardware-based transactional memory system of claim 11, the operation further comprising:

further responsive to detecting the exception event has occurred in the first thread, accessing the stack trace and the register dump relating to the first thread; and

storing the stack trace and the register dump in the core file.

14. The hardware-based transactional memory system of claim 13, wherein the stack trace and the register dump are stored as contents of the exception event, and wherein accessing the stack trace and the register dump further comprises accessing the contents of the exception event to retrieve the stack trace and the register dump.

15. The hardware-based transactional memory system of claim 11, wherein replaying the plurality of instructions that led to the exception event in the first thread via the debugger tool further comprises:

loading the core file into the debugging tool, together with an executable file for the first thread and one or more libraries associated with the first thread; and

retracing a plurality of instructions of the first thread leading up to the exception event, in order to view the impact of each of the plurality of instructions on the contents of the hardware-based transactional memory, using the portion of the transaction log within the core file.