All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 220117] New: cpufreq performance governor doesn't correctly apply in combination with isolcpus
Date: Tue, 13 May 2025 12:47:36 +0000	[thread overview]
Message-ID: <bug-220117-137361@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=220117

            Bug ID: 220117
           Summary: cpufreq performance governor doesn't correctly apply
                    in combination with isolcpus
           Product: Power Management
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: cpufreq
          Assignee: linux-pm@vger.kernel.org
          Reporter: robbert.proost@vitestro.com
        Regression: No

During testing on my setup with kernel 6.6.69 I have found that even though the
cpufreq uses the performance governor, it doesn't seem to correctly apply on
CPUs that are isolated using `isolcpus`.

In my setup if have isolated core 2 and 3 set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE in my kernel configuration to 'Y'.
When verifying the used governor with 'cat
/sys/devices/system/cpu/cpu2/cpufreq/scaling_governor' it correctly outputs
'performance'.

However, when running 'cat /proc/cpuinfo' the clock frequency of the isolated
CPUs is 800 MHz instead of the expected 3000 MHz. For the not isolated CPUs it
does correctly show 3000 MHz. Changing
'/sys/devices/system/cpu/cpuX/cpufreq/scaling_min_freq' to 3000 MHz does change
the clock frequency to 3000 MHz, but that shouldn't be needed.

Kernel bootline: console=tty console=ttyS0,115200 acpi_enforce_resources=lax
panic=1 earlyprintk isolcpus=2,3 rootwait

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2025-05-13 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 12:47 bugzilla-daemon [this message]
2025-05-14 20:44 ` [Bug 220117] cpufreq performance governor doesn't correctly apply in combination with isolcpus bugzilla-daemon
2026-02-28 12:06 ` bugzilla-daemon
2026-02-28 16:06 ` 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-220117-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.