Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Add caller info to xe_gt_reset_async
Date: Wed, 16 Oct 2024 16:57:58 +0200	[thread overview]
Message-ID: <44b59c01-ec83-4bc7-9054-1bbd54d3e146@intel.com> (raw)
In-Reply-To: <f57b1e3e-dbc9-4401-b2b8-0066213db11c@intel.com>


On 10/16/2024 4:44 PM, Matthew Auld wrote:
> On 16/10/2024 14:44, Nirmoy Das wrote:
>> Add caller info to the xe_gt_reset_async() to help debug issues.
>>
>> Cc: Matthew Auld <matthew.auld@intel.com>
>> Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/2874
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>> ---
>>   drivers/gpu/drm/xe/xe_gt.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_gt.c b/drivers/gpu/drm/xe/xe_gt.c
>> index 1c79660fb086..51324c7da0a9 100644
>> --- a/drivers/gpu/drm/xe/xe_gt.c
>> +++ b/drivers/gpu/drm/xe/xe_gt.c
>> @@ -834,7 +834,7 @@ static void gt_reset_worker(struct work_struct *w)
>>     void xe_gt_reset_async(struct xe_gt *gt)
>>   {
>> -    xe_gt_info(gt, "trying reset\n");
>> +    xe_gt_info(gt, "trying reset from %pS\n", __builtin_return_address(0));
>
> Probably ps is verbose enough?

Yes, that will work too. Re-sending.


Thanks,

Nirmoy

>
>>         /* Don't do a reset while one is already in flight */
>>       if (!xe_fault_inject_gt_reset() && xe_uc_reset_prepare(&gt->uc))

  reply	other threads:[~2024-10-16 15:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16 13:44 [PATCH] drm/xe: Add caller info to xe_gt_reset_async Nirmoy Das
2024-10-16 14:31 ` ✓ CI.Patch_applied: success for " Patchwork
2024-10-16 14:31 ` ✓ CI.checkpatch: " Patchwork
2024-10-16 14:33 ` ✓ CI.KUnit: " Patchwork
2024-10-16 14:44 ` [PATCH] " Matthew Auld
2024-10-16 14:57   ` Nirmoy Das [this message]
2024-10-16 14:44 ` ✓ CI.Build: success for " Patchwork
2024-10-16 14:46 ` ✓ CI.Hooks: " Patchwork
2024-10-16 14:48 ` ✓ CI.checksparse: " Patchwork
2024-10-16 15:05 ` ✓ CI.BAT: " Patchwork
2024-10-17  6:21 ` ✗ CI.FULL: 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=44b59c01-ec83-4bc7-9054-1bbd54d3e146@intel.com \
    --to=nirmoy.das@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@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