intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: <intel-xe@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>,
	"Raag Jadav" <raag.jadav@intel.com>,
	Andi Shyti <andi.shyti@linux.intel.com>
Subject: Re: [PATCH] drm/xe: Skip creation of pcode sysfs files when pcode is disabled
Date: Fri, 22 Aug 2025 12:30:02 -0400	[thread overview]
Message-ID: <aKibCnAxTuYcKtWx@intel.com> (raw)
In-Reply-To: <20250819175529.3722716-1-andi.shyti@kernel.org>

On Tue, Aug 19, 2025 at 04:55:29PM -0100, Andi Shyti wrote:
> From: Andi Shyti <andi.shyti@linux.intel.com>
> 
> Coverity warns that 'cap' may be used uninitialised. If pcode
> is disabled there is no need to go through the hassle of a
> pcode read or taking a PM reference.

Please mark it as false positive!
We will only get here for BMG which has pcode for sure.

> 
> Check skip_pcode early in the function and return if it is set.
> 
> No change for platforms where pcode is enabled.
> 
> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
> ---
>  drivers/gpu/drm/xe/xe_device_sysfs.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_device_sysfs.c b/drivers/gpu/drm/xe/xe_device_sysfs.c
> index bd9015761aa0..3a083c215891 100644
> --- a/drivers/gpu/drm/xe/xe_device_sysfs.c
> +++ b/drivers/gpu/drm/xe/xe_device_sysfs.c
> @@ -156,6 +156,9 @@ static int late_bind_create_files(struct device *dev)
>  	u32 cap;
>  	int ret;
>  
> +	if (xe->info.skip_pcode)
> +		return 0;
> +
>  	xe_pm_runtime_get(xe);
>  
>  	ret = xe_pcode_read(root, PCODE_MBOX(PCODE_LATE_BINDING, GET_CAPABILITY_STATUS, 0),
> -- 
> 2.50.0
> 

  parent reply	other threads:[~2025-08-22 16:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19 17:55 [PATCH] drm/xe: Skip creation of pcode sysfs files when pcode is disabled Andi Shyti
2025-08-20  2:52 ` ✓ CI.KUnit: success for " Patchwork
2025-08-20  4:06 ` ✓ Xe.CI.BAT: " Patchwork
2025-08-20 23:48 ` ✗ Xe.CI.Full: failure " Patchwork
2025-08-22 16:30 ` Rodrigo Vivi [this message]
2025-08-25 14:31   ` [PATCH] " Andi Shyti
2025-08-25 14:48     ` Raag Jadav
2025-08-25 15:26       ` Rodrigo Vivi
2025-08-25 16:11         ` Michal Wajdeczko

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=aKibCnAxTuYcKtWx@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=andi.shyti@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=raag.jadav@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;
as well as URLs for NNTP newsgroup(s).