From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Shekhar Chauhan <shekhar.chauhan@intel.com>,
igt-dev@lists.freedesktop.org, ashutosh.dixit@intel.com
Subject: Re: [PATCH v2] lib/intel_wa: Assert on error instead of returning -1
Date: Sat, 16 May 2026 12:11:13 -0700 [thread overview]
Message-ID: <87ecjbgofi.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20260515122408.zd564l5tnhaprha3@kamilkon-DESK.igk.intel.com>
On Fri, 15 May 2026 05:24:08 -0700, Kamil Konieczny wrote:
>
Hi Kamil,
> Hi Shekhar,
> On 2026-05-14 at 12:06:55 +0530, Shekhar Chauhan wrote:
> > igt_has_intel_wa() returns 0, 1, or -1, but there is no point
> > distinguishing the error and no-workaround cases for callers. Replace
> > the error return with igt_assert() and simplify debugfs_file_has_wa() by
> > dropping the igt_debugfs_exists() check, since igt_sysfs_get() returns
> > NULL for missing files anyway.
> >
> > v2: Make the func as bool instead of int.
> >
> > Signed-off-by: Shekhar Chauhan <shekhar.chauhan@intel.com>
> > ---
> > lib/intel_wa.c | 19 +++++++++----------
> > lib/intel_wa.h | 2 +-
> > 2 files changed, 10 insertions(+), 11 deletions(-)
> >
> > diff --git a/lib/intel_wa.c b/lib/intel_wa.c
> > index 727dd6c98..e4fe7b0ee 100644
> > --- a/lib/intel_wa.c
> > +++ b/lib/intel_wa.c
> > @@ -7,18 +7,18 @@
> > #include <stdint.h>
> > #include <stdio.h>
> >
> > +#include "igt_core.h"
> > #include "igt_debugfs.h"
> > #include "igt_sysfs.h"
> > #include "intel_wa.h"
> > #include "xe/xe_query.h"
> >
> > -static int debugfs_file_has_wa(int drm_fd, int debugfs_fd,
> > +static bool debugfs_file_has_wa(int drm_fd, int debugfs_fd,
> > const char *debugfs_name, const char *wa)
> > {
> > char *debugfs_dump;
> >
> > - if (!igt_debugfs_exists(drm_fd, debugfs_name, O_RDONLY))
> > - return -1;
> > + igt_assert(igt_debugfs_exists(drm_fd, debugfs_name, O_RDONLY));
> >
> > debugfs_dump = igt_sysfs_get(debugfs_fd, debugfs_name);
> > if (debugfs_dump) {
> > @@ -27,10 +27,10 @@ static int debugfs_file_has_wa(int drm_fd, int debugfs_fd,
> > free(debugfs_dump);
> >
> > if (has_wa)
> > - return 1;
> > + return true;
> > }
> >
> > - return 0;
> > + return false;
> > }
> >
> > /**
> > @@ -38,18 +38,17 @@ static int debugfs_file_has_wa(int drm_fd, int debugfs_fd,
> > * @drm_fd: A drm file descriptor
> > * @check_wa: Workaround to be checked
> > *
> > - * Returns: 0 if no WA, 1 if WA present, -1 on error
> > + * Returns: true if WA present, false otherwise
> > */
> > -int igt_has_intel_wa(int drm_fd, const char *check_wa)
> > +bool igt_has_intel_wa(int drm_fd, const char *check_wa)
> > {
> > - int ret = 0;
> > + bool ret = 0;
> > int debugfs_fd;
> > unsigned int xe;
> > char name[256];
> >
> > debugfs_fd = igt_debugfs_dir(drm_fd);
> > - if (debugfs_fd == -1)
> > - return -1;
> > + igt_assert(debugfs_fd >= 0);
>
> This will mean that all other users needs to be updated.
To date there are no other users of this function, except one in OA.
> The way of adding any igt_assert/igt_require into lib/
> make it impossible to reuse them in tools/ and require
> to write same functionality twice, one in lib/ and one
> for any tools which will want to use them. Or to write
> __function() without igt_assert/igt_require.
Well it was I who suggested doing this. Can you explain your point a bit?
Any tools which use a lib function which uses e.g. igt_assert/igt_require
can also link with lib_igt (which provides igt_assert/igt_require). See
e.g. tools/xe-perf/meson.build. It is not unreasonable for IGT tools to
link with lib_igt. I thought not linking with igt_lib was an unreasonabe
requirement and I removed it for tools/xe-perf.
If you are saying tools should be able to run without debugfs mounted,
maybe you have a point. In that case we can drop this patch. But even here
maybe IGT tools should run only with debugfs mounted?
Thanks.
--
Ashutosh
> > xe_for_each_gt(drm_fd, xe) {
> > sprintf(name, "gt%d/workarounds", xe);
> > diff --git a/lib/intel_wa.h b/lib/intel_wa.h
> > index 765a5948e..34cafecc4 100644
> > --- a/lib/intel_wa.h
> > +++ b/lib/intel_wa.h
> > @@ -6,6 +6,6 @@
> > #ifndef __INTEL_WA_H__
> > #define __INTEL_WA_H__
> >
> > -int igt_has_intel_wa(int drm_fd, const char *check_wa);
> > +bool igt_has_intel_wa(int drm_fd, const char *check_wa);
> >
> > #endif /* __INTEL_WA_H__ */
> > --
> > 2.53.0
> >
next prev parent reply other threads:[~2026-05-16 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 6:36 [PATCH v2] lib/intel_wa: Assert on error instead of returning -1 Shekhar Chauhan
2026-05-14 6:48 ` Dixit, Ashutosh
2026-05-14 7:23 ` ✗ i915.CI.BAT: failure for " Patchwork
2026-05-14 7:37 ` ✓ Xe.CI.BAT: success " Patchwork
2026-05-15 4:11 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-15 12:24 ` [PATCH v2] " Kamil Konieczny
2026-05-16 19:11 ` Dixit, Ashutosh [this message]
2026-05-18 23:53 ` Dixit, Ashutosh
2026-05-19 9:52 ` Kamil Konieczny
2026-05-20 22:18 ` Dixit, Ashutosh
2026-05-19 9:54 ` Kamil Konieczny
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=87ecjbgofi.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=shekhar.chauhan@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.