-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8366854: Extend jtreg failure handler with THP info #27086
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
Conversation
👋 Welcome back stefank! A progress list of the required criteria for merging this PR into |
@stefank This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 28 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
/label add hotspot |
@stefank |
The proposed changes give the following output the environment.html file:
|
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing this @stefank
This was really helpful when we debugged a THP issue recently, so good to get it into the mainline.
memory.proc_vmstat.args=-c\0cat /proc/vmstat | ||
memory.proc_vmstat.delimiter=\0 | ||
memory.thp.app=bash | ||
memory.thp.args=-c\0cat /sys/kernel/mm/transparent_hugepage/{enabled,defrag} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should include shmem_enabled
and we could use tail
if we want to see what files have what info. But I don't have a strong feeling about that:
$ cat /sys/kernel/mm/transparent_hugepage/{enabled,defrag,shmem_enabled}
always [madvise] never
always defer defer+madvise [madvise] never
always within_size advise [never] deny force
Versus:
$ tail /sys/kernel/mm/transparent_hugepage/{enabled,defrag,shmem_enabled}
==> /sys/kernel/mm/transparent_hugepage/enabled <==
always [madvise] never
==> /sys/kernel/mm/transparent_hugepage/defrag <==
always defer defer+madvise [madvise] never
==> /sys/kernel/mm/transparent_hugepage/shmem_enabled <==
always within_size advise [never] deny force
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added shmem_enabled but kept cat for now.
Thanks for the reviews! |
Going to push as commit a1ab12b.
Your commit was automatically rebased without conflicts. |
I propose that we also dump /proc/meminfo, /proc/vmstat, and /sys/kernel/mm/transparent_hugepage/{enabled, defrag} from the failure handler.
This information has been helpful when investigating a failure where there was an unexpected lack of transparent huge pages.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27086/head:pull/27086
$ git checkout pull/27086
Update a local copy of the PR:
$ git checkout pull/27086
$ git pull https://git.openjdk.org/jdk.git pull/27086/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27086
View PR using the GUI difftool:
$ git pr show -t 27086
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27086.diff
Using Webrev
Link to Webrev Comment