public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/skl: Use correct use counters for	force wakes
Date: Thu, 25 Sep 2014 15:05:27 +0300	[thread overview]
Message-ID: <874mvvhpmg.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20140925102916.GC15638@strange.amr.corp.intel.com>

Damien Lespiau <damien.lespiau@intel.com> writes:

> On Thu, Sep 25, 2014 at 11:17:00AM +0100, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> 
>> Write and reads following the block changed use engine specific use counters
>> and unless that is matched here force wake use counting goes bad. Same
>> force wake is attempted to be taken twice which leads to at least time outs.
>> 
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Is it worth a v2 to have gen >= 9 here?

I think we should have gen >= 8 here.

Shadowed ELSP's seems not to work on gen8. And the posting read will
need fw anyways.

Assuming the shadowing works on skl and we can get rid of the posting
read, we could run this part without taking forcewake.

-Mika

> -- 
> Damien
>
>> ---
>>  drivers/gpu/drm/i915/intel_lrc.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
>> index 3048d78..4b33767 100644
>> --- a/drivers/gpu/drm/i915/intel_lrc.c
>> +++ b/drivers/gpu/drm/i915/intel_lrc.c
>> @@ -301,7 +301,7 @@ static void execlists_elsp_write(struct intel_engine_cs *ring,
>>  	 * Instead, we do the runtime_pm_get/put when creating/destroying requests.
>>  	 */
>>  	spin_lock_irqsave(&dev_priv->uncore.lock, flags);
>> -	if (IS_CHERRYVIEW(dev_priv->dev)) {
>> +	if (IS_CHERRYVIEW(dev_priv->dev) || IS_GEN9(dev_priv->dev)) {
>>  		if (dev_priv->uncore.fw_rendercount++ == 0)
>>  			dev_priv->uncore.funcs.force_wake_get(dev_priv,
>>  							      FORCEWAKE_RENDER);
>> @@ -326,7 +326,7 @@ static void execlists_elsp_write(struct intel_engine_cs *ring,
>>  
>>  	/* Release Force Wakeup (see the big comment above). */
>>  	spin_lock_irqsave(&dev_priv->uncore.lock, flags);
>> -	if (IS_CHERRYVIEW(dev_priv->dev)) {
>> +	if (IS_CHERRYVIEW(dev_priv->dev) || IS_GEN9(dev_priv->dev)) {
>>  		if (--dev_priv->uncore.fw_rendercount == 0)
>>  			dev_priv->uncore.funcs.force_wake_put(dev_priv,
>>  							      FORCEWAKE_RENDER);
>> -- 
>> 2.1.0
>> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2014-09-25 12:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25 10:17 [PATCH] drm/i915/skl: Use correct use counters for force wakes Tvrtko Ursulin
2014-09-25 10:29 ` Damien Lespiau
2014-09-25 12:05   ` Mika Kuoppala [this message]
2014-09-25 12:43     ` Tvrtko Ursulin
2014-09-25 13:13       ` Damien Lespiau
2014-09-30 14:08 ` Tvrtko Ursulin
2014-09-30 14:19   ` Damien Lespiau
2014-09-30 14:57   ` Chris Wilson
2014-09-30 15:58     ` Tvrtko Ursulin
2014-09-30 16:29       ` 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=874mvvhpmg.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=damien.lespiau@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox