All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/dp: use seq buf for printing rates
Date: Wed, 27 Nov 2024 19:24:58 +0200	[thread overview]
Message-ID: <87mshkwpw5.fsf@intel.com> (raw)
In-Reply-To: <173272067132.9041.672991565423824805@intel.com>

On Wed, 27 Nov 2024, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
> Quoting Jani Nikula (2024-11-27 10:18:38-03:00)
>>Hand rolling the buffer overflow handling with snprintf() is a bit
>>tedious. The seq_buf interface is made for this. Switch to it.
>
> Cool! Today I learned a new kernel interface. :-)

\o/

>>
>>Use struct intel_display while at it.
>>
>>Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>>---
>> drivers/gpu/drm/i915/display/intel_dp.c | 36 ++++++++++---------------
>> 1 file changed, 14 insertions(+), 22 deletions(-)
>>
>>diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
>>index 053a9a4182e7..4471c8fcd478 100644
>>--- a/drivers/gpu/drm/i915/display/intel_dp.c
>>+++ b/drivers/gpu/drm/i915/display/intel_dp.c
>>@@ -28,6 +28,7 @@
>> #include <linux/export.h>
>> #include <linux/i2c.h>
>> #include <linux/notifier.h>
>>+#include <linux/seq_buf.h>
>> #include <linux/slab.h>
>> #include <linux/sort.h>
>> #include <linux/string_helpers.h>
>>@@ -1506,41 +1507,32 @@ bool intel_dp_source_supports_tps4(struct drm_i915_private *i915)
>>         return DISPLAY_VER(i915) >= 10;
>> }
>> 
>>-static void snprintf_int_array(char *str, size_t len,
>>-                               const int *array, int nelem)
>>+static void seq_buf_print_array(struct seq_buf *s, const int *array, int nelem)
>> {
>>         int i;
>> 
>>-        str[0] = '\0';
>>-
>>-        for (i = 0; i < nelem; i++) {
>>-                int r = snprintf(str, len, "%s%d", i ? ", " : "", array[i]);
>>-                if (r >= len)
>>-                        return;
>>-                str += r;
>>-                len -= r;
>>-        }
>>+        for (i = 0; i < nelem; i++)
>>+                seq_buf_printf(s, "%s%d", i ? ", " : "", array[i]);
>> }
>> 
>> static void intel_dp_print_rates(struct intel_dp *intel_dp)
>> {
>>-        struct drm_i915_private *i915 = dp_to_i915(intel_dp);
>>-        char str[128]; /* FIXME: too big for stack? */
>>+        struct intel_display *display = to_intel_display(intel_dp);
>>+        DECLARE_SEQ_BUF(s, 128); /* FIXME: too big for stack? */
>
> I wonder if just using drm_dbg_printer() would make things simpler,
> without requiring a buffer.

Mmh, that's always line based, isn't it? It would result in each rate
getting printed on its own line, which is too spammy.

> Anyway, the patch looks good to me, so:
>
> Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>

Thanks!

>
>> 
>>         if (!drm_debug_enabled(DRM_UT_KMS))
>>                 return;
>> 
>>-        snprintf_int_array(str, sizeof(str),
>>-                           intel_dp->source_rates, intel_dp->num_source_rates);
>>-        drm_dbg_kms(&i915->drm, "source rates: %s\n", str);
>>+        seq_buf_print_array(&s, intel_dp->source_rates, intel_dp->num_source_rates);
>>+        drm_dbg_kms(display->drm, "source rates: %s\n", seq_buf_str(&s));
>> 
>>-        snprintf_int_array(str, sizeof(str),
>>-                           intel_dp->sink_rates, intel_dp->num_sink_rates);
>>-        drm_dbg_kms(&i915->drm, "sink rates: %s\n", str);
>>+        seq_buf_clear(&s);
>>+        seq_buf_print_array(&s, intel_dp->sink_rates, intel_dp->num_sink_rates);
>>+        drm_dbg_kms(display->drm, "sink rates: %s\n", seq_buf_str(&s));
>> 
>>-        snprintf_int_array(str, sizeof(str),
>>-                           intel_dp->common_rates, intel_dp->num_common_rates);
>>-        drm_dbg_kms(&i915->drm, "common rates: %s\n", str);
>>+        seq_buf_clear(&s);
>>+        seq_buf_print_array(&s, intel_dp->common_rates, intel_dp->num_common_rates);
>>+        drm_dbg_kms(display->drm, "common rates: %s\n", seq_buf_str(&s));
>> }
>> 
>> static int forced_link_rate(struct intel_dp *intel_dp)
>>-- 
>>2.39.5
>>

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-11-27 17:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 13:18 [PATCH] drm/i915/dp: use seq buf for printing rates Jani Nikula
2024-11-27 13:26 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-27 13:26 ` ✓ CI.checkpatch: " Patchwork
2024-11-27 13:28 ` ✓ CI.KUnit: " Patchwork
2024-11-27 13:46 ` ✓ CI.Build: " Patchwork
2024-11-27 13:48 ` ✓ CI.Hooks: " Patchwork
2024-11-27 13:49 ` ✗ CI.checksparse: warning " Patchwork
2024-11-27 14:07 ` ✓ Xe.CI.BAT: success " Patchwork
2024-11-27 14:14 ` ✗ i915.CI.BAT: failure " Patchwork
2024-11-28 13:03   ` Jani Nikula
2024-11-29 11:23     ` Illipilli, TejasreeX
2024-11-27 15:17 ` [PATCH] " Gustavo Sousa
2024-11-27 17:24   ` Jani Nikula [this message]
2024-11-27 18:04     ` Gustavo Sousa
2024-11-27 15:34 ` Raag Jadav
2024-11-27 17:06   ` Jani Nikula
2024-11-27 17:40 ` ✗ Xe.CI.Full: failure for " Patchwork
2024-11-29 10:53 ` ✓ i915.CI.BAT: success " Patchwork
2024-11-29 14:03 ` ✗ i915.CI.Full: failure " Patchwork

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=87mshkwpw5.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.