Linux Power Management development
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: x86 Maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Subject: Re: [PATCH v1] x86/sched: Print debug messages on hybrid asym capacity changes
Date: Wed, 9 Jul 2025 13:46:06 +0200	[thread overview]
Message-ID: <20250709114606.GJ1613200@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <4664631.LvFx2qVVIh@rjwysocki.net>

On Wed, Jul 09, 2025 at 12:47:17PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Subject: [PATCH v1] x86/sched: Print debug messages on hybrid asym capacity changes
> 
> Make arch_set_cpu_capacity() print a debug message including the
> capacity and maximum frequency ratio used in scale-invariant utilization
> computations for a given CPU and in capacity-aware scheduling (CAS) or
> energy-aware scheduling (EAS).
> 
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
>  arch/x86/kernel/cpu/aperfmperf.c |    4 ++++
>  1 file changed, 4 insertions(+)
> 
> --- a/arch/x86/kernel/cpu/aperfmperf.c
> +++ b/arch/x86/kernel/cpu/aperfmperf.c
> @@ -416,6 +416,10 @@
>  			   div_u64(cap << SCHED_CAPACITY_SHIFT, max_cap));
>  		WRITE_ONCE(per_cpu_ptr(arch_cpu_scale, cpu)->freq_ratio,
>  			   div_u64(cap_freq << SCHED_CAPACITY_SHIFT, base_freq));
> +
> +		pr_debug("CPU%d: capacity = %lu, freq_ratio = %lu\n", cpu,
> +			 per_cpu_ptr(arch_cpu_scale, cpu)->capacity,
> +			 per_cpu_ptr(arch_cpu_scale, cpu)->freq_ratio);
>  	} else {
>  		WARN_ONCE(1, "Hybrid CPU capacity scaling not enabled");
>  	}

There's already a printk in the calling function
hybrid_set_cpu_capacity(), so now we get _2_ prints per CPU. That's a
bit excessive, no?

Also, should this print be conditional on sched_debug_verbose?

  reply	other threads:[~2025-07-09 11:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 10:47 [PATCH v1] x86/sched: Print debug messages on hybrid asym capacity changes Rafael J. Wysocki
2025-07-09 11:46 ` Peter Zijlstra [this message]
2025-07-09 12:02   ` Rafael J. Wysocki

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=20250709114606.GJ1613200@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ricardo.neri-calderon@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=x86@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