From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Move the common engine cleanup to intel_engine_cs.c
Date: Wed, 03 Aug 2016 15:52:31 +0300 [thread overview]
Message-ID: <1470228751.3860.12.camel@linux.intel.com> (raw)
In-Reply-To: <1470226756-24401-1-git-send-email-chris@chris-wilson.co.uk>
On ke, 2016-08-03 at 13:19 +0100, Chris Wilson wrote:
> Now that we initialize the state to both legacy and execlists inside
> intel_engine_cs, we should also clean up that state from the common
> functions.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_engine_cs.c | 14 ++++++++++++++
> drivers/gpu/drm/i915/intel_lrc.c | 5 +----
> drivers/gpu/drm/i915/intel_ringbuffer.c | 4 +---
> drivers/gpu/drm/i915/intel_ringbuffer.h | 1 +
> 4 files changed, 17 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c b/drivers/gpu/drm/i915/intel_engine_cs.c
> index b18f8c9a600c..3e37a122ad73 100644
> --- a/drivers/gpu/drm/i915/intel_engine_cs.c
> +++ b/drivers/gpu/drm/i915/intel_engine_cs.c
> @@ -213,3 +213,17 @@ int intel_engine_init_common(struct intel_engine_cs *engine)
>
> return intel_engine_init_cmd_parser(engine);
> }
> +
> +/**
> + * intel_engines_cleanup_common - cleans up the engine state created by
> + * the common initiailizers.
> + * @engine: Engine to cleanup.
> + *
> + * This cleans up everything created by the common helpers.
> + */
> +void intel_engine_cleanup_common(struct intel_engine_cs *engine)
> +{
> + intel_engine_cleanup_cmd_parser(engine);
> + intel_engine_fini_breadcrumbs(engine);
> + i915_gem_batch_pool_fini(&engine->batch_pool);
The order of calls is changed, this being the more correct, but having
faith on CI and;
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-03 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 12:19 [PATCH] drm/i915: Move the common engine cleanup to intel_engine_cs.c Chris Wilson
2016-08-03 12:41 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-08-03 12:52 ` Joonas Lahtinen [this message]
2016-08-03 13:08 ` [PATCH] " Chris Wilson
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=1470228751.3860.12.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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.