All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/6] drm/i915: move gt_cleanup_early out of gem_cleanup_early
Date: Tue, 30 Jul 2019 16:12:07 +0100	[thread overview]
Message-ID: <156449952721.6373.11192721571431718539@skylake-alporthouse-com> (raw)
In-Reply-To: <1f3a5fc1-7eda-4bbc-1f41-7f4a8631306b@intel.com>

Quoting Daniele Ceraolo Spurio (2019-07-30 15:56:57)
> 
> 
> On 7/30/19 1:01 AM, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2019-07-30 08:19:18)
> >>
> >> On 30/07/2019 00:47, Daniele Ceraolo Spurio wrote:
> >>> We don't call the init_early function from within the gem code, so we
> >>> shouldn't do it for the cleanup either.
> >>>
> >>> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> >>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> >>> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> >>> ---
> >>>    drivers/gpu/drm/i915/i915_drv.c | 2 ++
> >>>    drivers/gpu/drm/i915/i915_gem.c | 2 --
> >>>    2 files changed, 2 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> >>> index f2d3d754af37..934e605e2466 100644
> >>> --- a/drivers/gpu/drm/i915/i915_drv.c
> >>> +++ b/drivers/gpu/drm/i915/i915_drv.c
> >>> @@ -951,6 +951,7 @@ static int i915_driver_early_probe(struct drm_i915_private *dev_priv)
> >>>        intel_uc_cleanup_early(&dev_priv->gt.uc);
> >>>        i915_gem_cleanup_early(dev_priv);
> >>>    err_workqueues:
> >>> +     intel_gt_cleanup_early(&dev_priv->gt);
> >>>        i915_workqueues_cleanup(dev_priv);
> >>>        return ret;
> >>>    }
> >>> @@ -966,6 +967,7 @@ static void i915_driver_late_release(struct drm_i915_private *dev_priv)
> >>>        intel_power_domains_cleanup(dev_priv);
> >>>        intel_uc_cleanup_early(&dev_priv->gt.uc);
> >>>        i915_gem_cleanup_early(dev_priv);
> >>> +     intel_gt_cleanup_early(&dev_priv->gt);
> > 
> > Note the change in naming convention, intel_gt_driver_late_release().
> > -Chris
> > 
> 
> Does it make sense to flip only the gt function? it'd look terribly out 
> of place close to all those other cleanup_early() calls. I can follow up 
> with a patch to flip them all at the same time if that works for you.

Baby steps, the consistency is in the function callgraphs -- it looks
out of place to have late_release call cleanup_early :)
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-07-30 15:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29 23:47 [PATCH 0/6] Call uC functions from GT ones Daniele Ceraolo Spurio
2019-07-29 23:47 ` [PATCH 1/6] drm/i915/uc: move uC WOPCM setup in uc_init_hw Daniele Ceraolo Spurio
2019-07-30 14:39   ` Michal Wajdeczko
2019-07-30 21:04     ` Daniele Ceraolo Spurio
2019-07-30 20:24   ` kbuild test robot
2019-07-30 20:24   ` [RFC PATCH] drm/i915/uc: uc_wopcm_init_hw() can be static kbuild test robot
2019-07-29 23:47 ` [PATCH 2/6] drm/i915: move gt_cleanup_early out of gem_cleanup_early Daniele Ceraolo Spurio
2019-07-30  7:19   ` Tvrtko Ursulin
2019-07-30  8:01     ` Chris Wilson
2019-07-30 14:56       ` Daniele Ceraolo Spurio
2019-07-30 15:12         ` Chris Wilson [this message]
2019-07-29 23:47 ` [PATCH 3/6] drm/i915/uc: move uc early functions inside the gt ones Daniele Ceraolo Spurio
2019-07-30 14:53   ` Michal Wajdeczko
2019-07-29 23:47 ` [PATCH 4/6] drm/i915/gt: introduce intel_gt_runtime_suspend/resume Daniele Ceraolo Spurio
2019-07-30  7:35   ` Tvrtko Ursulin
2019-07-29 23:47 ` [PATCH 5/6] drm/i915/uc: move uc_resume under gt_resume Daniele Ceraolo Spurio
2019-07-30  8:09   ` Chris Wilson
2019-07-29 23:47 ` [PATCH 6/6] drm/i915/gt: introduce intel_gt_suspend Daniele Ceraolo Spurio
2019-07-30  7:33   ` Tvrtko Ursulin
2019-07-30  8:12     ` Chris Wilson
2019-07-30 14:58       ` Daniele Ceraolo Spurio
2019-07-30  0:44 ` ✗ Fi.CI.SPARSE: warning for Call uC functions from GT ones Patchwork
2019-07-30  1:03 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-30 12:20 ` ✓ 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=156449952721.6373.11192721571431718539@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.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.