Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Poosa, Karthik" <karthik.poosa@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
	<badal.nilawar@intel.com>, <riana.tauro@intel.com>,
	<jani.nikula@intel.com>
Subject: Re: [PATCH v6] drm/xe: Add a null pointer check
Date: Tue, 26 Mar 2024 20:53:15 +0530	[thread overview]
Message-ID: <9e257d4b-8335-473f-8d0c-ee2b6673aec5@intel.com> (raw)
In-Reply-To: <20240325175829.GZ718896@mdroper-desk1.amr.corp.intel.com>


On 25-03-2024 23:28, Matt Roper wrote:
> On Mon, Mar 25, 2024 at 07:42:23PM +0530, Karthik Poosa wrote:
>> Add a missing null pointer check.
> You have so many versions of this patch that I've lost track of which is
> which, but as I commented on an earlier version, this whole patch seems
> unnecessary.  All Intel devices will have at least one GT, and we can
> never "resume from runtime PM" before those GT(s) get initialized.  So a
> NULL return here is impossible.  If you want to be paranoid, you can add
> an assert to make that invariant clear and it will get compiled out of
> production releases.
>
>
> Matt
Unfortunately, I missed your comment on earlier version (v2). Will drop 
this patch.
>
>> v2: Release resources before returning error. (Riana)
>>
>> v3: Update commit message. (Badal)
>>
>> v4: Change drm_err to XE_WARN_ON. (Anshuman)
>>
>> v5: Fix XE_WARN_ON check. (Riana)
>>
>> v6: Update commit message. (Jani)
>>
>> Fixes: 09d88e3beb64 ("drm/xe/pm: Init pcode and restore vram on power lost")
>> Signed-off-by: Karthik Poosa <karthik.poosa@intel.com>
>> Reviewed-by: Riana Tauro <riana.tauro@intel.com>
>> ---
>>   drivers/gpu/drm/xe/xe_pm.c | 5 +++++
>>   1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
>> index cc650a92c2fc..f6837bd6f9a3 100644
>> --- a/drivers/gpu/drm/xe/xe_pm.c
>> +++ b/drivers/gpu/drm/xe/xe_pm.c
>> @@ -383,6 +383,11 @@ int xe_pm_runtime_resume(struct xe_device *xe)
>>   	 * really lost power. Detecting primary Gt power is sufficient.
>>   	 */
>>   	gt = xe_device_get_gt(xe, 0);
>> +	if (XE_WARN_ON(!gt)) {
>> +		err = -ENXIO;
>> +		goto out;
>> +	}
>> +
>>   	xe->d3cold.power_lost = xe_guc_in_reset(&gt->uc.guc);
>>   
>>   	if (xe->d3cold.allowed && xe->d3cold.power_lost) {
>> -- 
>> 2.25.1
>>

      reply	other threads:[~2024-03-26 15:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 14:12 [PATCH v6] drm/xe: Add a null pointer check Karthik Poosa
2024-03-25 14:45 ` Michal Wajdeczko
2024-03-25 17:58 ` Matt Roper
2024-03-26 15:23   ` Poosa, Karthik [this message]

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=9e257d4b-8335-473f-8d0c-ee2b6673aec5@intel.com \
    --to=karthik.poosa@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=riana.tauro@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