From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Riana Tauro <riana.tauro@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
<badal.nilawar@intel.com>
Subject: Re: [PATCH v2 2/2] drm/xe/xe_survivability: Fix static analysis tool reported issues
Date: Thu, 18 Dec 2025 17:46:16 -0500 [thread overview]
Message-ID: <aUSEOF9ka7KjunaK@intel.com> (raw)
In-Reply-To: <20251218105151.586575-6-riana.tauro@intel.com>
On Thu, Dec 18, 2025 at 04:21:54PM +0530, Riana Tauro wrote:
> 1) Use static survivability info attributes.
> 2) Fix visibility condition
>
> Fixes: f4e9fc967afd ("drm/xe/xe_survivability: Redesign survivability mode")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202512101919.G12cuhBJ-lkp@intel.com/
I don't see the number 2 above listed here in this report.
What am I missing?
Also, I believe it deserves a separate commit with proper explanation even
if it ends up with same closes and reported by tag.
Sorry for not noticing this on the previous revision.
> Signed-off-by: Riana Tauro <riana.tauro@intel.com>
> ---
> drivers/gpu/drm/xe/xe_survivability_mode.c | 23 +++++++++++-----------
> 1 file changed, 12 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_survivability_mode.c b/drivers/gpu/drm/xe/xe_survivability_mode.c
> index 2869866537ad..a25a23bcacc8 100644
> --- a/drivers/gpu/drm/xe/xe_survivability_mode.c
> +++ b/drivers/gpu/drm/xe/xe_survivability_mode.c
> @@ -221,15 +221,15 @@ static ssize_t survivability_info_show(struct device *dev,
> .index = _index, \
> }
>
> -SURVIVABILITY_ATTR_RO(capability_info, CAPABILITY_INFO);
> -SURVIVABILITY_ATTR_RO(postcode_trace, POSTCODE_TRACE);
> -SURVIVABILITY_ATTR_RO(postcode_trace_overflow, POSTCODE_TRACE_OVERFLOW);
> -SURVIVABILITY_ATTR_RO(aux_info0, AUX_INFO0);
> -SURVIVABILITY_ATTR_RO(aux_info1, AUX_INFO1);
> -SURVIVABILITY_ATTR_RO(aux_info2, AUX_INFO2);
> -SURVIVABILITY_ATTR_RO(aux_info3, AUX_INFO3);
> -SURVIVABILITY_ATTR_RO(aux_info4, AUX_INFO4);
> -SURVIVABILITY_ATTR_RO(fdo_mode, FDO_INFO);
> +static SURVIVABILITY_ATTR_RO(capability_info, CAPABILITY_INFO);
> +static SURVIVABILITY_ATTR_RO(postcode_trace, POSTCODE_TRACE);
> +static SURVIVABILITY_ATTR_RO(postcode_trace_overflow, POSTCODE_TRACE_OVERFLOW);
> +static SURVIVABILITY_ATTR_RO(aux_info0, AUX_INFO0);
> +static SURVIVABILITY_ATTR_RO(aux_info1, AUX_INFO1);
> +static SURVIVABILITY_ATTR_RO(aux_info2, AUX_INFO2);
> +static SURVIVABILITY_ATTR_RO(aux_info3, AUX_INFO3);
> +static SURVIVABILITY_ATTR_RO(aux_info4, AUX_INFO4);
> +static SURVIVABILITY_ATTR_RO(fdo_mode, FDO_INFO);
>
> static void xe_survivability_mode_fini(void *arg)
> {
> @@ -252,9 +252,10 @@ static umode_t survivability_info_attrs_visible(struct kobject *kobj, struct att
> u32 *info = survivability->info;
>
> /* FDO mode is visible only when supported */
> - if (idx >= MAX_SCRATCH_REG && survivability->version >= 2)
> + if (idx == MAX_SCRATCH_REG && survivability->version >= 2)
> return 0400;
> - else if (info[idx])
> +
> + if (idx < MAX_SCRATCH_REG && info[idx])
> return 0400;
>
> return 0;
> --
> 2.47.1
>
next prev parent reply other threads:[~2025-12-18 22:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 10:51 [PATCH v2 0/2] Survivability Mode Fixes Riana Tauro
2025-12-18 10:30 ` ✓ CI.KUnit: success for Survivability mode fixes (rev2) Patchwork
2025-12-18 10:51 ` [PATCH v2 1/2] drm/xe/xe_survivability: Remove unused index Riana Tauro
2025-12-18 22:46 ` Rodrigo Vivi
2025-12-18 10:51 ` [PATCH v2 2/2] drm/xe/xe_survivability: Fix static analysis tool reported issues Riana Tauro
2025-12-18 22:46 ` Rodrigo Vivi [this message]
2025-12-19 7:39 ` Riana Tauro
2025-12-18 11:04 ` ✓ Xe.CI.BAT: success for Survivability mode fixes (rev2) Patchwork
2025-12-19 6:11 ` ✗ Xe.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=aUSEOF9ka7KjunaK@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.