From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Aditya Garg <gargaditya08@live.com>
Cc: Sven Peter <sven@svenpeter.dev>,
Thomas Zimmermann <tzimmermann@suse.de>,
Aun-Ali Zaidi <admin@kodeit.net>,
Maxime Ripard <mripard@kernel.org>,
"airlied@redhat.com" <airlied@redhat.com>,
Simona Vetter <simona@ffwll.ch>, Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"apw@canonical.com" <apw@canonical.com>,
"joe@perches.com" <joe@perches.com>,
"dwaipayanray1@gmail.com" <dwaipayanray1@gmail.com>,
"lukas.bulwahn@gmail.com" <lukas.bulwahn@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Hector Martin <marcan@marcan.st>,
"asahi@lists.linux.dev" <asahi@lists.linux.dev>
Subject: Re: [PATCH 1/2] lib/vsprintf: Add support for generic FourCCs by extending %p4cc
Date: Thu, 13 Mar 2025 10:48:51 +0200 [thread overview]
Message-ID: <Z9Kb8zMJgmSP-rgD@smile.fi.intel.com> (raw)
In-Reply-To: <47AE7FCD-0F30-4379-ADE9-090A15ACD58F@live.com>
On Thu, Mar 13, 2025 at 07:26:05AM +0000, Aditya Garg wrote:
> > On 13 Mar 2025, at 12:58 AM, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > On Wed, Mar 12, 2025 at 07:14:36PM +0000, Aditya Garg wrote:
> >>> On 12 Mar 2025, at 9:05 PM, Sven Peter <sven@svenpeter.dev> wrote:
> >>> On Wed, Mar 12, 2025, at 13:03, Aditya Garg wrote:
...
> >>> I don't have a strong opinion either way: for SMC I just need to print
> >>> FourCC keys for debugging / information in a few places.
> >>>
> >>> I'm preparing the SMC driver for upstreaming again (after a two year delay :-()
> >>> and was just going to use macros to print the SMC FourCC keys similar to
> >>> DRM_MODE_FMT/DRM_MODE_ARG for now to keep the series smaller and revisit
> >>> the topic later.
> >>>
> >>> Right now I have these in my local tree (only compile tested so far):
> >>>
> >>> #define SMC_KEY_FMT "%c%c%c%c (0x%08x)"
> >>> #define SMC_KEY_ARG(k) (k)>>24, (k)>>16, (k)>>8, (k), (k)
> >>
> >> That seems to be a nice alternative, which I guess Thomas was also suggesting.
> >
> > I don't think it's "nice". Each of the approaches has pros and cons.
> > You can start from bloat-o-meter here and compare it with your %p extension.
> >
> > Also, can you show the bloat-o-meter output for the vsprintf.c?
>
> Here are your outputs:
Thank you!
> ---------------------------------------------------------------------
> For appletbdrm:
>
> aditya@MacBook:~/linux$ ./scripts/bloat-o-meter $P4 $MACRO
> add/remove: 0/0 grow/shrink: 1/1 up/down: 64/-19 (45)
> Function old new delta
> appletbdrm_read_response 395 459 +64
> appletbdrm_probe 1786 1767 -19
> Total: Before=13418, After=13463, chg +0.34%
This is enough, no need to repeat this for every parameter.
> ---------------------------------------------------------------------
> For vsprintf:
>
> aditya@MacBook:~/linux$ ./scripts/bloat-o-meter $OLD $NEW
> add/remove: 0/0 grow/shrink: 1/0 up/down: 220/0 (220)
> Function old new delta
> fourcc_string 479 699 +220
> Total: Before=26454, After=26674, chg +0.83%
So, we get +220 bytes vs +43 bytes. It means if we found 5+ users, it worth
doing.
> >>> which are then used like this:
> >>>
> >>> dev_info(dev,
> >>> "Initialized (%d keys " SMC_KEY_FMT " .. " SMC_KEY_FMT ")\n",
> >>> smc->key_count, SMC_KEY_ARG(smc->first_key),
> >>> SMC_KEY_ARG(smc->last_key));
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-03-13 8:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 9:04 [PATCH 0/2] Use proper printk format in appletbdrm Aditya Garg
2025-03-12 9:05 ` [PATCH 1/2] lib/vsprintf: Add support for generic FourCCs by extending %p4cc Aditya Garg
2025-03-12 11:46 ` Thomas Zimmermann
2025-03-12 11:49 ` Aditya Garg
2025-03-12 11:58 ` Thomas Zimmermann
2025-03-12 12:03 ` Aditya Garg
2025-03-12 12:07 ` Aditya Garg
2025-03-12 15:34 ` Sven Peter
2025-03-12 19:14 ` Aditya Garg
2025-03-12 19:28 ` Andy Shevchenko
2025-03-12 19:35 ` Aditya Garg
2025-03-12 19:51 ` Andy Shevchenko
2025-03-13 7:26 ` Aditya Garg
2025-03-13 8:48 ` Andy Shevchenko [this message]
2025-03-13 8:53 ` Aditya Garg
2025-03-13 8:56 ` Andy Shevchenko
2025-03-13 9:13 ` Aditya Garg
2025-03-13 10:48 ` Petr Mladek
2025-03-13 11:06 ` Aditya Garg
2025-03-13 13:24 ` Andy Shevchenko
2025-03-13 17:40 ` Kees Cook
2025-03-13 17:42 ` Aditya Garg
2025-03-14 0:05 ` Kees Cook
2025-03-12 9:06 ` [PATCH 2/2] drm/appletbdm: use %p4cl instead of %p4cc Aditya Garg
2025-03-12 11:51 ` Thomas Zimmermann
2025-03-12 14:51 ` andriy.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=Z9Kb8zMJgmSP-rgD@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=admin@kodeit.net \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=asahi@lists.linux.dev \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=dwaipayanray1@gmail.com \
--cc=gargaditya08@live.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=lukas.bulwahn@gmail.com \
--cc=marcan@marcan.st \
--cc=mripard@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=simona@ffwll.ch \
--cc=sven@svenpeter.dev \
--cc=tzimmermann@suse.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