[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yv5eMcmNOmyLmd++@sirena.org.uk>
Date: Thu, 18 Aug 2022 16:43:45 +0100
From: Mark Brown <broonie@...nel.org>
To: Marc Zyngier <maz@...nel.org>
Cc: Dmitry Rokosov <DDRokosov@...rdevices.ru>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"rafael@...nel.org" <rafael@...nel.org>,
"jic23@...nel.org" <jic23@...nel.org>,
"linux@...musvillemoes.dk>" <linux@...musvillemoes.dk>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"andy.shevchenko@...il.com" <andy.shevchenko@...il.com>,
kernel <kernel@...rdevices.ru>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1] regmap: introduce value tracing for regmap bulk
operations
On Thu, Aug 18, 2022 at 02:49:20PM +0100, Marc Zyngier wrote:
> I don't care much about regmap as a MMIO backend, but it strikes me as
> odd that you end up with multiple ways of logging the same stuff (with
> a memcpy in the middle of it).
> Why can't this be done with a small amount of trace post-processing?
At the minute we don't put the actual data for the bulk transfers into
the trace so the information simply isn't there.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists