Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"Nerlige Ramappa, Umesh" <umesh.nerlige.ramappa@intel.com>
Subject: Re: [PATCH i-g-t] lib/xe/oa: Re-instate TestOa metric sets in LNL/BMG XML's
Date: Mon, 18 Nov 2024 17:37:09 +0000	[thread overview]
Message-ID: <b42df3f01e6053edf9ad4eda96c3eb0dbdaaafc9.camel@intel.com> (raw)
In-Reply-To: <854j44xxh5.wl-ashutosh.dixit@intel.com>

On Mon, 2024-11-18 at 09:28 -0800, Dixit, Ashutosh wrote:
> On Mon, 18 Nov 2024 09:20:00 -0800, Souza, Jose wrote:
> > 
> > > diff --git a/lib/xe/oa-configs/codegen.py b/lib/xe/oa-configs/codegen.py
> > > index 51498f803d..7251f5c7a6 100644
> > > --- a/lib/xe/oa-configs/codegen.py
> > > +++ b/lib/xe/oa-configs/codegen.py
> > > @@ -352,6 +352,9 @@ class Gen:
> > >          m = re.search(r'\$GtSlice([0-9]+)XeCore([0-9]+)$', name)
> > >          if m:
> > >              return 'intel_xe_perf_devinfo_subslice_available(&perf->devinfo, {0}, {1})'.format(m.group(1), m.group(2))
> > > +        m = re.search(r'\$GtXeCore([0-99]+)$', name)
> > > +        if m:
> > > +            return 'intel_xe_perf_devinfo_subslice_available(&perf->devinfo, {0}, 0)'.format(m.group(1))
> > 
> > Just note sure about this one, it have 8 GtXeCore so should be the
> > subslice/DSS not the slices.  But you would also need need to ajust the
> > first parameter to take into consideration subslices in the second and
> > other slices or add a function that does this for you.
> 
> Yup, I just put it in "something" there to make this compile for now. I
> want to add a FIXME here to fix later.
> 
> It can be fixed later if anyone is going to use it. We don't know how to
> use this information yet, at least in IGT, so I am assuming this can be
> fixed if needed, if it's going to be used, at the time we try to actually
> make use of the TestOa metric in IGT.
> 
> Is there any use for this in Mesa?

Not used by Mesa, so you can add my RB with a TODO comment here.

Reviewed-by: José Roberto de Souza <jose.souza@intel.com>

> 
> Thanks.
> --
> Ashutosh


  reply	other threads:[~2024-11-18 17:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15  2:20 [PATCH i-g-t] lib/xe/oa: Re-instate TestOa metric sets in LNL/BMG XML's Ashutosh Dixit
2024-11-15  3:05 ` ✓ CI.xeBAT: success for " Patchwork
2024-11-15  7:49 ` ✓ Fi.CI.BAT: " Patchwork
2024-11-15  8:19 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-11-15 19:35 ` ✗ CI.xeFULL: " Patchwork
2024-11-18 17:20 ` [PATCH i-g-t] " Souza, Jose
2024-11-18 17:28   ` Dixit, Ashutosh
2024-11-18 17:37     ` Souza, Jose [this message]
2024-11-18 18:25       ` Dixit, Ashutosh

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=b42df3f01e6053edf9ad4eda96c3eb0dbdaaafc9.camel@intel.com \
    --to=jose.souza@intel.com \
    --cc=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