[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yv+hwyrQtBjc69Yd@sirena.org.uk>
Date: Fri, 19 Aug 2022 15:44:19 +0100
From: Mark Brown <broonie@...nel.org>
To: Dmitry Rokosov <DDRokosov@...rdevices.ru>
Cc: Marc Zyngier <maz@...nel.org>,
"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 Fri, Aug 19, 2022 at 01:31:35PM +0000, Dmitry Rokosov wrote:
> On Fri, Aug 19, 2022 at 01:07:47PM +0100, Mark Brown wrote:
> > 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.
> No any additional discussion before. I've added your address to all emails
> which I sent.
I assume you copied in Thomas, Rasmus and Marc for some reason?
> Why do you think it this patch will bring overhead to regmap? AFAK, when
> tracepoint is disabled, tracepoint fast assign operation shouldn't be
> executed. In other words, memcpy will not be applied.
To repeat I have not yet looked at your patch properly, one concern is
how we handle the marshalling which regmap does.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists