From: Jie Zhan <zhanjie9@hisilicon.com>
To: Yufan Dou <douyufan@picoheart.com>,
Sunil V L <sunilvl@ventanamicro.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, <linux-acpi@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Cc: <yuchao.46@picoheart.com>, <yang.yicong@picoheart.com>,
<lihuisong@picoheart.com>, <geshijian@picoheart.com>,
<wang.yechao255@zte.com.cn>
Subject: Re: [PATCH v2] ACPI: RISC-V: CPPC: Implement cpc_read_ffh_fb_ctrs()
Date: Thu, 17 Sep 2026 17:11:03 +0800 [thread overview]
Message-ID: <ac3b17af-c6bb-4e91-b9bb-6cf2d43f8107@hisilicon.com> (raw)
In-Reply-To: <20260909071541.1545-1-douyufan@picoheart.com>
On 9/9/2026 3:15 PM, Yufan Dou wrote:
> On RISC-V, reading FFH feedback counters on a remote hart through
> cpc_read_ffh() requires a separate IPI for each register.
> cppc_get_perf_ctrs() therefore samples the delivered and reference
> counters in two separate IPIs. Variation in the delay between these
> reads distorts the delivered/reference ratio and thus the frequency
> reported by cpufreq.
>
> Implement cpc_read_ffh_fb_ctrs() to read both counters back-to-back
> in a single callback on the target hart. For remote reads, this
> reduces two IPIs to one and narrows the separation between the
> counter samples. Support CSR-type, SBI-type and mixed-type pairs.
> Pairing SBI reads does not reduce the number of SBI calls, but
> still avoids a separate IPI for each counter.
>
> Factor the execution-context handling into cppc_ffh_read_on_cpu(),
> shared by cpc_read_ffh() and cpc_read_ffh_fb_ctrs(). CPPC frequency
> invariance (FIE) reads non-PCC counters directly from the scheduler
> tick, with local interrupts disabled. Unconditionally rejecting
> such reads prevents the frequency scale from being updated.
>
> Following arm64's counters_read_on_cpu(), invoke the callback
> directly when interrupts are disabled and the target is the current
> CPU. Reject remote reads in that context. Otherwise, use
> smp_call_function_single() and propagate its return value before
> accessing the callback results.
>
> Frequency accuracy testing used CSR-type delivered and reference
> counters, with CPU1 kept busy by:
>
> # stress-ng --cpu 1 --taskset 1
>
> On a CPU with cpuinfo_max_freq of 3000000 kHz:
>
> Before:
>
> Maximum observed cpuinfo_cur_freq: 3201369 kHz
> Maximum observed deviation: +201369 kHz (+6.71%)
>
> After:
>
> Maximum observed cpuinfo_cur_freq: 3009646 kHz
> Maximum observed deviation: +9646 kHz (+0.32%)
>
> The maximum observed deviation from cpuinfo_max_freq decreased
> by 95.2%.
>
> Additional testing covered the CPPC FIE tick path and SBI-type
> FFH register reads.
>
> Co-developed-by: Yicong Yang <yang.yicong@picoheart.com>
> Signed-off-by: Yicong Yang <yang.yicong@picoheart.com>
> Signed-off-by: Yufan Dou <douyufan@picoheart.com>
> Reviewed-by: Sunil V L <sunilvl@oss.qualcomm.com>
LGTM, thanks!
Reviewed-by: Jie Zhan <zhanjie9@hisilicon.com>
> ---
> Changes in v2:
> - Support SBI-type and mixed-type counter pairs in a single callback
> on the target hart, reducing remote reads to one IPI.
> - Factor out cppc_ffh_read_on_cpu() for both FFH read interfaces.
> Allow local reads with interrupts disabled and reject remote reads
> in that context, following arm64's counters_read_on_cpu().
> - Propagate synchronous cross-CPU call errors in cpc_read_ffh().
> - Test the CPPC FIE tick path and SBI-type FFH register reads.
>
> v1:
> https://lore.kernel.org/all/20260902083450.2348-1-douyufan@picoheart.com/
>
> drivers/acpi/riscv/cppc.c | 102 ++++++++++++++++++++++++++++++++++++--
> 1 file changed, 97 insertions(+), 5 deletions(-)
>
[ ... ]
prev parent reply other threads:[~2026-09-17 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 8:34 [PATCH] " Yufan Dou
2026-09-03 5:11 ` Sunil V L
2026-09-07 11:29 ` Jie Zhan
2026-09-07 13:17 ` Yicong Yang
2026-09-07 13:38 ` Jie Zhan
2026-09-09 7:15 ` [PATCH v2] " Yufan Dou
2026-09-17 9:11 ` Jie Zhan [this message]
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=ac3b17af-c6bb-4e91-b9bb-6cf2d43f8107@hisilicon.com \
--to=zhanjie9@hisilicon.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=douyufan@picoheart.com \
--cc=geshijian@picoheart.com \
--cc=lenb@kernel.org \
--cc=lihuisong@picoheart.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rafael@kernel.org \
--cc=sunilvl@ventanamicro.com \
--cc=wang.yechao255@zte.com.cn \
--cc=yang.yicong@picoheart.com \
--cc=yuchao.46@picoheart.com \
/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®