From: Mark Brown <broonie@kernel.org>
To: Dmitry Rokosov <DDRokosov@sberdevices.ru>
Cc: Marc Zyngier <maz@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"rafael@kernel.org" <rafael@kernel.org>,
"jic23@kernel.org" <jic23@kernel.org>,
"linux@rasmusvillemoes.dk>" <linux@rasmusvillemoes.dk>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
kernel <kernel@sberdevices.ru>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] regmap: introduce value tracing for regmap bulk operations
Date: Fri, 19 Aug 2022 13:07:47 +0100 [thread overview]
Message-ID: <Yv99E0mrPI0qG66I@sirena.org.uk> (raw)
In-Reply-To: <20220818174441.arh7otvrkzg5uk3s@CAB-WSD-L081021.sigma.sbrf.ru>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
On Thu, Aug 18, 2022 at 05:44:23PM +0000, Dmitry Rokosov wrote:
> On Thu, Aug 18, 2022 at 04:43:45PM +0100, Mark Brown wrote:
> > At the minute we don't put the actual data for the bulk transfers into
> > the trace so the information simply isn't there.
> What do you think about the patch? Can we use the separate trace event
> class, or do we have to add these tracepoints to some existing class, like
> regmap_block?
I didn't realise that was even a question, but then there seems to be
some discussion I've not seen given the CCing going on. The biggest
issue is do we even want the overhead but I'll need to find time to look
at this properly.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-08-19 12:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 18:14 [PATCH v1] regmap: introduce value tracing for regmap bulk operations Dmitry Rokosov
2022-08-18 12:15 ` Dmitry Rokosov
2022-08-18 13:49 ` Marc Zyngier
2022-08-18 15:43 ` Mark Brown
2022-08-18 17:44 ` Dmitry Rokosov
2022-08-19 12:07 ` Mark Brown [this message]
2022-08-19 13:31 ` Dmitry Rokosov
2022-08-19 14:44 ` Mark Brown
2022-08-19 15:22 ` Dmitry Rokosov
2022-08-19 14:25 ` Marc Zyngier
2022-08-19 14:38 ` Mark Brown
2022-08-19 15:31 ` Dmitry Rokosov
2022-08-18 17:02 ` Dmitry Rokosov
2022-08-23 16:47 ` Mark Brown
2022-08-23 21:39 ` Andy Shevchenko
2022-08-31 0:45 ` Dmitry Rokosov
2022-09-01 13:16 ` Andy Shevchenko
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=Yv99E0mrPI0qG66I@sirena.org.uk \
--to=broonie@kernel.org \
--cc=DDRokosov@sberdevices.ru \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=kernel@sberdevices.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=maz@kernel.org \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
/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