From: Joe Perches <joe@perches.com>
To: Jim Cromie <jim.cromie@gmail.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] amdgpu_ucode: reduce number of pr_debug calls
Date: Wed, 29 Sep 2021 19:08:51 -0700 [thread overview]
Message-ID: <a61f6bc2dc18397de92e4b7cdd9b37e2dff7e114.camel@perches.com> (raw)
In-Reply-To: <20210930014427.14239-3-jim.cromie@gmail.com>
On Wed, 2021-09-29 at 19:44 -0600, Jim Cromie wrote:
> There are blocks of DRM_DEBUG calls, consolidate their args into
> single calls. With dynamic-debug in use, each callsite consumes 56
> bytes of callsite data, and this patch removes about 65 calls, so
> it saves ~3.5kb.
>
> no functional changes.
No functional change, but an output logging content change.
> RFC: this creates multi-line log messages, does that break any syslog
> conventions ?
It does change the output as each individual DRM_DEBUG is a call to
__drm_dbg which is effectively:
printk(KERN_DEBUG "[" DRM_NAME ":%ps] %pV",
__builtin_return_address(0), &vaf);
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ucode.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ucode.c
[]
> @@ -30,17 +30,26 @@
>
>
> static void amdgpu_ucode_print_common_hdr(const struct common_firmware_header *hdr)
> {
> - DRM_DEBUG("size_bytes: %u\n", le32_to_cpu(hdr->size_bytes));
> - DRM_DEBUG("header_size_bytes: %u\n", le32_to_cpu(hdr->header_size_bytes));
[]
> + DRM_DEBUG("size_bytes: %u\n"
> + "header_size_bytes: %u\n"
etc...
next prev parent reply other threads:[~2021-09-30 2:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 1:44 [PATCH 0/4] drm: maintenance patches for 5.15-rcX Jim Cromie
2021-09-30 1:44 ` [PATCH 1/4] drm: fix doc grammar error Jim Cromie
2021-09-30 1:44 ` [PATCH 2/4] amdgpu_ucode: reduce number of pr_debug calls Jim Cromie
2021-09-30 2:08 ` Joe Perches [this message]
2021-09-30 3:37 ` jim.cromie
2021-09-30 1:44 ` [PATCH 3/4] nouveau: fold multiple DRM_DEBUG_DRIVERs together Jim Cromie
2021-09-30 1:44 ` [PATCH 4/4] i915/gvt: remove spaces in pr_debug "gvt: core:" etc prefixes Jim Cromie
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=a61f6bc2dc18397de92e4b7cdd9b37e2dff7e114.camel@perches.com \
--to=joe@perches.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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