linux-kernel - Re: [PATCH] drivers/perf: riscv: Keep the fixed counter counting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20260209123628.1866-1-cp0613@linux.alibaba.com>
Date: Mon,  9 Feb 2026 20:36:28 +0800
From: cp0613@...ux.alibaba.com
To: atish.patra@...ux.dev
Cc: anup@...infault.org,
	alex@...ti.fr,
	pjw@...nel.org,
	guoren@...nel.org,
	linux-riscv@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers/perf: riscv: Keep the fixed counter counting

On Wed, 4 Feb 2026 01:17:25 -0800, atish.patra@...ux.dev wrote:

> > The RISC-V SBI PMU driver disables all PMU counters during initialization
> > via pmu_sbi_stop_all. For fixed counters CYCLE, TIME and INSTRET, this is
> > unnecessary for the following two reasons:
> >
> > 1. Some kernel driver code may directly read CYCLE and INSTRET to perform
> >     simple performance analysis.
> 
> Is this for some debugging purpose to read the instret/cycle count at 
> boot time or real use case for driver performance analysis ?
> 
> If it is the latter, that will be problematic for various reasons such 
> as context switching will lead to inaccurate numbers.

Hi Atish,

Thanks for the reminder, but I might not be able to provide specific scenarios
due to our niche usage. Therefore, let's just discuss the legacy usage of
sysctl_perf_user_access.

> > 2. In legacy mode, user space directly reads CYCLE and INSTRET. (echo 2 >
> >     /proc/sys/kernel/perf_user_access)
> >
> > Therefore, We keep counting CYCLE, TIME and INSTRET.
> >
> > Signed-off-by: Chen Pei <cp0613@...ux.alibaba.com>
> > ---
> >   drivers/perf/riscv_pmu_sbi.c | 3 +++
> >   1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/perf/riscv_pmu_sbi.c b/drivers/perf/riscv_pmu_sbi.c
> > index 7dd282da67ce..93aaab324443 100644
> > --- a/drivers/perf/riscv_pmu_sbi.c
> > +++ b/drivers/perf/riscv_pmu_sbi.c
> > @@ -899,6 +899,9 @@ static int pmu_sbi_get_ctrinfo(int nctr, unsigned long *mask)
> >   
> >   static inline void pmu_sbi_stop_all(struct riscv_pmu *pmu)
> >   {
> > + /* We keep counting CYCLE, TIME and INSTRET. */
> > + pmu->cmask &= ~0x7;
> > +
> 
> This is incorrect. The cmask should be set based on the perf_user_access 
> value. We should not continue counting the CYCLE/INSTRET when legacy 
> mode is not set. if (sysctl_perf_user_access == SYSCTL_LEGACY) 
> csr_write(CSR_SCOUNTEREN, 0x7); else csr_write(CSR_SCOUNTEREN, 0x2);

I have a slightly different understanding here. Regarding perf_user_access, I think
it is only used to control user mode access permissions to CYCLE, TIME, and INSTRET
(via SCOUNTEREN), but whether the counters themselves are in a counting state is
another issue (via MCOUNTINHIBIT). I think the cmask in pmu_sbi_stop_all should
represent a counter to stop the counting, rather than a permission configuration.

The problem we are currently encountering is that even when switching to LEGACY mode,
CYCLE and INSTRET are not counting, so we want to change this default behavior so
that these three fixed counters are always in counting.

Sorry for the late reply. I've reviewed some previous related discussions, and it
seems that using time is more reasonable between cycle and time. However, for some
small code snippets, there is a need to use cycle and instant (at least instant),
so keeping them constantly counting doesn't seem to have any downsides.

Thanks,
Pei

> >    /*
> >     * No need to check the error because we are disabling all the counters
> >     * which may include counters that are not enabled yet.