From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/skl: Use correct use counters for force wakes
Date: Tue, 30 Sep 2014 16:58:54 +0100 [thread overview]
Message-ID: <542AD33E.1030300@linux.intel.com> (raw)
In-Reply-To: <20140930145703.GN19278@nuc-i3427.alporthouse.com>
On 09/30/2014 03:57 PM, Chris Wilson wrote:
> On Tue, Sep 30, 2014 at 03:08:02PM +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.
>>
>> NOTE: Depending on feedback from hardware designers it may not be necessary
>> to grab force wakes on Gen9 here. But for Gen8 it is needed due to a race
>> between RC6 and ELSP writes.
>>
>> v2: Added blitter force wake engine and made more future proof.
>> Added commit note.
>
> Speaking of futureproofing, what did you think of my patch to remove the
> duplicated counting logic?
[For reference it is called "[PATCH] drm/i915: Reduce duplicated
forcewake logic".]
Disclaimer: I don't know this code that well - only had to dig into it a
few days back when I hit this bug which resulted in my patch.
But from a glance your patch does make it look cleaner and indeed more
future proof (much better separation between platform specific and
generic). Does it need a proper review to move it forward?
Regards,
Tvrtko
next prev parent reply other threads:[~2014-09-30 15:59 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
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 [this message]
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=542AD33E.1030300@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
/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