From: Andi Shyti <andi.shyti@linux.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 11/12] drm/i915: Use to_gt() helper for GGTT accesses
Date: Mon, 13 Dec 2021 20:16:25 +0200 [thread overview]
Message-ID: <YbeN+WRnQhfLDOSf@intel.intel> (raw)
In-Reply-To: <20211213181053.GJ2219399@mdroper-desk1.amr.corp.intel.com>
Hi Matt,
> > diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> > index 95174938b160..2619bb17b6eb 100644
> > --- a/drivers/gpu/drm/i915/i915_driver.c
> > +++ b/drivers/gpu/drm/i915/i915_driver.c
> > @@ -571,6 +571,8 @@ static int i915_driver_hw_probe(struct drm_i915_private *dev_priv)
> >
> > i915_perf_init(dev_priv);
> >
> > + intel_gt_init_hw_early(to_gt(dev_priv), to_gt(dev_priv)->ggtt);
>
> intel_gt_init_hw_early is defined as
>
> void intel_gt_init_hw_early(struct intel_gt *gt, struct i915_ggtt *ggtt)
> {
> gt->ggtt = ggtt;
> }
>
> so this call is now essentially doing
>
> to_gt(dev_priv)->ggtt = to_gt(dev_priv)->ggtt
>
> which isn't what you intended. It might be better to just drop the
> function completely and instead assign the gt's ggtt pointer here to a
> drmm_kzalloc() dynamic allocation.
ehehe... yes, I actually had this fixed (in mock device it's
indeed correct), but I might have brought it back by mistake.
Thanks for noticing it.
The next patch removes it.
Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: "Michał Winiarski" <michal.winiarski@intel.com>,
"Andi Shyti" <andi@etezian.org>,
"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>,
"Andi Shyti" <andi.shyti@linux.intel.com>
Subject: Re: [PATCH RESEND v7 11/12] drm/i915: Use to_gt() helper for GGTT accesses
Date: Mon, 13 Dec 2021 20:16:25 +0200 [thread overview]
Message-ID: <YbeN+WRnQhfLDOSf@intel.intel> (raw)
In-Reply-To: <20211213181053.GJ2219399@mdroper-desk1.amr.corp.intel.com>
Hi Matt,
> > diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> > index 95174938b160..2619bb17b6eb 100644
> > --- a/drivers/gpu/drm/i915/i915_driver.c
> > +++ b/drivers/gpu/drm/i915/i915_driver.c
> > @@ -571,6 +571,8 @@ static int i915_driver_hw_probe(struct drm_i915_private *dev_priv)
> >
> > i915_perf_init(dev_priv);
> >
> > + intel_gt_init_hw_early(to_gt(dev_priv), to_gt(dev_priv)->ggtt);
>
> intel_gt_init_hw_early is defined as
>
> void intel_gt_init_hw_early(struct intel_gt *gt, struct i915_ggtt *ggtt)
> {
> gt->ggtt = ggtt;
> }
>
> so this call is now essentially doing
>
> to_gt(dev_priv)->ggtt = to_gt(dev_priv)->ggtt
>
> which isn't what you intended. It might be better to just drop the
> function completely and instead assign the gt's ggtt pointer here to a
> drmm_kzalloc() dynamic allocation.
ehehe... yes, I actually had this fixed (in mock device it's
indeed correct), but I might have brought it back by mistake.
Thanks for noticing it.
The next patch removes it.
Andi
next prev parent reply other threads:[~2021-12-13 18:16 UTC|newest]
Thread overview: 42+ 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 ` 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 ` 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 ` 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 ` Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 04/12] drm/i915/gt: " Andi Shyti
2021-12-12 15:21 ` Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 05/12] drm/i915/gem: " Andi Shyti
2021-12-12 15:21 ` Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 06/12] drm/i915/gvt: " Andi Shyti
2021-12-12 15:21 ` Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 07/12] drm/i915/selftests: " Andi Shyti
2021-12-12 15:21 ` Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 08/12] drm/i915/pxp: " Andi Shyti
2021-12-12 15:21 ` Andi Shyti
2021-12-12 15:21 ` [Intel-gfx] [PATCH RESEND v7 09/12] drm/i915: " Andi Shyti
2021-12-12 15:21 ` 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 ` 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-12 15:21 ` Andi Shyti
2021-12-13 18:10 ` [Intel-gfx] " Matt Roper
2021-12-13 18:10 ` Matt Roper
2021-12-13 18:16 ` Andi Shyti [this message]
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-12 15:21 ` Andi Shyti
2021-12-13 16:12 ` [Intel-gfx] " kernel test robot
2021-12-13 16:12 ` kernel test robot
2021-12-13 16:12 ` kernel test robot
2021-12-13 16:12 ` kernel test robot
2021-12-13 18:16 ` [Intel-gfx] " Matt Roper
2021-12-13 18:16 ` Matt Roper
2021-12-13 18:20 ` [Intel-gfx] " Andi Shyti
2021-12-13 18:20 ` Andi Shyti
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=YbeN+WRnQhfLDOSf@intel.intel \
--to=andi.shyti@linux.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 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.