[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<TYCPR01MB67177BF90FEBAB9E20463012C141A@TYCPR01MB6717.jpnprd01.prod.outlook.com>
Date: Tue, 1 Jul 2025 06:13:57 +0000
From: "Koichi Okuno (Fujitsu)" <fj2767dz@...itsu.com>
To: 'Peter Zijlstra' <peterz@...radead.org>
CC: Will Deacon <will@...nel.org>, Mark Rutland <mark.rutland@....com>,
Jonathan Corbet <corbet@....net>, Catalin Marinas <catalin.marinas@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, Bjorn Andersson
<quic_bjorande@...cinc.com>, Geert Uytterhoeven <geert+renesas@...der.be>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, Konrad Dybcio
<konradybcio@...nel.org>, Neil Armstrong <neil.armstrong@...aro.org>, Arnd
Bergmann <arnd@...db.de>, NĂcolas F. R. A. Prado
<nfraprado@...labora.com>, Thomas Gleixner <tglx@...utronix.de>, Jonathan
Cameron <Jonathan.Cameron@...wei.com>, "linux-doc@...r.kernel.org"
<linux-doc@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "Koichi Okuno (Fujitsu)"
<fj2767dz@...itsu.com>
Subject: RE: [PATCH v5 2/2] perf: Fujitsu: Add the Uncore PCI PMU driver
Hi, Peter
Sorry for the late reply.
> On Tue, Jun 17, 2025 at 07:27:50PM +0900, Koichi Okuno wrote:
> > + pcipmu->pmu = (struct pmu) {
> > + .parent = dev,
> > + .task_ctx_nr = perf_invalid_context,
> > +
> > + .pmu_enable = fujitsu_pci__pmu_enable,
> > + .pmu_disable = fujitsu_pci__pmu_disable,
> > + .event_init = fujitsu_pci__event_init,
> > + .add = fujitsu_pci__event_add,
> > + .del = fujitsu_pci__event_del,
> > + .start = fujitsu_pci__event_start,
> > + .stop = fujitsu_pci__event_stop,
> > + .read = fujitsu_pci__event_read,
> > +
> > > + .attr_groups = fujitsu_pci_pmu_attr_grps,
> > + .capabilities = PERF_PMU_CAP_NO_EXCLUDE,
>
> Should these drivers not also have PERF_PMU_CAP_NO_INTERRUPT ? Per them
> being uncore they cannot generate samples.
Even now, the fujitsu_pci__event_init() function rejects sampling events
before checking PERF_PMU_CAP_NO_INTERRUPT in core.c.
However, I think it is correct to have PERF_PMU_CAP_NO_INTERRUPT which
means not being able to sample, so I will add NO_INTERRUPT in the next
version.
Best Regards,
Koichi Okuno
Powered by blists - more mailing lists