Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shekhar Chauhan <shekhar.chauhan@intel.com>
To: "Vivekanandan,
	Balasubramani" <balasubramani.vivekanandan@intel.com>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: drm/xe/devcoredump: Drop a FIXME in devcoredump
Date: Tue, 12 May 2026 14:27:15 +0530	[thread overview]
Message-ID: <0a9d21ce-4af3-44a4-81be-dcf39d9f9cc5@intel.com> (raw)
In-Reply-To: <agLUJsi3ZoPFyc0j@bvivekan-mob1>


On 5/12/2026 12:47, Vivekanandan, Balasubramani wrote:
> On 12.05.2026 11:25, Shekhar Chauhan wrote:
>> The FIXME says that xe_engine_snapshot_print.. is accessing persistent
>> driver data, unlike what the FIXME says that it does. Drop the FIXME
>> since the current code is not going to access the hardware while
>> dumping.
> Is there any typo in the above commit message? Did you intent to say
>
> The xe_engine_snapshot_print.. is accessing persistent
> driver data, unlike what the FIXME says that it does.
>
> After making that correction,
>
> Reviewed-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
Okay, that can be done (although my initial intent was to keep it as 
"that" to signify what the FIXME said). But, making it as "the" instead 
of "that" also makes sense.

Since it is a minor change, do you think I should send a new revision 
for it or is this something the maintainer(s) can just take care of 
while merging?

-shekhar

>
> Regards,
> Bala
>
>
>> More details about this patch:
>> https://patchwork.freedesktop.org/patch/703884/?series=161407&rev=1
>> The starting two feedbacks make sense and the original patch is wrong
>> in adding those changes, but the last feedback is the one which
>> highlights the point.
>>
>> Signed-off-by: Shekhar Chauhan <shekhar.chauhan@intel.com>
>> ---
>>   drivers/gpu/drm/xe/xe_guc_capture.c | 6 ------
>>   1 file changed, 6 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_guc_capture.c b/drivers/gpu/drm/xe/xe_guc_capture.c
>> index bc49e40165a3..21f7caf9ea08 100644
>> --- a/drivers/gpu/drm/xe/xe_guc_capture.c
>> +++ b/drivers/gpu/drm/xe/xe_guc_capture.c
>> @@ -1841,12 +1841,6 @@ void xe_engine_snapshot_print(struct xe_hw_engine_snapshot *snapshot, struct drm
>>   		   str_yes_no(snapshot->kernel_reserved));
>>   
>>   	for (type = GUC_STATE_CAPTURE_TYPE_GLOBAL; type < GUC_STATE_CAPTURE_TYPE_MAX; type++) {
>> -		/*
>> -		 * FIXME: During devcoredump print we should avoid accessing the
>> -		 * driver pointers for gt or engine. Printing should be done only
>> -		 * using the snapshot captured. Here we are accessing the gt
>> -		 * pointer. It should be fixed.
>> -		 */
>>   		list = xe_guc_capture_get_reg_desc_list(gt, GUC_CAPTURE_LIST_INDEX_PF, type,
>>   							capture_class, false);
>>   		snapshot_print_by_list_order(snapshot, p, type, list);

-- 
Shekhar Chauhan
Linux Graphics Software Engineer
Intel Corporation


  reply	other threads:[~2026-05-12  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  5:55 [PATCH] drm/xe/devcoredump: Drop a FIXME in devcoredump Shekhar Chauhan
2026-05-12  7:17 ` Vivekanandan, Balasubramani
2026-05-12  8:57   ` Shekhar Chauhan [this message]
2026-05-12 10:23     ` Vivekanandan, Balasubramani
2026-05-12 10:07 ` ✓ CI.KUnit: success for " Patchwork
2026-05-12 11:24 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-12 20:20 ` ✓ Xe.CI.FULL: " 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=0a9d21ce-4af3-44a4-81be-dcf39d9f9cc5@intel.com \
    --to=shekhar.chauhan@intel.com \
    --cc=balasubramani.vivekanandan@intel.com \
    --cc=intel-xe@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