Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	"Roper, Matthew D" <matthew.d.roper@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v6 1/1] drm/i915/pxp: Promote pxp subsystem to top-level of i915
Date: Thu, 1 Dec 2022 19:20:08 +0000	[thread overview]
Message-ID: <860bdb16f2aa72423d5ffcdc81810f6918dabf96.camel@intel.com> (raw)
In-Reply-To: <1c4cd3873756ee417391d0354f2646a031cdf2b6.camel@intel.com>



On Wed, 2022-11-30 at 17:42 +0000, Vivi, Rodrigo wrote:
> On Wed, 2022-11-30 at 09:32 -0800, Matt Roper wrote:
> > On Tue, Nov 29, 2022 at 06:02:45PM -0800, Alan Previn wrote:
> > > Starting with MTL, there will be two GT-tiles, a render and media
> > > tile. PXP as a service for supporting workloads with protected
> > 
> > Drive-by comment:  we've been a bit inconsistent about terminology in
> > the past, but my understanding is that we're trying to standardize on
> > "GT" for the unit that MTL has two of, and keeping the term "tile"
> > for
> > the PVC-style unit that is a combination of (GT+lmem).
> 
> I agree that this gets really confusing... but it will be hard to
> standardize this I'm afraid. Specially when we do the PVC-style-tile a
> intel_gt struct and we apparently are doing the same on MTL, no?!
> 
> So, unless the topology gets organized in the code with a standard
> name, it is hard to demand everyone to use the same one.
> 
> Besides that whenever we were discussing the pvc's one we all had
> agreed that the term "tile" was bad, hence we focused on keep the
> intel_gt ready for that.
> 
> Whenever I hear tile I think of the display buffer organization...
> and there are other "tiles" examples iirc.
> 
> 
Yeah... GPU is so complex these days, a single subssytem is like a whole SOC back in the day ... beside display tiling
formats, media's HEVC has "tiles" that is kinda like macro-blocks and who can forget render's tiled-rendering (all 3
similar but can be completely orthogonal depending on the hw config / buffer state / usage). I'm assuming this
conversation is a nit. Please correct me otherwise.

  reply	other threads:[~2022-12-01 19:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30  2:02 [Intel-gfx] [PATCH v6 1/1] drm/i915/pxp: Promote pxp subsystem to top-level of i915 Alan Previn
2022-11-30  2:28 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for series starting with [v6,1/1] " Patchwork
2022-11-30  2:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-30 11:20 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-12-01 19:25   ` Teres Alexis, Alan Previn
2022-11-30 17:32 ` [Intel-gfx] [PATCH v6 1/1] " Matt Roper
2022-11-30 17:42   ` Vivi, Rodrigo
2022-12-01 19:20     ` Teres Alexis, Alan Previn [this message]
2022-12-01 23:55 ` Teres Alexis, Alan Previn
2022-12-02  0:11   ` Teres Alexis, Alan Previn

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=860bdb16f2aa72423d5ffcdc81810f6918dabf96.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox