THREAD SERIALIZATION AND DISABLEMENT TOOL

• US 20140359583A1
• Filed: 08/12/2014
• Published: 12/04/2014
• Est. Priority Date: 11/23/2009
• Status: Active Grant

• Current Assignee: Taiwan Semiconductor Manufacturing Company Limited
• Original Assignee: International Business Machines Corporation
• Inventors: Krauss, Kirk J.
• Granted Patent: US 9,058,417 B2
• Time in Patent Office: Days
• US Class Current: 717/130
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 9/4881 Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues

Abstract

A computer-implemented method of performing runtime analysis on and control of a multithreaded computer program. One embodiment of the present invention can include identifying threads of a computer program to be analyzed. With a supervisor thread, execution of the identified threads can be controlled and execution of the identified threads can be monitored to determine a status of the identified threads. An indicator corresponding to the determined status of the threads can be output.

Claims

1-20. -20. (canceled)

21. A method of performing runtime analysis on a multithreaded computer program, comprising:

identifying threads of the computer program to be analyzed;

instrumenting the computer program to track events for each of the identified threads;

presenting, in a user interface, at least one indicator corresponding to a determined status for each of the identified threads.

22. The method of claim 21, further comprising:

assigning a management lock to the identified threads to control when the identified threads are executed; and

executing the identified threads based upon the management lock.

23. The method of claim 22, wherein

the at least one indicator indicates which of the identified threads is waiting to receive ownership of the management lock.

24. The method of claim 21, further comprising:

allocating a management lock exclusively for ownership by one of the identified threads at a time; and

revoking ownership of the management lock exclusively upon no processor activity detected for the identified thread to which the management lock is allocated.

25. The method of claim 21, further comprising:

receiving a user request to disable execution of at least one thread selected from the identified threads;

queuing the user request until the selected thread no longer holds any management locks; and

upon the selected thread no longer holding any management locks, assigning ownership of a management lock to a second thread thereby disabling execution of the selected thread until the selected thread is assigned ownership of the management lock.

26. The method of claim 21, further comprising:

receiving a user input indicating, for each of a plurality of the identified threads, a respective thread priority to be assigned;

assigning each of the respective thread priorities to a corresponding one of the identified threads; and

executing the identified threads in an order determined from the assigned thread priorities.

27. A computer hardware system configured to perform runtime analysis on a multithreaded computer program, comprising:

at least one processor, wherein the at least one processor is configured to initiate and/or perform;

identifying threads of the computer program to be analyzed;

instrumenting the computer program to track events for each of the identified threads;

presenting, in a user interface, at least one indicator corresponding to a determined status for each of the identified threads.

28. The system of claim 27, wherein the at least one processor is further configured to initiate and/or perform:

assigning a management lock to the identified threads to control when the identified threads are executed; and

executing the identified threads based upon the management lock.

29. The system of claim 28, wherein

the at least one indicator indicates which of the identified threads is waiting to receive ownership of the management lock.

30. The system of claim 27, wherein the at least one processor is further configured to initiate and/or perform:

allocating a management lock exclusively for ownership by one of the identified threads at a time; and

revoking ownership of the management lock exclusively upon no processor activity detected for the identified thread to which the management lock is allocated.

31. The system of claim 27, wherein the at least one processor is further configured to initiate and/or perform:

receiving a user request to disable execution of at least one thread selected from the identified threads;

queuing the user request until the selected thread no longer holds any management locks; and

upon the selected thread no longer holding any management locks, assigning ownership of a management lock to a second thread thereby disabling execution of the selected thread until the selected thread is assigned ownership of the management lock.

32. The system of claim 27, wherein the at least one processor is further configured to initiate and/or perform:

receiving a user input indicating, for each of a plurality of the identified threads, a respective thread priority to be assigned;

assigning each of the respective thread priorities to a corresponding one of the identified threads; and

executing the identified threads in an order determined from the assigned thread priorities.

33. A computer program product comprising:

a computer-usable storage medium having stored therein computer-usable program code for performing runtime analysis on a multithreaded computer program,

the computer-usable program code, which when executed by a computer hardware system, causes the computer hardware system to perform;

identifying threads of the computer program to be analyzed;

instrumenting the computer program to track events for each of the identified threads;

presenting, in a user interface, at least one indicator corresponding to a determined status for each of the identified threads, wherein

the computer-usable storage medium is not a transitory, propagating signal per se.

34. The computer program product of claim 33, wherein the computer-usable program code further causes the computer hardware system to perform:

assigning a management lock to the identified threads to control when the identified threads are executed; and

executing the identified threads based upon the management lock.

35. The computer program product of claim 34, wherein

the at least one indicator indicates which of the identified threads is waiting to receive ownership of the management lock.

36. The computer program product of claim 33, wherein the computer-usable program code further causes the computer hardware system to perform:

allocating a management lock exclusively for ownership by one of the identified threads at a time; and

revoking ownership of the management lock exclusively upon no processor activity detected for the identified thread to which the management lock is allocated.

37. The computer program product of claim 33, wherein the computer-usable program code further causes the computer hardware system to perform:

receiving a user request to disable execution of at least one thread selected from the identified threads;

queuing the user request until the selected thread no longer holds any management locks; and

upon the selected thread no longer holding any management locks, assigning ownership of a management lock to a second thread thereby disabling execution of the selected thread until the selected thread is assigned ownership of the management lock.

38. The computer program product of claim 33, wherein the computer-usable program code further causes the computer hardware system to perform:

receiving a user input indicating, for each of a plurality of the identified threads, a respective thread priority to be assigned;

assigning each of the respective thread priorities to a corresponding one of the identified threads; and

executing the identified threads in an order determined from the assigned thread priorities.