From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 1/5] drm/xe: Export xe_step_name for kunit tests
Date: Fri, 13 Jun 2025 17:52:52 +0200 [thread overview]
Message-ID: <4bc609fa-168a-4601-864e-1b078ecb89f5@intel.com> (raw)
In-Reply-To: <20250613001438.678728-8-matthew.d.roper@intel.com>
On 13.06.2025 02:14, Matt Roper wrote:
> xe_step_name() is used by xe_assert(), so adding assertions to functions
> like xe_device_get_gt() will result in
>
> ERROR: modpost: "xe_step_name" [drivers/gpu/drm/xe/tests/xe_test.ko] undefined!
>
> while building the kunit tests. Export xe_step_name to avoid these
> build failures when adding assertions.
>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
this looks exactly as my patch from Feb [1] so it must be good ;)
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
[1] https://patchwork.freedesktop.org/patch/638883/?series=145269&rev=1
> ---
> drivers/gpu/drm/xe/xe_step.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_step.c b/drivers/gpu/drm/xe/xe_step.c
> index c77b5c317fa0..10e88f2c9615 100644
> --- a/drivers/gpu/drm/xe/xe_step.c
> +++ b/drivers/gpu/drm/xe/xe_step.c
> @@ -5,6 +5,7 @@
>
> #include "xe_step.h"
>
> +#include <kunit/visibility.h>
> #include <linux/bitfield.h>
>
> #include "xe_device.h"
> @@ -255,3 +256,4 @@ const char *xe_step_name(enum xe_step step)
> return "**";
> }
> }
> +EXPORT_SYMBOL_IF_KUNIT(xe_step_name);
next prev parent reply other threads:[~2025-06-13 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 0:14 [PATCH 0/5] Future-proof for multi-tile + multi-GT cases Matt Roper
2025-06-13 0:14 ` [PATCH 1/5] drm/xe: Export xe_step_name for kunit tests Matt Roper
2025-06-13 15:52 ` Michal Wajdeczko [this message]
2025-06-13 0:14 ` [PATCH 2/5] drm/xe: Track maximum GTs per tile on a per-platform basis Matt Roper
2025-06-13 20:32 ` Lucas De Marchi
2025-06-13 0:14 ` [PATCH 3/5] drm/xe/tests/pci: Ensure all platforms have a valid GT/tile count Matt Roper
2025-06-13 17:59 ` Michal Wajdeczko
2025-06-13 19:21 ` Michal Wajdeczko
2025-06-13 0:14 ` [PATCH 4/5] drm/xe: Assign GT IDs properly on multi-tile + multi-GT platforms Matt Roper
2025-06-13 0:14 ` [PATCH 5/5] drm/xe: Don't compare GT ID to GT count when determining valid GTs Matt Roper
2025-06-13 7:36 ` ✗ CI.checkpatch: warning for Future-proof for multi-tile + multi-GT cases Patchwork
2025-06-13 7:37 ` ✗ CI.KUnit: 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=4bc609fa-168a-4601-864e-1b078ecb89f5@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@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