Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: <saurabhg.gupta@intel.com>, <alex.zuo@intel.com>,
	<matthew.d.roper@intel.com>, <rodrigo.vivi@intel.com>,
	<tejas.upadhyay@intel.com>
Subject: Re: [PATCH v3 1/7] drm/xe: s/xe_device_get_gt/xe_device_lookup_gt
Date: Tue, 14 Oct 2025 19:17:18 +0200	[thread overview]
Message-ID: <02b2088b-1b61-4774-bef4-33b3d1ef44d5@intel.com> (raw)
In-Reply-To: <20251014164758.125598-10-jonathan.cavitt@intel.com>



On 10/14/2025 6:48 PM, Jonathan Cavitt wrote:
> Replace the function name xe_device_get_gt with xe_device_lookup_gt to
> better illustrate it's capacity to return NULL in some cases.
> 

my suggestion was little different: introduce _new_ helper that can't fail
so the tool will not complain, and use it where we are sure we get a valid gt

renaming main function and then adding dedicated helper (that only wraps 
the original one) is not solving any problem at all

if we don't want to reuse/abuse existing xe_root_mmio_gt() then maybe just
add something similar but renamed for dedicated use case:

static inline struct xe_gt *xe_device_primary_gt(struct xe_device *xe)
{
	return xe_device_get_root_tile(xe)->primary_gt;
}

and start by using it as replacement for xe_device_get_gt(xe, 0)
where we known that checks are redundant/not needed (kunit/sriov)

then update remaining usages of xe_device_get_gt(xe, id) by
adding proper NULL check as needed

> Suggested-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Suggested-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> ---
>  drivers/gpu/drm/xe/tests/xe_guc_buf_kunit.c   |  2 +-
>  drivers/gpu/drm/xe/tests/xe_guc_db_mgr_test.c |  2 +-
>  drivers/gpu/drm/xe/tests/xe_guc_g2g_test.c    |  2 +-
>  drivers/gpu/drm/xe/tests/xe_guc_id_mgr_test.c |  2 +-
>  drivers/gpu/drm/xe/tests/xe_guc_relay_test.c  |  8 ++++----
>  drivers/gpu/drm/xe/xe_device.h                |  4 ++--
>  drivers/gpu/drm/xe/xe_eu_stall.c              |  2 +-
>  drivers/gpu/drm/xe/xe_exec_queue.c            |  2 +-
>  drivers/gpu/drm/xe/xe_guc.c                   |  2 +-
>  drivers/gpu/drm/xe/xe_hw_engine.c             |  4 ++--
>  drivers/gpu/drm/xe/xe_pmu.c                   | 10 +++++-----
>  drivers/gpu/drm/xe/xe_query.c                 |  2 +-
>  drivers/gpu/drm/xe/xe_sriov_vf.c              |  2 +-
>  13 files changed, 22 insertions(+), 22 deletions(-)

  reply	other threads:[~2025-10-14 17:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 16:47 [PATCH v3 0/7] drm/xe: Guard against NULL return for xe_device_get_gt Jonathan Cavitt
2025-10-14 16:48 ` [PATCH v3 1/7] drm/xe: s/xe_device_get_gt/xe_device_lookup_gt Jonathan Cavitt
2025-10-14 17:17   ` Michal Wajdeczko [this message]
2025-10-14 17:21     ` Cavitt, Jonathan
2025-10-14 16:48 ` [PATCH v3 2/7] drm/xe: Don't call xe_device_lookup_gt twice in xe_hw_engine_lookup Jonathan Cavitt
2025-10-14 16:48 ` [PATCH v3 3/7] drm/xe/xe_device: Reintroduce xe_device_get_gt Jonathan Cavitt
2025-10-14 17:28   ` Michal Wajdeczko
2025-10-14 16:48 ` [PATCH v3 4/7] drm/xe: Guard against NULL GT in xe_sriov_vf.c Jonathan Cavitt
2025-10-14 17:32   ` Michal Wajdeczko
2025-10-14 17:34     ` Cavitt, Jonathan
2025-10-14 16:48 ` [PATCH v3 5/7] drm/xe: Guard against NULL GT in xe_pmu.c Jonathan Cavitt
2025-10-14 16:48 ` [PATCH v3 6/7] drm/xe: Guard against NULL GT in xe_guc.c Jonathan Cavitt
2025-10-14 16:48 ` [PATCH v3 7/7] drm/xe/tests: Use any available GT for testing Jonathan Cavitt
2025-10-14 17:51   ` Michal Wajdeczko
2025-10-14 18:06     ` Cavitt, Jonathan
2025-10-14 16:55 ` ✓ CI.KUnit: success for drm/xe: Guard against NULL return for xe_device_get_gt Patchwork
2025-10-14 17:44 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-15  2:37 ` ✗ Xe.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=02b2088b-1b61-4774-bef4-33b3d1ef44d5@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=alex.zuo@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=saurabhg.gupta@intel.com \
    --cc=tejas.upadhyay@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