From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/9] drm/i915: Remove early l3-remap
Date: Tue, 19 Apr 2016 10:41:23 +0100 [thread overview]
Message-ID: <5715FD43.9050506@linux.intel.com> (raw)
In-Reply-To: <1461048560-31983-5-git-send-email-chris@chris-wilson.co.uk>
On 19/04/16 07:49, Chris Wilson wrote:
> Since we do the l3-remap on context switch, and proceed to do a context
> switch immediately after manually doing the l3-remap, we can remove the
> redundant manual call.
Looks like it should say it is removing the l3-remap on driver load, not
"manual".
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/i915_drv.h | 1 -
> drivers/gpu/drm/i915/i915_gem.c | 39 +--------------------------------
> drivers/gpu/drm/i915/i915_gem_context.c | 31 +++++++++++++++++++++++++-
> 3 files changed, 31 insertions(+), 40 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index 368fd7090189..4c55f480f60b 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -2983,7 +2983,6 @@ bool i915_gem_clflush_object(struct drm_i915_gem_object *obj, bool force);
> int __must_check i915_gem_init(struct drm_device *dev);
> int i915_gem_init_engines(struct drm_device *dev);
> int __must_check i915_gem_init_hw(struct drm_device *dev);
> -int i915_gem_l3_remap(struct drm_i915_gem_request *req, int slice);
> void i915_gem_init_swizzling(struct drm_device *dev);
> void i915_gem_cleanup_engines(struct drm_device *dev);
> int __must_check i915_gpu_idle(struct drm_device *dev);
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index c9d7dfc8f80c..fd9a36badb45 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -4077,35 +4077,6 @@ err:
> return ret;
> }
>
> -int i915_gem_l3_remap(struct drm_i915_gem_request *req, int slice)
> -{
> - struct intel_engine_cs *engine = req->engine;
> - u32 *remap_info = to_i915(req)->l3_parity.remap_info[slice];
Wrong base.
> - int i, ret;
> -
> - if (!HAS_L3_DPF(req) || !remap_info)
> - return 0;
> -
> - ret = intel_ring_begin(req, GEN7_L3LOG_SIZE / 4 * 3);
> - if (ret)
> - return ret;
> -
> - /*
> - * Note: We do not worry about the concurrent register cacheline hang
> - * here because no other code should access these registers other than
> - * at initialization time.
> - */
> - for (i = 0; i < GEN7_L3LOG_SIZE / 4; i++) {
> - intel_ring_emit(engine, MI_LOAD_REGISTER_IMM(1));
> - intel_ring_emit_reg(engine, GEN7_L3LOG(slice, i));
> - intel_ring_emit(engine, remap_info[i]);
> - }
> -
> - intel_ring_advance(engine);
> -
> - return ret;
> -}
> -
> void i915_gem_init_swizzling(struct drm_device *dev)
> {
> struct drm_i915_private *dev_priv = dev->dev_private;
> @@ -4210,7 +4181,7 @@ i915_gem_init_hw(struct drm_device *dev)
> {
> struct drm_i915_private *dev_priv = dev->dev_private;
> struct intel_engine_cs *engine;
> - int ret, j;
> + int ret;
>
> if (INTEL_INFO(dev)->gen < 6 && !intel_enable_gtt())
> return -EIO;
> @@ -4284,14 +4255,6 @@ i915_gem_init_hw(struct drm_device *dev)
> break;
> }
>
> - if (engine->id == RCS) {
> - for (j = 0; j < NUM_L3_SLICES(dev); j++) {
> - ret = i915_gem_l3_remap(req, j);
> - if (ret)
> - goto err_request;
> - }
> - }
> -
> ret = i915_ppgtt_init_ring(req);
> if (ret)
> goto err_request;
> diff --git a/drivers/gpu/drm/i915/i915_gem_context.c b/drivers/gpu/drm/i915/i915_gem_context.c
> index db53d811370d..6870556a180b 100644
> --- a/drivers/gpu/drm/i915/i915_gem_context.c
> +++ b/drivers/gpu/drm/i915/i915_gem_context.c
> @@ -691,6 +691,35 @@ needs_pd_load_post(struct intel_context *to, u32 hw_flags)
> return false;
> }
>
> +static int remap_l3(struct drm_i915_gem_request *req, int slice)
> +{
> + u32 *remap_info = to_i915(req)->l3_parity.remap_info[slice];
> + struct intel_engine_cs *engine = req->engine;
> + int i, ret;
> +
> + if (!remap_info)
> + return 0;
HAS_L3_DPF check is gone. Ok it looks correct from the call site, but
best would be not to change it when moving around.
> +
> + ret = intel_ring_begin(req, GEN7_L3LOG_SIZE/4 * 2 + 2);
More changes - should you perhaps add a patch which simplifies l3 remap
to use since lri ahead of this one?
> + if (ret)
> + return ret;
> +
> + /*
> + * Note: We do not worry about the concurrent register cacheline hang
> + * here because no other code should access these registers other than
> + * at initialization time.
> + */
> + intel_ring_emit(engine, MI_LOAD_REGISTER_IMM(GEN7_L3LOG_SIZE/4));
> + for (i = 0; i < GEN7_L3LOG_SIZE/4; i++) {
> + intel_ring_emit_reg(engine, GEN7_L3LOG(slice, i));
> + intel_ring_emit(engine, remap_info[i]);
> + }
> + intel_ring_emit(engine, MI_NOOP);
> + intel_ring_advance(engine);
> +
> + return 0;
> +}
> +
> static int do_rcs_switch(struct drm_i915_gem_request *req)
> {
> struct intel_context *to = req->ctx;
> @@ -810,7 +839,7 @@ static int do_rcs_switch(struct drm_i915_gem_request *req)
> if (!(to->remap_slice & (1<<i)))
> continue;
>
> - ret = i915_gem_l3_remap(req, i);
> + ret = remap_l3(req, i);
> if (ret)
> return ret;
>
>
Otherwise looks safe, although I am not sure why it belongs in this series.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-19 9:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 11:54 [PATCH 0/3] GuC premature LRC unpin Tvrtko Ursulin
2016-04-15 11:54 ` [PATCH 1/3] drm/i915: Refactor execlists default context pinning Tvrtko Ursulin
2016-04-15 12:16 ` Chris Wilson
2016-04-15 13:21 ` Tvrtko Ursulin
2016-04-15 11:54 ` [PATCH 2/3] drm/i915/guc: Keep the previous context pinned until the next one has been completed Tvrtko Ursulin
2016-04-15 12:12 ` Chris Wilson
2016-04-15 13:16 ` Tvrtko Ursulin
2016-04-15 11:54 ` [PATCH 3/3] DO NOT MERGE: drm/i915: Enable GuC submission Tvrtko Ursulin
2016-04-15 15:24 ` ✗ Fi.CI.BAT: warning for GuC premature LRC unpin Patchwork
2016-04-19 6:49 ` Premature " Chris Wilson
2016-04-19 6:49 ` [PATCH 1/9] drm/i915: Assign every HW context a unique ID Chris Wilson
2016-04-19 8:57 ` Tvrtko Ursulin
2016-04-19 9:04 ` Chris Wilson
2016-04-19 9:20 ` Tvrtko Ursulin
2016-04-19 6:49 ` [PATCH 2/9] drm/i915: Replace the pinned context address with its " Chris Wilson
2016-04-19 9:03 ` Tvrtko Ursulin
2016-04-19 6:49 ` [PATCH 3/9] drm/i915: Refactor execlists default context pinning Chris Wilson
2016-04-19 9:16 ` Tvrtko Ursulin
2016-04-19 9:55 ` [PATCH] " Chris Wilson
2016-04-19 6:49 ` [PATCH 4/9] drm/i915: Remove early l3-remap Chris Wilson
2016-04-19 9:41 ` Tvrtko Ursulin [this message]
2016-04-19 10:07 ` [PATCH 1/3] drm/i915: L3 cache remapping is part of context switching Chris Wilson
2016-04-19 10:07 ` [PATCH 2/3] drm/i915: Consolidate L3 remapping LRI Chris Wilson
2016-04-19 10:21 ` Tvrtko Ursulin
2016-04-19 10:07 ` [PATCH 3/3] drm/i915: Remove early l3-remap Chris Wilson
2016-04-19 10:23 ` Tvrtko Ursulin
2016-04-19 10:20 ` [PATCH 1/3] drm/i915: L3 cache remapping is part of context switching Tvrtko Ursulin
2016-04-19 6:49 ` [PATCH 5/9] drm/i915: Rearrange switch_context to load the aliasing ppgtt on first use Chris Wilson
2016-04-19 9:52 ` Tvrtko Ursulin
2016-04-19 6:49 ` [PATCH 6/9] drm/i915: Move context initialisation to first-use Chris Wilson
2016-04-19 9:57 ` Tvrtko Ursulin
2016-04-19 10:15 ` Tvrtko Ursulin
2016-04-19 10:55 ` Chris Wilson
2016-04-19 6:49 ` [PATCH 7/9] drm/i915: Move the magical deferred context allocation into the request Chris Wilson
2016-04-19 10:28 ` Tvrtko Ursulin
2016-04-19 6:49 ` [PATCH 8/9] drm/i915: Track the previous pinned context inside " Chris Wilson
2016-04-19 12:02 ` Tvrtko Ursulin
2016-04-19 12:14 ` Chris Wilson
2016-04-19 6:49 ` [PATCH 9/9] drm/i915: Move releasing of the GEM request from free to retire/cancel Chris Wilson
2016-04-19 12:16 ` Tvrtko Ursulin
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=5715FD43.9050506@linux.intel.com \
--to=tvrtko.ursulin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).