Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-xe@lists.freedesktop.org, apoorva.singh@intel.com,
	Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH] drm/xe: Remove NULL check of lrc->bo in xe_lrc_snapshot_capture()
Date: Mon, 26 Aug 2024 11:24:00 +0200	[thread overview]
Message-ID: <2ea4efde-1a8b-4a2e-9d35-9bec9d98f89d@linux.intel.com> (raw)
In-Reply-To: <Zsd0KqGme2kci1tk@intel.com>


On 8/22/2024 7:23 PM, Rodrigo Vivi wrote:
> On Tue, Aug 20, 2024 at 11:43:12AM +0200, Nirmoy Das wrote:
>> Hi Rodrigo,
>>
>> On 8/16/2024 4:00 PM, Rodrigo Vivi wrote:
>>> On Fri, Aug 16, 2024 at 01:33:55PM +0530, apoorva.singh@intel.com wrote:
>>>> From: Apoorva Singh <apoorva.singh@intel.com>
>>>>
>>>> - lrc->bo NULL check is not needed in xe_lrc_snapshot_capture() as
>>>>     its already been taken care of in xe_lrc_init().
>>> I'm afraid this is not a good reason.
>>> This snapshot capture is coming from other places and apparently
>>> with risks of paths where bo was already freed?!
>>
>> After taking another look, I just realized the lrc bo is always pinned and
>> as far as I see, only place we unpin and free it,  is when we destroy the
>> lrc.
>>
>> Am I missing any condition when xe_lrc_snapshot_capture() can be called with
>> lrc->bo freed ?
> if you are confident we don't need it, let's kill...
>
> Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>


Merged this to drm-xe-next.


Thanks,

Nirmoy

>
>>
>> Regards,
>>
>> Nirmoy
>>
>>
>>> why is this check bothering you so much?
>>>
>>>> Signed-off-by: Apoorva Singh <apoorva.singh@intel.com>
>>>> ---
>>>>    drivers/gpu/drm/xe/xe_lrc.c | 2 +-
>>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/xe/xe_lrc.c b/drivers/gpu/drm/xe/xe_lrc.c
>>>> index 974a9cd8c379..aec7db39c061 100644
>>>> --- a/drivers/gpu/drm/xe/xe_lrc.c
>>>> +++ b/drivers/gpu/drm/xe/xe_lrc.c
>>>> @@ -1649,7 +1649,7 @@ struct xe_lrc_snapshot *xe_lrc_snapshot_capture(struct xe_lrc *lrc)
>>>>    	if (!snapshot)
>>>>    		return NULL;
>>>> -	if (lrc->bo && lrc->bo->vm)
>>>> +	if (lrc->bo->vm)
>>>>    		xe_vm_get(lrc->bo->vm);
>>>>    	snapshot->context_desc = xe_lrc_ggtt_addr(lrc);
>>>> -- 
>>>> 2.34.1
>>>>

  reply	other threads:[~2024-08-26  9:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16  8:03 [PATCH] drm/xe: Remove NULL check of lrc->bo in xe_lrc_snapshot_capture() apoorva.singh
2024-08-16  8:07 ` Singh, Apoorva
2024-08-16  8:10 ` ✓ CI.Patch_applied: success for drm/xe: Remove NULL check of lrc->bo in xe_lrc_snapshot_capture() (rev2) Patchwork
2024-08-16  8:10 ` ✓ CI.checkpatch: " Patchwork
2024-08-16  8:11 ` ✓ CI.KUnit: " Patchwork
2024-08-16  8:27 ` ✓ CI.Build: " Patchwork
2024-08-16  8:31 ` ✓ CI.Hooks: " Patchwork
2024-08-16  8:32 ` [PATCH] drm/xe: Remove NULL check of lrc->bo in xe_lrc_snapshot_capture() Nirmoy Das
2024-08-16  8:33 ` ✓ CI.checksparse: success for drm/xe: Remove NULL check of lrc->bo in xe_lrc_snapshot_capture() (rev2) Patchwork
2024-08-16  9:11 ` ✗ CI.BAT: failure " Patchwork
2024-08-16 14:00 ` [PATCH] drm/xe: Remove NULL check of lrc->bo in xe_lrc_snapshot_capture() Rodrigo Vivi
2024-08-16 14:12   ` Nirmoy Das
2024-08-20  9:43   ` Nirmoy Das
2024-08-22 17:23     ` Rodrigo Vivi
2024-08-26  9:24       ` Nirmoy Das [this message]
2024-08-16 15:50 ` ✗ CI.FULL: failure for drm/xe: Remove NULL check of lrc->bo in xe_lrc_snapshot_capture() (rev2) Patchwork
2024-08-16 17:07 ` [PATCH] drm/xe: Remove NULL check of lrc->bo in xe_lrc_snapshot_capture() Matthew Brost
  -- strict thread matches above, loose matches on Subject: below --
2024-08-16  8:37 apoorva.singh
2024-08-16  6:24 apoorva.singh
2024-08-16  6:26 ` Singh, Apoorva

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=2ea4efde-1a8b-4a2e-9d35-9bec9d98f89d@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=apoorva.singh@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=rodrigo.vivi@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