Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Harrison <john.c.harrison@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	<intel-gfx@lists.freedesktop.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc: Improve debug message on context reset notification
Date: Wed, 1 Feb 2023 10:38:33 -0800	[thread overview]
Message-ID: <7aeb8cf2-aa85-07e4-0636-79b16aa4a7db@intel.com> (raw)
In-Reply-To: <20230131214413.1879-1-michal.wajdeczko@intel.com>

On 1/31/2023 13:44, Michal Wajdeczko wrote:
> Just recently we switched over to new GuC oriented log macros but in
> the meantime yet another message was added that we missed to update.
>
> While around improve that new message by adding engine name and use
> existing helpers to check for context state.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: John Harrison <John.C.Harrison@Intel.com>

> ---
>   drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 7 ++++---
>   1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> index 53f3ed3244d5..be495e657d66 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> @@ -4660,9 +4660,10 @@ static void guc_handle_context_reset(struct intel_guc *guc,
>   {
>   	trace_intel_context_reset(ce);
>   
> -	drm_dbg(&guc_to_gt(guc)->i915->drm, "Got GuC reset of 0x%04X, exiting = %d, banned = %d\n",
> -		ce->guc_id.id, test_bit(CONTEXT_EXITING, &ce->flags),
> -		test_bit(CONTEXT_BANNED, &ce->flags));
> +	guc_dbg(guc, "Got context reset notification: 0x%04X on %s, exiting = %s, banned = %s\n",
> +		ce->guc_id.id, ce->engine->name,
> +		str_yes_no(intel_context_is_exiting(ce)),
> +		str_yes_no(intel_context_is_banned(ce)));
>   
>   	if (likely(intel_context_is_schedulable(ce))) {
>   		capture_error_state(guc, ce);


      parent reply	other threads:[~2023-02-01 18:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 21:44 [Intel-gfx] [PATCH] drm/i915/guc: Improve debug message on context reset notification Michal Wajdeczko
2023-01-31 22:21 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-01-31 23:42 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-02-01 18:38 ` John Harrison [this message]

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=7aeb8cf2-aa85-07e4-0636-79b16aa4a7db@intel.com \
    --to=john.c.harrison@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@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