From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218022] New: CONFIG_CPU_FREQ_GOV_SCHEDUTIL - 10%-12% reduced performance in lower priority processes on ADL Intel processors.
Date: Tue, 17 Oct 2023 17:11:56 +0000 [thread overview]
Message-ID: <bug-218022-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218022
Bug ID: 218022
Summary: CONFIG_CPU_FREQ_GOV_SCHEDUTIL - 10%-12% reduced
performance in lower priority processes on ADL Intel
processors.
Product: Power Management
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: ionut_n2001@yahoo.com
Regression: No
Hi,
I have noticed for some days, working on an Intel ADL system, that certain
processes are not processed correctly at certain low frequencies, and the
return in frequency causes the applications to go under glitches.
How could I test to see if there are problems from the scheduler, C-state or
intel_pstate?
CPU: 12th Gen Intel(R) Core(TM) i7-1260P
5.15.0-1042-intel-iotg (5.15.122) Ubuntu OS
From what I see on ADL the performances are relatively good, but with C-state
disabled they are improved quite a lot.
- processor.max_cstate=0 intel.max_cstate=0 processor_idle.max_cstate=0
intel_idle.max_cstate=0
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.0-1042-intel-iotg
root=UUID=d52175e7-4bd5-4a56-891f-f5961006330f ro processor.max_cstate=0
intel.max_cstate=0 processor_idle.max_cstate=0 intel_idle.max_cstate=0 quiet
splash vt.handoff=7
With all parameters in cmdline, the system becomes stable.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-10-17 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 17:11 bugzilla-daemon [this message]
2023-10-17 17:12 ` [Bug 218022] CONFIG_CPU_FREQ_GOV_SCHEDUTIL - 10%-12% reduced performance in lower priority processes on ADL Intel processors bugzilla-daemon
2023-10-17 17:16 ` bugzilla-daemon
2023-10-18 6:49 ` bugzilla-daemon
2023-10-18 13:24 ` bugzilla-daemon
2023-10-18 16:29 ` bugzilla-daemon
2023-10-19 8:53 ` bugzilla-daemon
2023-10-19 8:57 ` bugzilla-daemon
2023-10-20 5:38 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-218022-137361@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-pm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).