Scalable system call stack sampling

• US 8,799,904 B2
• Filed: 01/21/2011
• Issued: 08/05/2014
• Est. Priority Date: 01/21/2011
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Kuiper, Kean G., Levine, Frank E.
• Primary Examiner(s): NGUYEN, VAN H
• Application Number:
  US13/011,621
• Publication Number:
  US 20120191893A1
• Time in Patent Office: 1,292 Days
• Field of Search: 719/310, 719/318, 718/100, 718/107, 717/126, 717/127
• US Class Current: 718/100
• CPC Class Codes: G06F 13/24 using interrupt G06F13/32 takes precedence
• CPC Class Codes: G06F 9/4812 by interrupt, e.g. masked

Abstract

An interrupt is generated based on an event. Further, a thread is selected for monitoring. In addition, an interrupt handler captures information for the monitored thread. An affinity of the monitored thread is set such that the monitored thread runs only on a current processor without being able to migrate to a different processor. A sampler thread that runs on the current processor retrieves a call stack associated with a monitored thread after the affinity of the monitored thread has been set to the current processor.

Claims

1. A computer program product for multi-threading, the computer program product comprising:

a non-transitory computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising;

computer readable program code configured to generate an interrupt based on an event;

computer readable program code configured to select a thread for monitoring;

computer readable program code configured to capture information, with an interrupt handler, for a monitored thread;

computer readable program code configured to set an affinity of the monitored thread such that the monitored thread runs only on a current processor without being able to migrate to a different processor; and

computer readable program code configured to retrieve, with a sampler thread that runs on the current processor, a call stack associated with a monitored thread after the affinity of the monitored thread has been set to the current processor.

2. The computer program product of claim 1, wherein the computer readable program code is also configured to restore the affinity of the monitored thread after the call stack has been retrieved.

3. The computer program product of claim 1, wherein the monitored thread is selected utilizing a subsequent thread in a list of threads.

4. The computer program product of claim 1, wherein the interrupt handler selects the monitored thread in response to taking an interrupt.

5. The computer program product of claim 1, wherein the monitored thread is selected by a sampler thread.

6. The computer program product of claim 1, wherein the monitored thread is selected randomly according to a random selection process.

7. The computer program product of claim 6, wherein the random selection process includes a weighting related to a number of times each thread is interrupted.

8. The computer program product of claim 1, wherein the current processor is busy at the time the interrupt is signaled and the monitored thread is not currently executing.

9. The computer program product of claim 1, wherein the monitored thread is selected from a list of threads identified during a warm up phase before the call stacks are recorded.

10. A method comprising:

generating, using a computer having storage, an interrupt based on an event;

selecting a thread for monitoring;

capturing information, with an interrupt handler, for a monitored thread;

setting an affinity of the monitored thread such that the monitored thread runs only on a current processor without being able to migrate to a different processor;

retrieving, with a sampler thread that runs on the current processor, a call stack associated with a monitored thread after the affinity of the monitored thread has been set to the current processor; and

restoring the affinity of the monitored thread after the call stack has been retrieved.

11. The method of claim 10, further comprising restoring the affinity of the monitored thread after the call stack has been retrieved.

12. The method of claim 10, wherein the interrupt handler selects the monitored thread in response to taking an interrupt.

13. The method of claim 10, wherein the monitored thread is selected by a sampler thread.

14. The method of claim 10, wherein the monitored thread is selected randomly according to a random selection process.

15. The method of claim 14, wherein the random selection process includes a weighting related to a number of times each thread is interrupted.

16. The method of claim 10, wherein the current processor is busy at the time the interrupt is signaled and the monitored thread is not currently executing.

17. The method of claim 10, wherein the monitored thread is selected from a list of threads identified during a warm up phase before the call stacks are recorded.

18. A system comprising:

processors; and

storage coupled to the processors, wherein the storage device has stored thereon program code, and wherein at least one of the processors is configured to execute the program code to perform operations, wherein the operations comprise;

generating an interrupt based on an event;

selecting a thread for monitoring;

capturing information, with an interrupt handler, for a monitored thread;

setting an affinity of the monitored thread such that the monitored thread runs only on a current processor of the processors without being able to migrate to a different processor of the processors; and

retrieving, with a sampler thread that runs on the current processor, a call stack associated with a monitored thread after the affinity of the monitored thread has been set to the current processor.

19. The system of claim 18, wherein the monitored thread is selected utilizing a subsequent thread in a list of threads.

20. The system of claim 18, wherein the interrupt handler selects the monitored thread in response to taking an interrupt.

21. The system of claim 20, wherein the monitored thread is selected by a sampler thread.

22. The system of claim 21, wherein the monitored thread is suspended after the monitored thread is identified.

23. The system of claim 22, wherein the monitored thread is resumed the after the affinity is set.