From: "Souza, Jose" <jose.souza@intel.com>
To: "Roper, Matthew D" <matthew.d.roper@intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Yang, Fei" <fei.yang@intel.com>,
"Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Subject: Re: [PATCH] drm/xe/uapi: Expose EU width via topology query
Date: Wed, 10 Jul 2024 16:17:10 +0000 [thread overview]
Message-ID: <f86f49ad7dac5b1c2d1ef3ffcb10082a1ffe135e.camel@intel.com> (raw)
In-Reply-To: <llboo4x7ihtit737wa23qmws4n7q5szvuvhxlakkvr4hhxshuc@gpbsxzfgrosw>
On Wed, 2024-07-10 at 09:59 -0500, Lucas De Marchi wrote:
> On Wed, Jul 10, 2024 at 07:52:38AM GMT, Matt Roper wrote:
> > On Tue, Jul 09, 2024 at 10:53:54PM -0700, Lucas De Marchi wrote:
> > > PVC, Xe2 and later platforms have a 16 wide EU. We were implicitly
> > > reporting for PVC the number of 16-wide EUs without giving userspace any
> > > hint that they were different than for other platforms. Xe2 and later
> > > also have 16-wide, but in those case the reported number would
> > > correspond to the 8-wide count.
> > >
> > > Add a new item to the topology that aims to clarify what the EU_PER_DSS
> > > mask means. This new item uses mask[] as a single u8 value. Xe2 and
> > > later platforms start returning the number of SIMD16 EUs.
> >
> > So it looks like your patch is adding a new standalone "EU type" item to
> > the list of masks returned by the query. I.e.,
> >
> > - DRM_XE_TOPO_DSS_GEOMETRY = ...
> > - DRM_XE_TOPO_DSS_COMPUTE = ...
> > - DRM_XE_TOPO_DSS_EU_PER_DSS = ...
> > - DRM_XE_TOPO_EU_WIDTH = {0, 1}
> >
> > I think it would be more natural if we just didn't include
> > DRM_XE_TOPO_DSS_EU_PER_DSS in the list of masks returned on new
> > platforms, but instead added a new type of mask that would be returned
> > on the newer platforms. I.e.,
> >
> > Old Xe1 platforms receive from query:
> > - DRM_XE_TOPO_DSS_GEOMETRY = ...
> > - DRM_XE_TOPO_DSS_COMPUTE = ...
> > - DRM_XE_TOPO_DSS_EU_PER_DSS = ...
> >
> > New Xe2 platforms receive from query:
> > - DRM_XE_TOPO_DSS_GEOMETRY = ...
> > - DRM_XE_TOPO_DSS_COMPUTE = ...
> > - DRM_XE_TOPO_DSS_SIMD16_EU_PER_DSS = ...
>
> yeah, I like this and wouldn't be an abuse of the field "mask[]" like
> I'm doing here.
Ack on this approach
>
> Should we document that the query may not have all the items?
>
> thanks
> Lucas De Marchi
prev parent reply other threads:[~2024-07-10 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 5:53 [PATCH] drm/xe/uapi: Expose EU width via topology query Lucas De Marchi
2024-07-10 6:19 ` ✓ CI.Patch_applied: success for " Patchwork
2024-07-10 6:20 ` ✓ CI.checkpatch: " Patchwork
2024-07-10 6:21 ` ✓ CI.KUnit: " Patchwork
2024-07-10 6:33 ` ✓ CI.Build: " Patchwork
2024-07-10 6:35 ` ✓ CI.Hooks: " Patchwork
2024-07-10 6:36 ` ✓ CI.checksparse: " Patchwork
2024-07-10 7:02 ` ✓ CI.BAT: " Patchwork
2024-07-10 8:49 ` ✓ CI.FULL: " Patchwork
2024-07-10 14:05 ` [PATCH] " Souza, Jose
2024-07-10 14:36 ` Lucas De Marchi
2024-07-10 15:38 ` Souza, Jose
2024-07-10 14:52 ` Matt Roper
2024-07-10 14:59 ` Lucas De Marchi
2024-07-10 16:17 ` Souza, Jose [this message]
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=f86f49ad7dac5b1c2d1ef3ffcb10082a1ffe135e.camel@intel.com \
--to=jose.souza@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=fei.yang@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=rodrigo.vivi@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.