From: John Harrison <john.c.harrison@intel.com>
To: <Intel-GFX@Lists.FreeDesktop.Org>
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH 2/3] drm/i915/guc: Update log for unsolicited CTB response
Date: Tue, 30 May 2023 14:02:36 -0700 [thread overview]
Message-ID: <948849e9-b94a-a747-b389-1b359a1d3049@intel.com> (raw)
In-Reply-To: <20230526235538.2230780-3-John.C.Harrison@Intel.com>
On 5/26/2023 16:55, John.C.Harrison@Intel.com wrote:
> From: Michal Wajdeczko <michal.wajdeczko@intel.com>
>
> Instead of printing message fence twice, include HXG header of the
> unexpected message and its len.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: John Harrison <John.C.Harrison@Intel.com>
> ---
> drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
> index af52ed4ffc7fb..3a71bb582089e 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
> @@ -994,9 +994,8 @@ static int ct_handle_response(struct intel_guc_ct *ct, struct ct_incoming_msg *r
> break;
> }
> if (!found) {
> - CT_ERROR(ct, "Unsolicited response (fence %u)\n", fence);
> - CT_ERROR(ct, "Could not find fence=%u, last_fence=%u\n", fence,
> - ct->requests.last_fence);
> + CT_ERROR(ct, "Unsolicited response message: len %u, data %#x (fence %u, last %u)\n",
> + len, hxg[0], fence, ct->requests.last_fence);
> list_for_each_entry(req, &ct->requests.pending, link)
> CT_ERROR(ct, "request %u awaits response\n",
> req->fence);
next prev parent reply other threads:[~2023-05-30 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 23:55 [Intel-gfx] [PATCH 0/3] Use FAST_REQUEST mechanism for non-blocking H2G calls John.C.Harrison
2023-05-26 23:55 ` [Intel-gfx] [PATCH 1/3] drm/i915/guc: Use FAST_REQUEST " John.C.Harrison
2023-05-30 21:02 ` John Harrison
2023-05-26 23:55 ` [Intel-gfx] [PATCH 2/3] drm/i915/guc: Update log for unsolicited CTB response John.C.Harrison
2023-05-30 21:02 ` John Harrison [this message]
2023-05-26 23:55 ` [Intel-gfx] [PATCH 3/3] drm/i915/guc: Track all sent actions to GuC John.C.Harrison
2023-05-30 21:06 ` John Harrison
2023-05-27 0:22 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Use FAST_REQUEST mechanism for non-blocking H2G calls Patchwork
2023-05-27 0:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-27 23:41 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=948849e9-b94a-a747-b389-1b359a1d3049@intel.com \
--to=john.c.harrison@intel.com \
--cc=DRI-Devel@Lists.FreeDesktop.Org \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
/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