From: "Piotr Piórkowski" <piotr.piorkowski@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 3/4] drm/xe/pf: Update LMTT to use tile-based messages
Date: Mon, 6 Oct 2025 15:30:08 +0200 [thread overview]
Message-ID: <20251006133008.j4t7kytgfwglfqlb@intel.com> (raw)
In-Reply-To: <20251005133641.2651-4-michal.wajdeczko@intel.com>
Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on nie [2025-paź-05 15:36:39 +0200]:
> Since now we have tile-based SR-IOV printk macros, there is no
> need to manually prepare the LMTT specific warning message (that
> is now upgraded to proper error level message) nor to use generic
> debug message without tile/LMTT identification.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
> drivers/gpu/drm/xe/xe_lmtt.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_lmtt.c b/drivers/gpu/drm/xe/xe_lmtt.c
> index 62fc5a1a332d..4dc1de482eee 100644
> --- a/drivers/gpu/drm/xe/xe_lmtt.c
> +++ b/drivers/gpu/drm/xe/xe_lmtt.c
> @@ -17,7 +17,7 @@
> #include "xe_mmio.h"
> #include "xe_res_cursor.h"
> #include "xe_sriov.h"
> -#include "xe_sriov_printk.h"
> +#include "xe_tile_sriov_printk.h"
>
> /**
> * DOC: Local Memory Translation Table
> @@ -32,7 +32,7 @@
> */
>
> #define lmtt_assert(lmtt, condition) xe_tile_assert(lmtt_to_tile(lmtt), condition)
> -#define lmtt_debug(lmtt, msg...) xe_sriov_dbg_verbose(lmtt_to_xe(lmtt), "LMTT: " msg)
> +#define lmtt_debug(lmtt, msg...) xe_tile_sriov_dbg_verbose(lmtt_to_tile(lmtt), "LMTT: " msg)
>
> static bool xe_has_multi_level_lmtt(struct xe_device *xe)
> {
> @@ -267,15 +267,14 @@ static int lmtt_invalidate_hw(struct xe_lmtt *lmtt)
> */
> void xe_lmtt_invalidate_hw(struct xe_lmtt *lmtt)
> {
> - struct xe_device *xe = lmtt_to_xe(lmtt);
> int err;
>
> - lmtt_assert(lmtt, IS_SRIOV_PF(xe));
> + lmtt_assert(lmtt, IS_SRIOV_PF(lmtt_to_xe(lmtt)));
>
> err = lmtt_invalidate_hw(lmtt);
> if (err)
> - xe_sriov_warn(xe, "LMTT%u invalidation failed (%pe)",
> - lmtt_to_tile(lmtt)->id, ERR_PTR(err));
> + xe_tile_sriov_err(lmtt_to_tile(lmtt), "LMTT invalidation failed (%pe)",
> + ERR_PTR(err));
> }
LGTM:
Reviewed-by: Piotr Piórkowski <piotr.piorkowski@intel.com>
>
> static void lmtt_write_pte(struct xe_lmtt *lmtt, struct xe_lmtt_pt *pt,
> --
> 2.47.1
>
--
next prev parent reply other threads:[~2025-10-06 13:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-05 13:36 [PATCH 0/4] Update tile-based messages Michal Wajdeczko
2025-10-05 13:36 ` [PATCH 1/4] drm/xe: Update SRIOV printk macros Michal Wajdeczko
2025-10-06 13:03 ` Piotr Piórkowski
2025-10-05 13:36 ` [PATCH 2/4] drm/xe: Add tile-based " Michal Wajdeczko
2025-10-06 13:27 ` Piotr Piórkowski
2025-10-05 13:36 ` [PATCH 3/4] drm/xe/pf: Update LMTT to use tile-based messages Michal Wajdeczko
2025-10-06 13:30 ` Piotr Piórkowski [this message]
2025-10-05 13:36 ` [PATCH 4/4] drm/xe: Update MEMIRQ to use tile-based printk macros Michal Wajdeczko
2025-10-06 13:32 ` Piotr Piórkowski
2025-10-05 13:42 ` ✗ CI.checkpatch: warning for Update tile-based messages Patchwork
2025-10-05 13:43 ` ✓ CI.KUnit: success " Patchwork
2025-10-05 14:24 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-05 15:33 ` ✓ Xe.CI.Full: " 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=20251006133008.j4t7kytgfwglfqlb@intel.com \
--to=piotr.piorkowski@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@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