Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] lib/xe/oa: Don't skip if freq sysfs are not present
Date: Mon, 21 Oct 2024 14:03:46 -0700	[thread overview]
Message-ID: <85bjzd2mod.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <Zxa/wYnP2t3JYu7b@orsosgc001>

On Mon, 21 Oct 2024 13:55:29 -0700, Umesh Nerlige Ramappa wrote:
>

Hi Umesh,

> On Mon, Oct 21, 2024 at 11:12:03AM -0700, Ashutosh Dixit wrote:
> > Freq sysfs are not created in certain environments. In most of these cases
> > OA IGT's will work just fine, even when GT min/max freq's are not
> > known. Therefore, just print a warning if freq sysfs are not present but
> > don't cause tests to skip.
> >
> > Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > ---
> > lib/xe/xe_oa.c | 6 ++----
> > 1 file changed, 2 insertions(+), 4 deletions(-)
> >
> > diff --git a/lib/xe/xe_oa.c b/lib/xe/xe_oa.c
> > index 86264230c9..189388b76b 100644
> > --- a/lib/xe/xe_oa.c
> > +++ b/lib/xe/xe_oa.c
> > @@ -571,11 +571,9 @@ xe_perf_for_fd(int drm_fd, int gt)
> >	}
> >
> >	if (!read_sysfs(sysfs_dir_fd, path_min, &gt_min_freq) ||
> > -	    !read_sysfs(sysfs_dir_fd, path_max, &gt_max_freq)) {
> > +	    !read_sysfs(sysfs_dir_fd, path_max, &gt_max_freq))
> >		igt_warn("Unable to read freqs from sysfs\n");
>
> 1) Well.. you would still end up with an igt_warn. CI will still complain,
> I guess. Is that acceptable?

I don't know if igt_warn causes CI to create a bug or only dmesg-warn does
that? Let me change to igt_info (or igt_debug).

>
> 2) If called from an application (i.e. gpuvis), does the igt_warn show up
> in stdout?

Yes igt_warn/info etc will show in stdout or stderr.

> For IGT, I don't see oa tests using this, so it's probably okay. If the
> answer for 1 and 2 is yes, then this is

Not upstream tests.

>
> Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>

Thanks but will post another version.

--
Ashutosh


> > -		close(sysfs_dir_fd);
> > -		return NULL;
> > -	}
> > +
> >	close(sysfs_dir_fd);
> >
> >	device_id = intel_get_drm_devid(drm_fd);
> > --
> > 2.41.0
> >

  reply	other threads:[~2024-10-21 21:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 18:12 [PATCH i-g-t] lib/xe/oa: Don't skip if freq sysfs are not present Ashutosh Dixit
2024-10-21 19:50 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-10-21 19:52 ` ✓ CI.xeBAT: " Patchwork
2024-10-21 20:55 ` [PATCH i-g-t] " Umesh Nerlige Ramappa
2024-10-21 21:03   ` Dixit, Ashutosh [this message]
2024-10-22  1:25 ` ✗ CI.xeFULL: failure for " Patchwork
2024-10-22  4:59 ` ✗ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-10-21 21:42 [PATCH i-g-t] " 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=85bjzd2mod.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=umesh.nerlige.ramappa@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