As we approach the GA of RHEL 9.6 and RHEL 10.0, we would like to invite you to participate in the kernel code coverage testing for these releases. RHEL 9.6 will be an EUS stream, while RHEL 10.0 marks a brand-new major release. Both releases are crucial to our business objectives.

We have been conducting kernel code coverage tests for several years, and they have proven invaluable in identifying our strengths and weaknesses. These tests guide our next steps for testing enhancements and improvements. You can find our historical data from RHEL 7 to RHEL 9.4 here.

To run the kernel code coverage tests, please refer to the Code Coverage How-to.

You may also refer to our example Beaker jobs for RHEL 9.6 and RHEL 10.0:

• RHEL 10.0: https://beaker.engineering.redhat.com/jobs/10962319
• RHEL 9.6: https://beaker.engineering.redhat.com/jobs/10962320

kernel, kernel-rt, and kernel-automotive code coverage RPMs for RHEL 9.6 and RHEL 10.0 at the following links:

• RHEL 9.6:
    - kernel-5.14.0-570.12.1.gcov.el9_6
    - kernel-automotive-5.14.0-570.518.12.1.11.gcov.el9_6iv
• RHEL 10.0:
    - kernel-6.12.0-55.9.1.gcov.el10_0

Our recommended test scope is as follows:

• RHEL 9.6:
    - Run all tier tests on x86_64 for both kernel and kernel-rt.
    - Make a best effort to cover s390x, aarch64, and ppc64le.
• RHEL 10.0:
    - Run all tier tests on x86_64, s390x, aarch64, and ppc64le for both kernel and kernel-rt.

Our plan for the kernel code coverage testing is outlined below:
1. SSTs:
   - Decide on the test scope and complete the kernel code coverage testing by May 16th.
2. Kmaint QE:
   - Collect all raw coverage data and merge it into a single core kernel team coverage data file. This file will represent our team's kernel code coverage.
   - Complete the merge by May 23th and distribute the data to the SSTs and feature owners involved in the 9.6/10.0 kernel code coverage testing.
3. SSTs and Feature Owners:
   - Extract subsystem coverage data from the single core kernel team coverage data file
4. Follow-Up Actions:
   - Review the original data and identify areas for improvement if possible in the next minor release.