From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: "Koichi Okuno" <fj2767dz@fujitsu.com>,
"Will Deacon" <will@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Gowthami Thiagarajan" <gthiagarajan@marvell.com>,
"Linu Cherian" <lcherian@marvell.com>,
linux-arm-kernel@lists.infradead.org,
"Bjorn Andersson" <quic_bjorande@quicinc.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Peter Zijlstra" <peterz@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/2] perf: Fujitsu: Add the Uncore MAC PMU driver
Date: Fri, 15 Aug 2025 16:51:49 +0100 [thread overview]
Message-ID: <20250815165149.00004d60@huawei.com> (raw)
In-Reply-To: <ea3fda8c-2b7d-4902-9bda-d97d7b090cff@arm.com>
> > +static struct attribute *fujitsu_mac_pmu_events[] = {
> > + MAC_EVENT_ATTR(cycles, MAC_EVENT_CYCLES),
> > + MAC_EVENT_ATTR(read-count, MAC_EVENT_READ_COUNT),
> > + MAC_EVENT_ATTR(read-count-request, MAC_EVENT_READ_COUNT_REQUEST),
> > + MAC_EVENT_ATTR(read-count-return, MAC_EVENT_READ_COUNT_RETURN),
> > + MAC_EVENT_ATTR(read-count-request-pftgt, MAC_EVENT_READ_COUNT_REQUEST_PFTGT),
> > + MAC_EVENT_ATTR(read-count-request-normal, MAC_EVENT_READ_COUNT_REQUEST_NORMAL),
> > + MAC_EVENT_ATTR(read-count-return-pftgt-hit, MAC_EVENT_READ_COUNT_RETURN_PFTGT_HIT),
> > + MAC_EVENT_ATTR(read-count-return-pftgt-miss, MAC_EVENT_READ_COUNT_RETURN_PFTGT_MISS),
> > + MAC_EVENT_ATTR(read-wait, MAC_EVENT_READ_WAIT),
> > + MAC_EVENT_ATTR(write-count, MAC_EVENT_WRITE_COUNT),
> > + MAC_EVENT_ATTR(write-count-write, MAC_EVENT_WRITE_COUNT_WRITE),
> > + MAC_EVENT_ATTR(write-count-pwrite, MAC_EVENT_WRITE_COUNT_PWRITE),
> > + MAC_EVENT_ATTR(memory-read-count, MAC_EVENT_MEMORY_READ_COUNT),
> > + MAC_EVENT_ATTR(memory-write-count, MAC_EVENT_MEMORY_WRITE_COUNT),
> > + MAC_EVENT_ATTR(memory-pwrite-count, MAC_EVENT_MEMORY_PWRITE_COUNT),
> > + MAC_EVENT_ATTR(ea-mac, MAC_EVENT_EA_MAC),
> > + MAC_EVENT_ATTR(ea-memory, MAC_EVENT_EA_MEMORY),
> > + MAC_EVENT_ATTR(ea-memory-mac-write, MAC_EVENT_EA_MEMORY_MAC_WRITE),
> > + MAC_EVENT_ATTR(ea-ha, MAC_EVENT_EA_HA),
> I firmly maintain my opinion that if this is the only place the event
> numbers are referenced then the extra layer of macros actually makes it
> *harder* to read and follow, compared to simply:
>
> MAC_EVENT_ATTR(ea-ha, 0xa0),
>
> but that is very much just one reviewer's personal opinion :)
I'll second this suggestion! I failed to notice they were only used here.
Jonathan
next prev parent reply other threads:[~2025-08-15 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 3:47 [PATCH v7 0/2] perf: Fujitsu: Add Uncore MAC/PCI PMU driver Koichi Okuno
2025-08-15 3:47 ` [PATCH v7 1/2] perf: Fujitsu: Add the Uncore MAC " Koichi Okuno
2025-08-15 11:33 ` Jonathan Cameron
2025-08-15 12:39 ` Robin Murphy
2025-08-15 15:51 ` Jonathan Cameron [this message]
2025-09-04 6:37 ` Koichi Okuno (Fujitsu)
2025-08-15 3:47 ` [PATCH v7 2/2] perf: Fujitsu: Add the Uncore PCI " Koichi Okuno
2025-08-15 11:36 ` Jonathan Cameron
2025-08-15 12:59 ` Robin Murphy
2025-09-04 6:41 ` Koichi Okuno (Fujitsu)
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=20250815165149.00004d60@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=fj2767dz@fujitsu.com \
--cc=geert+renesas@glider.be \
--cc=gthiagarajan@marvell.com \
--cc=konradybcio@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lcherian@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.com \
--cc=peterz@infradead.org \
--cc=quic_bjorande@quicinc.com \
--cc=robin.murphy@arm.com \
--cc=tglx@linutronix.de \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).