Bug 2081325
Summary: | Add measurement and load location information to the run summary report | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Clark Williams <williams> |
Component: | rteval | Assignee: | Leah Leshchinsky <lleshchi> |
Status: | CLOSED ERRATA | QA Contact: | Waylon Cude <wcude> |
Severity: | medium | Docs Contact: | Sujata Kurup <skurup> |
Priority: | unspecified | ||
Version: | 9.2 | CC: | bhu, jkacur, mstowell, qzhao, rt-maint, skurup |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rteval-3.4-4.el9 | Doc Type: | Enhancement |
Doc Text: |
.The `rteval` command output now includes the program loads and measurement threads information
The `rteval` command now displays a report summary with the number of program loads, measurement threads, and the corresponding CPU that ran these threads. This information helps to evaluate the performance of a real-time kernel under load on specific hardware platforms.
The `rteval` report is written to an XML file along with the boot log for the system and saved to the `rteval-<date>-N-tar.bz2` compressed file. The `date` specifies the report generation date and `N` is the counter for the Nth run.
To generate an `rteval` report, enter the following command:
----
# rteval --summarize rteval-<date>-N.tar.bz2
----
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-05-09 07:18:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2119171 |
Description
Clark Williams
2022-05-03 13:01:26 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (rteval bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:2149 |