From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/4] drm/i915/guc: Print error name on CTB (de)registration failure
Date: Wed, 18 Aug 2021 17:11:17 +0200 [thread overview]
Message-ID: <7bdb20cf-550f-9c65-5c9b-60cc87de33b2@intel.com> (raw)
In-Reply-To: <YR0XFp/Q+f8Todgk@phenom.ffwll.local>
On 18.08.2021 16:20, Daniel Vetter wrote:
> On Thu, Jul 01, 2021 at 05:55:11PM +0200, Michal Wajdeczko wrote:
>> Instead of plain error value (%d) print more user friendly error
>> name (%pe).
>>
>> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> ---
>> drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 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 a26bb55c0898..18d52c39f0c2 100644
>> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
>> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
>> @@ -167,8 +167,8 @@ static int ct_register_buffer(struct intel_guc_ct *ct, u32 type,
>> err = guc_action_register_ct_buffer(ct_to_guc(ct), type,
>> desc_addr, buff_addr, size);
>> if (unlikely(err))
>> - CT_ERROR(ct, "Failed to register %s buffer (err=%d)\n",
>> - guc_ct_buffer_type_to_str(type), err);
>> + CT_ERROR(ct, "Failed to register %s buffer (%pe)\n",
>> + guc_ct_buffer_type_to_str(type), ERR_PTR(err));
>
> errname() is what you want here, not this convoluted jumping through hoops
> to fake an error pointer.
nope, I was already trying that shortcut, but errname() is not exported
so we fail with
ERROR: modpost: "errname" [drivers/gpu/drm/i915/i915.ko] undefined!
so unless we add that export we must follow initial approach [1]
-Michal
[1]
https://cgit.freedesktop.org/drm/drm-tip/commit/?id=57f5677e535ba24b8926a7125be2ef8d7f09323c
>
> With that: Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>> return err;
>> }
>>
>> @@ -195,8 +195,8 @@ static int ct_deregister_buffer(struct intel_guc_ct *ct, u32 type)
>> int err = guc_action_deregister_ct_buffer(ct_to_guc(ct), type);
>>
>> if (unlikely(err))
>> - CT_ERROR(ct, "Failed to deregister %s buffer (err=%d)\n",
>> - guc_ct_buffer_type_to_str(type), err);
>> + CT_ERROR(ct, "Failed to deregister %s buffer (%pe)\n",
>> + guc_ct_buffer_type_to_str(type), ERR_PTR(err));
>> return err;
>> }
>>
>> --
>> 2.25.1
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
next prev parent reply other threads:[~2021-08-18 15:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 15:55 [Intel-gfx] [PATCH 0/4] drm/i915/guc: Improve CTB error handling Michal Wajdeczko
2021-07-01 15:55 ` [Intel-gfx] [PATCH 1/4] drm/i915/guc: Verify result from CTB (de)register action Michal Wajdeczko
2021-08-18 14:21 ` Daniel Vetter
2021-07-01 15:55 ` [Intel-gfx] [PATCH 2/4] drm/i915/guc: Print error name on CTB (de)registration failure Michal Wajdeczko
2021-08-18 14:20 ` Daniel Vetter
2021-08-18 15:11 ` Michal Wajdeczko [this message]
2021-08-18 16:35 ` Daniel Vetter
2021-08-18 19:12 ` Michal Wajdeczko
2021-08-19 8:35 ` Daniel Vetter
2021-07-01 15:55 ` [Intel-gfx] [PATCH 3/4] drm/i915/guc: Print error name on CTB send failure Michal Wajdeczko
2021-08-18 14:22 ` Daniel Vetter
2021-07-01 15:55 ` [Intel-gfx] [PATCH 4/4] drm/i915/guc: Move and improve error message for missed CTB reply Michal Wajdeczko
2021-08-18 14:24 ` Daniel Vetter
2021-07-01 20:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/guc: Improve CTB error handling Patchwork
2021-07-02 1:31 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=7bdb20cf-550f-9c65-5c9b-60cc87de33b2@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=daniel@ffwll.ch \
--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;
as well as URLs for NNTP newsgroup(s).