[PATCH 1/3] drm/xe/guc: Demote the H2G retry log message to debug
Matthew Brost
matthew.brost at intel.com
Tue Jun 25 21:42:11 UTC 2024
On Tue, Jun 25, 2024 at 04:12:56PM +0200, Michal Wajdeczko wrote:
> The G2H RETRY message sent by the GuC does not necessary indicate
> any serious problem and can be a part of the normal communication
> flow. Switch the log level from warning to more appropriate debug.
> This will also let the CI ignore these logs which were seen in few
> SR-IOV scenarios.
>
> While at it, use hex to print the reason and add missing \n.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
> Cc: Matthew Brost <matthew.brost at intel.com>
Reviewed-by: Matthew Brost <matthew.brost at intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_ct.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
> index b4137fe195a4..91a8a969a6ad 100644
> --- a/drivers/gpu/drm/xe/xe_guc_ct.c
> +++ b/drivers/gpu/drm/xe/xe_guc_ct.c
> @@ -877,8 +877,8 @@ static int guc_ct_send_recv(struct xe_guc_ct *ct, const u32 *action, u32 len,
> }
>
> if (g2h_fence.retry) {
> - xe_gt_warn(gt, "H2G retry, action 0x%04x, reason %u",
> - action[0], g2h_fence.reason);
> + xe_gt_dbg(gt, "H2G action %#x retrying: reason %#x\n",
> + action[0], g2h_fence.reason);
> goto retry;
> }
> if (g2h_fence.fail) {
> --
> 2.43.0
>
More information about the Intel-xe
mailing list