RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

I am not too familiar with systemtap so can we have someone from the systemtap review this please?

The sentence above would address that. More information about transparent huge pages at:

www.linux-kvm.org/wiki/images/9/9e/2010-forum-thp.pdf

According to slide 12 it only works for anonymous memory regions and the following bz indicates that the user stack can make use of huge pages:

678209 - (CVE-2011-0999) CVE-2011-0999 kernel: thp: prevent hugepages during args/env copying into the user stack


Could figures 5.1, 5.2, and 5.3 be from John D. Shakshober (shak) group? Maybe he can provide some details on the benchmarks.

The text around the graphs 5.1, 5.2 and 5.3 make it clearer what information the graphs present. The y-axis label on graph 5.3 also makes it clear what is being measured.