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 1247184 - scheduler plugin causes nohz_full to be de-activated
Summary: scheduler plugin causes nohz_full to be de-activated
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tuned
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: Tereza Cerna
URL:
Whiteboard:
Depends On:
Blocks: kvm-rt-tuned
TreeView+ depends on / blocked
 
Reported: 2015-07-27 14:03 UTC by Luiz Capitulino
Modified: 2015-11-19 12:21 UTC (History)
5 users (show)

Fixed In Version: tuned-2.5.1-3.el7
Doc Type: Bug Fix
Doc Text:
Cause: Previously the new perf code for runtime tuning functionality of plugin_scheduler could cause nohz_full not to work correctly. Consequence: This may degrade performance for real-time workloads or HPC workloads. Fix: The perf code was improved to work correctly with nohz_full. Result: Now the runtime functionality of scheduler_plugin works correctly with nohz_full.
Clone Of:
Environment:
Last Closed: 2015-11-19 12:21:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2375 0 normal SHIPPED_LIVE tuned bug fix and enhancement update 2015-11-19 10:51:42 UTC

Description Luiz Capitulino 2015-07-27 14:03:10 UTC 
Description of problem:

During KVM-RT testing, we've found that tuned's scheduler plugin causes nohz_full to be de-activated. This happens because the scheduler plugin sets up perf event watching on all cores during startup and nohz_full is currently incompatible with perf event watching (see reproducer below).

Version-Release number of selected component (if applicable): tuned-2.4.1-1.20150705git1da9f3cc.el7.noarch


How reproducible:


Steps to Reproduce:
1. Set up nohz_full on a core. Eg., use the following options to the kernel command-line:

isolcpus=X nohz_full=X

2. Install tuned and activate a profile that uses the scheduler plugin. I'm using the realtime-virtual-host profile

3. Run the following script, where Y is the CPU mask corresponding to the nohz_full core and "stress" is any application capable of taking 100% of the CPU

"""
/bin/bash

cd /sys/kernel/debug/tracing
echo Y > tracing_cpumask
echo tick_stop > set_event
echo nop > current_tracer
echo > set_ftrace_filter
echo > /tracing/trace
echo 1 > /tracing/tracing_on

cd
chrt -f 1 taskset -c 15 ./stress --cpu 1 &
sleep 2

grep tick_stop /tracing/trace
pkill -9 stress
"""

Actual results:

Lots of:

tick_stop: success=no msg=perf events running


Expected results:

Only one of the following:

stress-3236  [015] d...1..   292.142704: tick_stop: success=yes msg=


Additional info:
Comment 1 Luiz Capitulino 2015-07-27 14:07:26 UTC 
I forgot to mention that it's possible to disable the scheduler plugin runtime feature as a workaround for this issue. Simply edit the tuned.conf file for the profile and add runtime=0 to the scheduler section, like:

[scheduler]
runtime=0
Comment 2 Jaroslav Škarvada 2015-07-31 14:32:06 UTC 
Upstream commit fixing this problem:
https://git.fedorahosted.org/cgit/tuned.git/commit/?id=5024f00ef59de394c31668696eb2f311f2aebc85
Comment 4 Fedora Update System 2015-09-03 18:49:50 UTC 
tuned-2.5.1-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
Comment 5 Fedora Update System 2015-09-03 18:50:46 UTC 
tuned-2.5.1-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Comment 7 errata-xmlrpc 2015-11-19 12:21:59 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://rhn.redhat.com/errata/RHBA-2015-2375.html
Note You need to log in before you can comment on or make changes to this bug.