From: Ben Widawsky <ben@bwidawsk.net>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 0/4] Haswell GPU hang fixes
Date: Fri, 17 Aug 2012 15:53:53 -0700 [thread overview]
Message-ID: <1f4d08b1efee07ec02fb5d2c7f27636a@bwidawsk.net> (raw)
In-Reply-To: <CA+gsUGRhLmrEC7ZNyONTUUhxeptMfLhUtQYrJtHcavs-dQgqyQ@mail.gmail.com>
On 2012-08-17 15:42, Paulo Zanoni wrote:
> 2012/8/17 Ben Widawsky <ben@bwidawsk.net>:
>> On 2012-08-17 14:35, Paulo Zanoni wrote:
>>>
>>> From: Paulo Zanoni <paulo.r.zanoni@intel.com>
>>>
>>> Hi
>>>
>>> Since we stopped running the gen6 workarounds on gen > 6 I started
>>> seeing a lot
>>> of GPU hangs on my gen 7.5 machine. These patches add gen7+
>>> workarounds
>>> which
>>> prevent the GPU hangs I'm seeing.
>>>
>>> These patches were tested mostly on HSW and briefly on IVB, but the
>>> workarounds
>>> implemented are documented for both. This is also the first time I
>>> touch
>>> this
>>> kind of code, so extra careful reviewing might be needed.
>>>
>>> Thanks,
>>> Paulo
>>>
>>>
>>> Paulo Zanoni (4):
>>> drm/i915: add gen7_render_ring_flush
>>> drm/i915: add workarounds directly to gen6_render_ring_flush
>>> drm/i915: add workaround to gen7_render_ring_flush
>>> drm/i915: add one more workaround to gen7_render_ring_flush
>>>
>>> drivers/gpu/drm/i915/intel_ringbuffer.c | 81
>>> ++++++++++++++++++++++++++++++---
>>> 1 file changed, 74 insertions(+), 7 deletions(-)
>>
>>
>> I don't think this makes for ideal bisection. I'd rather you
>> implement the
>> ring flush + workarounds before you set the pointer. If you want to
>> keep the
>> patches split out like this, just add a 5 patch to do the pointer
>> change
>> that's in the first patch. Or else collapse patch 1, 3, 4 into 1.
>
> But currently gen7 is *already* not running any of the workarounds...
> Patch 1 does not introduce any real difference (neither adds nor
> removes bugs), patch 2 also does not change anything. Only patches 3
> and 4 start to fix the bugs that were already present before the
> series.
>
I guess I thought the patches would be, revert Chris patch to separate
out the workaround, then add IVB specific flush. So now I see you've
done things slightly differently. Sorry for the rushed comments. Also
this doesn't fix my platform :/
>
>>
>> I didn't really review anything yet though.
>>
>> --
>> Ben Widawsky, Intel Open Source Technology Center
--
Ben Widawsky, Intel Open Source Technology Center
prev parent reply other threads:[~2012-08-17 22:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 21:35 [PATCH 0/4] Haswell GPU hang fixes Paulo Zanoni
2012-08-17 21:35 ` [PATCH 1/4] drm/i915: add gen7_render_ring_flush Paulo Zanoni
2012-08-17 21:35 ` [PATCH 2/4] drm/i915: add workarounds directly to gen6_render_ring_flush Paulo Zanoni
2012-08-17 21:35 ` [PATCH 3/4] drm/i915: add workaround to gen7_render_ring_flush Paulo Zanoni
2012-08-28 9:17 ` Daniel Vetter
2012-08-28 13:10 ` Paulo Zanoni
2012-08-28 15:17 ` Daniel Vetter
2012-08-17 21:35 ` [PATCH 4/4] drm/i915: add one more " Paulo Zanoni
2012-08-17 22:39 ` [PATCH 0/4] Haswell GPU hang fixes Ben Widawsky
2012-08-17 22:42 ` Paulo Zanoni
2012-08-17 22:53 ` Ben Widawsky [this message]
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=1f4d08b1efee07ec02fb5d2c7f27636a@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=przanoni@gmail.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