public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: "Michał Winiarski" <michal.winiarski@intel.com>,
	"Intel GFX" <intel-gfx@lists.freedesktop.org>,
	"Lucas De Marchi" <lucas.demarchi@intel.com>,
	"DRI Devel" <dri-devel@lists.freedesktop.org>,
	"Chris Wilson" <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH RESEND v7 12/12] drm/i915: Move the GGTT from i915 private data to the GT
Date: Mon, 13 Dec 2021 20:20:06 +0200	[thread overview]
Message-ID: <YbeO1saXid4TEJHy@intel.intel> (raw)
In-Reply-To: <20211213181647.GK2219399@mdroper-desk1.amr.corp.intel.com>

Hi Matt,

On Mon, Dec 13, 2021 at 10:16:47AM -0800, Matt Roper wrote:
> On Sun, Dec 12, 2021 at 05:21:17PM +0200, Andi Shyti wrote:
> > GGTT was available both through i915->ggtt and gt->ggtt, and we
> > eventually want to get rid of the i915->ggtt one.
> > Move the GGTT from i915 to gt and use to_gt() for accesssing the
> > ggtt.
> > 
> > Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
> > Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> > Cc: Matt Roper <matthew.d.roper@intel.com>
> > ---
> ...
> > diff --git a/drivers/gpu/drm/i915/gt/intel_gt_types.h b/drivers/gpu/drm/i915/gt/intel_gt_types.h
> > index 14216cc471b1..02fc7641b82e 100644
> > --- a/drivers/gpu/drm/i915/gt/intel_gt_types.h
> > +++ b/drivers/gpu/drm/i915/gt/intel_gt_types.h
> > @@ -69,7 +69,7 @@ enum intel_submission_method {
> >  struct intel_gt {
> >  	struct drm_i915_private *i915;
> >  	struct intel_uncore *uncore;
> > -	struct i915_ggtt *ggtt;
> > +	struct i915_ggtt ggtt;
> >  
> >  	struct intel_uc uc;
> >  
> 
> I'm not sure this is the direction we want to go.  Although it works for
> the initial multi-tile support, there's some other stuff coming up soon
> that will require two intel_gt's to share the same ggtt rather than
> each having an independent one.

Sure... I sent this just to have an opinion, I'm dropping it.

Thanks,
Andi

  reply	other threads:[~2021-12-13 18:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12 15:21 [Intel-gfx] [PATCH RESEND v7 00/12] More preparation for multi gt patches Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 01/12] drm/i915: Store backpointer to GT in uncore Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 02/12] drm/i915: Introduce to_gt() helper Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 03/12] drm/i915/display: Use " Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 04/12] drm/i915/gt: " Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 05/12] drm/i915/gem: " Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 06/12] drm/i915/gvt: " Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 07/12] drm/i915/selftests: " Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 08/12] drm/i915/pxp: " Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 09/12] drm/i915: " Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 10/12] drm/i915: Rename i915->gt to i915->gt0 Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 11/12] drm/i915: Use to_gt() helper for GGTT accesses Andi Shyti
2021-12-13 18:10   ` Matt Roper
2021-12-13 18:16     ` Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 12/12] drm/i915: Move the GGTT from i915 private data to the GT Andi Shyti
2021-12-13 16:12   ` kernel test robot
2021-12-13 18:16   ` Matt Roper
2021-12-13 18:20     ` Andi Shyti [this message]
2021-12-12 15:33 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for More preparation for multi gt patches Patchwork
2021-12-12 15:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-12 16:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-12 17:23 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork

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=YbeO1saXid4TEJHy@intel.intel \
    --to=andi.shyti@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=michal.winiarski@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