From: "Arnd Bergmann" <arnd@arndb.de>
To: "Varad Gautam" <varadgautam@google.com>,
Linux-Arch <linux-arch@vger.kernel.org>
Cc: "Sai Prakash Ranjan" <quic_saipraka@quicinc.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] asm-generic/io.h: Skip trace helpers if rwmmio events are disabled
Date: Sat, 26 Jul 2025 18:22:27 +0200 [thread overview]
Message-ID: <f74d9899-6aba-4c8e-87b1-cd6ecc7772e6@app.fastmail.com> (raw)
In-Reply-To: <CAOLDJOJ98EccMJ4O3FyX4mSFtHnbQ4iwwXsHT2EbLL+KrXfvtw@mail.gmail.com>
On Thu, Jul 24, 2025, at 13:49, Varad Gautam wrote:
> On Wed, May 28, 2025 at 5:28 PM Varad Gautam <varadgautam@google.com> wrote:
>>
>> On Mon, Apr 28, 2025 at 9:41 PM Varad Gautam <varadgautam@google.com> wrote:
>> >
>> > On Mon, Apr 7, 2025 at 6:13 PM Varad Gautam <varadgautam@google.com> wrote:
>> > >
>> > > On Sun, Mar 30, 2025 at 6:42 PM Varad Gautam <varadgautam@google.com> wrote:
>> > > >
>> > > > With `CONFIG_TRACE_MMIO_ACCESS=y`, the `{read,write}{b,w,l,q}{_relaxed}()`
>> > > > mmio accessors unconditionally call `log_{post_}{read,write}_mmio()`
>> > > > helpers, which in turn call the ftrace ops for `rwmmio` trace events
>> > > >
>> > > > This adds a performance penalty per mmio accessor call, even when
>> > > > `rwmmio` events are disabled at runtime (~80% overhead on local
>> > > > measurement).
>> > > >
>> > > > Guard these with `tracepoint_enabled()`.
>> > > >
>> > > > Signed-off-by: Varad Gautam <varadgautam@google.com>
>> > > > Fixes: 210031971cdd ("asm-generic/io: Add logging support for MMIO accessors")
>> > > > Cc: <stable@vger.kernel.org>
>> > >
>> > > Ping.
>> > >
>> >
>> > Ping.
>> >
>>
>> Ping. Arnd, can this be picked up into the asm-generic tree?
>>
>
> Ping.
I'm sorry I keep missing this one. It's really too late again for
the merge window, so it won't be in 6.17 either, but I've applied
it locally in my asm-generic branch that I'm planning for 6.18
so I hope I won't miss it again.
I currently have nothing queued up for 6.17 at all, but I already
have some of my own patches that I plan to submit for review after
the merge window and merge through the asm-generic tree.
Arnd
next prev parent reply other threads:[~2025-07-26 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-30 16:42 Varad Gautam
2025-04-07 16:13 ` Varad Gautam
2025-04-28 19:41 ` Varad Gautam
2025-05-28 11:58 ` Varad Gautam
2025-07-24 11:49 ` Varad Gautam
2025-07-26 16:22 ` Arnd Bergmann [this message]
2025-09-23 11:07 ` Varad Gautam
2025-09-24 14:25 ` Arnd Bergmann
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=f74d9899-6aba-4c8e-87b1-cd6ecc7772e6@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_saipraka@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=varadgautam@google.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®