From 0dcdade9472358d1889d9040e5648c18ca86d075 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Piotr=20Pi=C3=B3rkowski?= Date: Tue, 21 Jul 2026 11:31:16 +0200 Subject: [PATCH] drm/xe/mert: Rate limit VF LMTT fault debug log MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A faulty or malicious VF may repeatedly trigger LMTT faults and generate many identical CATERR debug messages. Use xe_sriov_dbg_ratelimited() to reduce log spam while keeping useful debug information available. Reviewed-by: Lukasz Laguna Link: https://patch.msgid.link/20260721093116.4011940-3-piotr.piorkowski@intel.com Signed-off-by: Piotr Piórkowski --- drivers/gpu/drm/xe/xe_mert.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/xe/xe_mert.c b/drivers/gpu/drm/xe/xe_mert.c index f637df95418b..32700c19a1df 100644 --- a/drivers/gpu/drm/xe/xe_mert.c +++ b/drivers/gpu/drm/xe/xe_mert.c @@ -77,7 +77,7 @@ static void mert_handle_cat_error(struct xe_device *xe) xe_device_declare_wedged(xe); break; case CATERR_LMTT_FAULT: - xe_sriov_dbg(xe, "MERT: CAT_ERR: VF%u LMTT fault!\n", vfid); + xe_sriov_dbg_ratelimited(xe, "MERT: CAT_ERR: VF%u LMTT fault!\n", vfid); /* XXX: track/report malicious VF activity */ break; default: