All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/4] drm/i915: Always clear semaphore mboxes on seqno wrap
Date: Tue, 18 Dec 2012 16:19:52 +0200	[thread overview]
Message-ID: <87ip7ze92v.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <eeac1e$5dimc7@AZSMGA002.ch.intel.com>

Chris Wilson <chris@chris-wilson.co.uk> writes:

> On Mon, 17 Dec 2012 18:44:27 +0200, Mika Kuoppala <mika.kuoppala@linux.intel.com> wrote:
>> We need to clear the hw semaphore values explicitly.
>> Even if sync_seqnos are zero, there might still be
>> invalid values in the hw semaphores when we wrap.
>
> This changelog does not make it clear why you want this patch. This is
> for enabling a future feature, right?
>
> Anyway, after initial misgivings because I thought you were trying to
> fix a bug rather than add a feature, and provided that you improve the
> changelog,

The intent is to always clear the mboxes and also set the hws page when
seqno is set. Both when wrapping and setting seqno from debugfs. 
The hws part is needed to fix a bug where initial seqno in hws page is
zero (after boot) and driver seqno is past the 2^31 boundary.
I guess i could have split the mboxes and hws page setting apart
saving the optimization but the gain would be little.

I think this is also issue on suspend/resume if we have passed 2^31 on
suspend and we come back with driver setting initial seqno to 1.

In both cases i915_seqno_passed(ring->get_seqno(), driver_seqno) will
return errorneous value.

> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris

Does r-b still stand after the explanation above?

-Mika

  reply	other threads:[~2012-12-18 14:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 16:44 [PATCH 1/4] drm/i915: Initialize hardware semaphore state on ring init Mika Kuoppala
2012-12-17 16:44 ` [PATCH 2/4] drm/i915: Always clear semaphore mboxes on seqno wrap Mika Kuoppala
2012-12-17 19:15   ` Chris Wilson
2012-12-18 14:19     ` Mika Kuoppala [this message]
2012-12-18 14:29       ` Chris Wilson
2012-12-17 16:44 ` [PATCH 3/4] drm/i915: Introduce i915_gem_seqno_init Mika Kuoppala
2012-12-17 16:44 ` [PATCH 4/4] drm/i915: Make next_seqno debugs entry to use i915_gem_seqno_init Mika Kuoppala
2012-12-17 19:13   ` Chris Wilson
2012-12-18 14:32     ` Mika Kuoppala
2012-12-18 14:47       ` Chris Wilson
2012-12-18 15:49         ` Mika Kuoppala
2012-12-17 19:17   ` Chris Wilson
2012-12-18 14:33     ` Mika Kuoppala

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=87ip7ze92v.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@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.