From: Damien Lespiau <damien.lespiau@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH] drm/i915: Fix possible overflow when recording semaphore states.
Date: Fri, 18 Jul 2014 16:47:52 +0100 [thread overview]
Message-ID: <20140718154752.GD31263@strange.amr.corp.intel.com> (raw)
In-Reply-To: <1405672769-8104-1-git-send-email-rodrigo.vivi@intel.com>
On Fri, Jul 18, 2014 at 01:39:29AM -0700, Rodrigo Vivi wrote:
> semaphore _sync_seqno, _seqno and _mbox are smaller than number of rings.
> This optimization is to remove the ring itself from the list and the logic to do that
> is at intel_ring_sync_index as below:
>
> /*
> * rcs -> 0 = vcs, 1 = bcs, 2 = vecs, 3 = vcs2;
> * vcs -> 0 = bcs, 1 = vecs, 2 = vcs2, 3 = rcs;
> * bcs -> 0 = vecs, 1 = vcs2. 2 = rcs, 3 = vcs;
> * vecs -> 0 = vcs2, 1 = rcs, 2 = vcs, 3 = bcs;
> * vcs2 -> 0 = rcs, 1 = vcs, 2 = bcs, 3 = vecs;
> */
>
> v2: Skip when from == to (Damien).
>
> Cc: Damien Lespiau <damien.lespiau@intel.com>
> Cc: Ben Widawsky <benjamin.widawsky@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/i915_gpu_error.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
> index 9faebbc..6608bee 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -764,7 +764,7 @@ static void gen8_record_semaphore_state(struct drm_i915_private *dev_priv,
> struct intel_engine_cs *ring,
> struct drm_i915_error_ring *ering)
> {
> - struct intel_engine_cs *useless;
> + struct intel_engine_cs *to;
> int i;
>
> if (!i915_semaphore_is_enabled(dev_priv->dev))
> @@ -776,13 +776,17 @@ static void gen8_record_semaphore_state(struct drm_i915_private *dev_priv,
> dev_priv->semaphore_obj,
> &dev_priv->gtt.base);
>
> - for_each_ring(useless, dev_priv, i) {
> + for_each_ring(to, dev_priv, i) {
> u16 signal_offset =
> (GEN8_SIGNAL_OFFSET(ring, i) & PAGE_MASK) / 4;
> u32 *tmp = error->semaphore_obj->pages[0];
> + int idx = intel_ring_sync_index(ring, to);
>
> - ering->semaphore_mboxes[i] = tmp[signal_offset];
> - ering->semaphore_seqno[i] = ring->semaphore.sync_seqno[i];
> + if (ring->id == to->id)
> + return;
continue; ? you need to skip "ring", but you also need to fill the array
when to->id > ring->id.
I guess you should also be able to short-circuit the iteration sooner as
well, no need to do the computations. I believe if "(ring == to)" would
work as well.
--
Damien
next prev parent reply other threads:[~2014-07-18 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 12:35 [PATCH] drm/i915: Fix possible overflow when recording semaphore states Rodrigo Vivi
2014-07-17 21:31 ` Ben Widawsky
2014-07-18 10:29 ` Damien Lespiau
2014-07-18 8:39 ` Rodrigo Vivi
2014-07-18 15:47 ` Damien Lespiau [this message]
2014-07-18 9:05 ` Rodrigo Vivi
2014-07-18 16:12 ` Damien Lespiau
2014-07-18 9:19 ` Rodrigo Vivi
2014-07-19 2:00 ` Ben Widawsky
2014-07-21 9:20 ` Daniel Vetter
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=20140718154752.GD31263@strange.amr.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=benjamin.widawsky@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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