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.
Bug 1554458 - realtime-virtual-host: vCPU thread going to userspace
Summary: realtime-virtual-host: vCPU thread going to userspace
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: tuned
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: Robin Hack
URL:
Whiteboard:
Depends On:
Blocks: kvm-rt-tuned
TreeView+ depends on / blocked
 
Reported: 2018-03-12 17:37 UTC by Luiz Capitulino
Modified: 2020-11-14 12:20 UTC (History)
5 users (show)

Fixed In Version: tuned-2.12.0-0.1.rc1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:31:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
patch for upstream adding tsc-deadline=on (1.09 KB, patch)
2018-03-13 12:53 UTC, Luiz Capitulino 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3633 0 None None None 2019-11-05 22:31:29 UTC

Description Luiz Capitulino 2018-03-12 17:37:37 UTC 
Description of problem:

I can observe that the vCPU thread of the guest ran by run-tscdeadline-latency.sh is going to userspace to do I/O. This increases the latency when trying to find the best timer advancement value from the host profile. Passing tsc-deadline=on in -cpu seems to fix this. I believe that qemu is not using the in kernel irqchip if tsc-deadline=on is not passed.


Version-Release number of selected component (if applicable): tuned-2.9.0-1.el7.noarch


How reproducible:

Unfortunately, the most reliable method to reproduce is a bit complex:

1. Clone kvm-unit-tests repo:

 # git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git

2. Edit x86/tscdeadline_latency.c and change TABLE_SIZE to be 1000000

3. Build it with make

4. Edit /usr/lib/tuned/realtime-virtual-host/run-tscdeadline-latency.sh and change the following line:

-kernel /usr/share/qemu-kvm/tscdeadline_latency.flat

to be:

-kernel /path/to/kvm-unit-tests/x86/tscdeadline_latency.flat

5. Run run-tscdeadline-latency.sh from the host profile

6. Trace for kvm_userspace_exit in all CPUs (make sure there are no other guests running)

Actual results:

You'll see the kvm_userspace_exit event triggering all the time.

Expected results:

There may be some kvm_userspace_exit in the beginning, but they eventually stop.

Additional info:
Comment 2 Luiz Capitulino 2018-03-13 12:53:19 UTC 
Created attachment 1407549 [details]
patch for upstream adding tsc-deadline=on
Comment 3 Jaroslav Škarvada 2019-03-18 12:43:05 UTC 
Ah, sorry, this haven't yet got upstream. Is it still needed?
Comment 4 Luiz Capitulino 2019-03-18 16:57:06 UTC 
To be honest, I'm not 100% sure. Let's do it for RHEL8 and then we (KVM-RT team) can
evaluate the need for RHEL7.
Comment 5 Jaroslav Škarvada 2019-06-10 17:15:05 UTC 
Upstream commit: https://github.com/redhat-performance/tuned/commit/9b1c045d30d957c9b2d1537699503edaedb37129
Comment 6 Robin Hack 2019-06-11 08:50:46 UTC 
QA_ACK+ RHEL8.1
Comment 15 errata-xmlrpc 2019-11-05 22:31:10 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, 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-2019:3633
Note You need to log in before you can comment on or make changes to this bug.