Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 2/4] lib/igt_sysfs: Don't assert in igt_sysfs_dir_id_to_name
Date: Mon, 05 Jun 2023 18:27:17 -0700	[thread overview]
Message-ID: <87ilc1mlca.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230606012150.2119065-3-ashutosh.dixit@intel.com>

On Mon, 05 Jun 2023 18:21:48 -0700, Ashutosh Dixit wrote:
>
> Old platforms (BLB/ELK) don't have any freq attributes even in legacy
> per-device sysfs. Asserting for this platforms shows up as a CI
> regression.

This can be seen in CI results here:

https://patchwork.freedesktop.org/series/118809/#rev6
https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_769/fi-blb-e6850/igt@gem_ctx_freq@sysfs.html
https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_769/fi-elk-e7500/igt@gem_ctx_freq@sysfs.html

> So don't assert, just return the device level attribute and let file open
> on the non-existent attribute fail to preserve previous behavior.
>
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
>  lib/igt_sysfs.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/lib/igt_sysfs.c b/lib/igt_sysfs.c
> index 8021ba9cbb2e..35a4faa9aab5 100644
> --- a/lib/igt_sysfs.c
> +++ b/lib/igt_sysfs.c
> @@ -115,10 +115,8 @@ const char *igt_sysfs_dir_id_to_name(int dir, enum i915_attr_id id)
>
>	if (igt_sysfs_has_attr(dir, i915_attr_name[RPS][id]))
>		return i915_attr_name[RPS][id];
> -	if (igt_sysfs_has_attr(dir, i915_attr_name[GT][id]))
> -		return i915_attr_name[GT][id];
>
> -	igt_assert_f(0, "attr_id not found %d\n", id);
> +	return i915_attr_name[GT][id];
>  }
>
>  /**
> --
> 2.38.0
>

  reply	other threads:[~2023-06-06  1:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06  1:21 [igt-dev] [PATCH i-g-t 0/4] gem_ctx_freq: multi-gt support and disable efficient freq Ashutosh Dixit
2023-06-06  1:21 ` [igt-dev] [PATCH i-g-t 1/4] tests/gem_ctx_freq: Add support for multi-gts Ashutosh Dixit
2023-06-07 23:47   ` Dixit, Ashutosh
2023-06-06  1:21 ` [igt-dev] [PATCH i-g-t 2/4] lib/igt_sysfs: Don't assert in igt_sysfs_dir_id_to_name Ashutosh Dixit
2023-06-06  1:27   ` Dixit, Ashutosh [this message]
2023-06-07 20:53   ` Umesh Nerlige Ramappa
2023-06-06  1:21 ` [igt-dev] [PATCH i-g-t 3/4] tests/gem_ctx_freq: Disable SLPC efficient freq for the test Ashutosh Dixit
2023-06-07 21:35   ` Umesh Nerlige Ramappa
2023-06-08  2:28     ` Dixit, Ashutosh
2023-06-08  6:01   ` Belgaumkar, Vinay
2023-06-08 15:50     ` Dixit, Ashutosh
2023-06-06  1:21 ` [igt-dev] [PATCH i-g-t 4/4] HAX: Add gem_ctx_freq to BAT testlist Ashutosh Dixit
2023-06-06  2:27 ` [igt-dev] ✓ Fi.CI.BAT: success for gem_ctx_freq: multi-gt support and disable efficient freq Patchwork
2023-06-06 23:36 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-06-08 15:47 [igt-dev] [PATCH v2 i-g-t 0/4] " Ashutosh Dixit
2023-06-08 15:47 ` [igt-dev] [PATCH i-g-t 2/4] lib/igt_sysfs: Don't assert in igt_sysfs_dir_id_to_name Ashutosh Dixit

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=87ilc1mlca.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@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