From: Phil Auld <pauld@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [tip: sched/urgent] sched/x86: Export 'percpu arch_freq_scale'
Date: Fri, 31 May 2024 09:19:59 -0400 [thread overview]
Message-ID: <20240531131959.GC54413@lorien.usersys.redhat.com> (raw)
In-Reply-To: <171714958509.10875.11912816904466913393.tip-bot2@tip-bot2>
On Fri, May 31, 2024 at 09:59:45AM -0000 tip-bot2 for Phil Auld wrote:
> The following commit has been merged into the sched/urgent branch of tip:
>
> Commit-ID: d40605a6823577a6c40fad6fb1f10a40ea0389d7
> Gitweb: https://git.kernel.org/tip/d40605a6823577a6c40fad6fb1f10a40ea0389d7
> Author: Phil Auld <pauld@redhat.com>
> AuthorDate: Thu, 30 May 2024 14:15:48 -04:00
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitterDate: Fri, 31 May 2024 11:48:42 +02:00
>
> sched/x86: Export 'percpu arch_freq_scale'
>
Thanks Ingo!
> Commit:
>
> 7bc263840bc3 ("sched/topology: Consolidate and clean up access to a CPU's max compute capacity")
>
> removed rq->cpu_capacity_orig in favor of using arch_scale_freq_capacity()
> calls. Export the underlying percpu symbol on x86 so that external trace
> point helper modules can be made to work again.
>
> Signed-off-by: Phil Auld <pauld@redhat.com>
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Link: https://lore.kernel.org/r/20240530181548.2039216-1-pauld@redhat.com
> ---
> arch/x86/kernel/cpu/aperfmperf.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/x86/kernel/cpu/aperfmperf.c b/arch/x86/kernel/cpu/aperfmperf.c
> index f9a8c7b..b3fa61d 100644
> --- a/arch/x86/kernel/cpu/aperfmperf.c
> +++ b/arch/x86/kernel/cpu/aperfmperf.c
> @@ -345,6 +345,7 @@ static DECLARE_WORK(disable_freq_invariance_work,
> disable_freq_invariance_workfn);
>
> DEFINE_PER_CPU(unsigned long, arch_freq_scale) = SCHED_CAPACITY_SCALE;
> +EXPORT_PER_CPU_SYMBOL_GPL(arch_freq_scale);
>
> static void scale_freq_tick(u64 acnt, u64 mcnt)
> {
>
--
next prev parent reply other threads:[~2024-05-31 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 18:15 [PATCH] sched,x86: export percpu arch_freq_scale Phil Auld
2024-05-31 9:59 ` [tip: sched/urgent] sched/x86: Export 'percpu arch_freq_scale' tip-bot2 for Phil Auld
2024-05-31 13:19 ` Phil Auld [this message]
2024-06-04 12:23 ` [PATCH] sched,x86: export percpu arch_freq_scale Qais Yousef
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=20240531131959.GC54413@lorien.usersys.redhat.com \
--to=pauld@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®