Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lockup: Print tasks which have been on-cpu for too long #109

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

richl9
Copy link
Contributor

@richl9 richl9 commented Sep 30, 2024

  1. add helper for scanning potential lockups on cpus and dumping their info
  2. add prio in runq dump

@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Sep 30, 2024
Copy link
Member

@brenns10 brenns10 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks interesting. I think my biggest question is whether the number of seconds on CPU is actually a reliable indicator of some sort of lockup, and whether 0 is a good default for that parameter.

drgn_tools/lockup.py Outdated Show resolved Hide resolved
drgn_tools/lockup.py Outdated Show resolved Hide resolved
drgn_tools/lockup.py Show resolved Hide resolved
drgn_tools/runq.py Outdated Show resolved Hide resolved
drgn_tools/runq.py Outdated Show resolved Hide resolved
@richl9 richl9 changed the title Richard/lockup lockup: Print tasks which have been on-cpu for too long Oct 18, 2024
@richl9 richl9 requested a review from brenns10 October 19, 2024 01:56
@brenns10 brenns10 merged commit 5477af2 into oracle-samples:main Dec 16, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCA Verified All contributors have signed the Oracle Contributor Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants