From: Jani Nikula <jani.nikula@linux.intel.com>
To: Krzysztof Karas <krzysztof.karas@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org,
Andi Shyti <andi.shyti@linux.intel.com>,
Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Krzysztof Niemiec <krzysztof.niemiec@intel.com>,
Krzysztof Karas <krzysztof.karas@intel.com>
Subject: Re: [PATCH v4 7/7] drm/i915/selftests: Use i915_* prints in i915_selftest.c
Date: Fri, 25 Sep 2026 13:51:32 +0300 [thread overview]
Message-ID: <50d3e5960b31018d569a4cbb15cd7e5b3858606d@intel.com> (raw)
In-Reply-To: <20260924120147.1305127-8-krzysztof.karas@intel.com>
On Thu, 24 Sep 2026, Krzysztof Karas <krzysztof.karas@intel.com> wrote:
> Move away from generic pr prints to drm device context aware
> i915_* versions.
So I think moving away from pr_* to drm_* logging is fine, and there's a
limited amount of that.
But the i915_* macros just open the door to an insane amount of churn
converting drm_* to i915_* everywhere in a driver that's essentially in
maintenance mode now, for no real benefit to anyone.
BR,
Jani.
>
> Assisted-by: GitHub-Copilot:claude-opus-5
> Assisted-by: GitHub-Copilot:claude-sonnet-5
> Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
> ---
> v4:
> - renamed from "Use drm_* prints in selftest headers" (the title
> did not match the change) and switched to the new i915_*
> prints instead of drm_*;
>
> drivers/gpu/drm/i915/selftests/i915_selftest.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/selftests/i915_selftest.c b/drivers/gpu/drm/i915/selftests/i915_selftest.c
> index 3adcfdab75ae..4e2566189879 100644
> --- a/drivers/gpu/drm/i915/selftests/i915_selftest.c
> +++ b/drivers/gpu/drm/i915/selftests/i915_selftest.c
> @@ -23,6 +23,8 @@
>
> #include <linux/random.h>
>
> +#include "i915_printk.h"
> +
> #include "gt/intel_gt.h"
> #include "gt/intel_gt_pm.h"
> #include "gt/intel_gt_regs.h"
> @@ -47,7 +49,7 @@ int i915_mock_sanitycheck(void)
>
> int i915_live_sanitycheck(struct drm_i915_private *i915)
> {
> - pr_info("%s: %s() - ok!\n", i915->drm.driver->name, __func__);
> + i915_info(i915, "%s() - ok!\n", __func__);
> return 0;
> }
>
> @@ -154,7 +156,7 @@ __wait_gsc_proxy_completed(struct drm_i915_private *i915)
>
> if (need_to_wait && wait_for(!__gsc_proxy_init_progressing(&i915->media_gt->uc.gsc),
> timeout_ms))
> - pr_warn(DRIVER_NAME "Timed out waiting for gsc_proxy_completion!\n");
> + i915_warn(i915, "Timed out waiting for gsc_proxy_completion!\n");
> }
>
> static void
> @@ -178,7 +180,7 @@ __wait_gsc_huc_load_completed(struct drm_i915_private *i915)
>
> if (need_to_wait &&
> wait_for(i915_sw_fence_done(&huc->delayed_load.fence), timeout_ms))
> - pr_warn(DRIVER_NAME "Timed out waiting for huc load via GSC!\n");
> + i915_warn(i915, "Timed out waiting for huc load via GSC!\n");
> }
>
> static struct mm_struct *get_selftest_mm(int u_pid_nr)
--
Jani Nikula, Intel
prev parent reply other threads:[~2026-09-25 10:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 12:01 [PATCH v4 0/7] drm/i915/selftests: Modernize printing in i915 selftests Krzysztof Karas
2026-09-24 12:01 ` [PATCH v4 1/7] drm/i915/selftests: Use gt_*/drm_* prints in core selftests Krzysztof Karas
2026-09-24 12:01 ` [PATCH v4 2/7] drm/i915: Add i915_* printer macros Krzysztof Karas
2026-09-24 13:58 ` Sebastian Brzezinka
2026-09-25 10:47 ` Jani Nikula
2026-09-29 12:00 ` Krzysztof Karas
2026-09-24 12:01 ` [PATCH v4 3/7] drm/i915/selftests: Use gt_*/i915_* prints in selftest helpers Krzysztof Karas
2026-09-24 12:01 ` [PATCH v4 4/7] drm/i915/gt/selftests: Use gt_* prints in aggregated gt selftests Krzysztof Karas
2026-09-24 12:01 ` [PATCH v4 5/7] drm/i915/gt/selftests: Use gt_* prints in gt standalone tests Krzysztof Karas
2026-09-24 12:01 ` [PATCH v4 6/7] drm/i915/gt/selftests: Use gt_* prints in gt selftest helpers Krzysztof Karas
2026-09-24 12:01 ` [PATCH v4 7/7] drm/i915/selftests: Use i915_* prints in i915_selftest.c Krzysztof Karas
2026-09-25 10:51 ` Jani Nikula [this message]
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=50d3e5960b31018d569a4cbb15cd7e5b3858606d@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=krzysztof.niemiec@intel.com \
--cc=sebastian.brzezinka@intel.com \
/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