From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/6] ring seqno wrap handling
Date: Tue, 04 Dec 2012 14:05:42 +0000 [thread overview]
Message-ID: <6c3329$7g2496@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1354626725-8521-1-git-send-email-mika.kuoppala@intel.com>
On Tue, 4 Dec 2012 15:11:59 +0200, Mika Kuoppala <mika.kuoppala@linux.intel.com> wrote:
> Hi,
>
> As Ben suggested, explicitly syncing across wrap boundary
> revealed yet another set of issues that gem_stress didn't find.
>
> So here is a patchset which addresses the syncing problems
> across wrap boundary. Chris helped me to carve out seqno handling
> ugliness from my initial attempts to handle the ring wrapping.
>
> As I can't break this anymore, i added 6/6.
> --Mika
>
> Mika Kuoppala (6):
> drm/i915: Fix debugfs seqno info print to use uint
> drm/i915: Don't emit semaphore wait if wrap happened
> drm/i915: Split intel_ring_begin
> drm/i915: Add intel_ring_handle_seqno wrap
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> drm/i915: Add debugfs entry to read/write next_seqno
Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
> drm/i915: Set initial seqno value close to wrap boundary
*washes hands*
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-12-04 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 13:11 [PATCH 0/6] ring seqno wrap handling Mika Kuoppala
2012-12-04 13:12 ` [PATCH 1/6] drm/i915: Add debugfs entry to read/write next_seqno Mika Kuoppala
2012-12-04 13:12 ` [PATCH 2/6] drm/i915: Fix debugfs seqno info print to use uint Mika Kuoppala
2012-12-04 13:12 ` [PATCH 3/6] drm/i915: Don't emit semaphore wait if wrap happened Mika Kuoppala
2012-12-05 20:44 ` Paulo Zanoni
2012-12-06 8:51 ` Daniel Vetter
2012-12-06 11:41 ` Paulo Zanoni
2012-12-06 12:14 ` Daniel Vetter
2012-12-06 12:24 ` Chris Wilson
2012-12-06 14:12 ` [PATCH] Detect wraparound using next-seqno rather than waiter->olr Chris Wilson
2012-12-04 13:12 ` [PATCH 4/6] drm/i915: Split intel_ring_begin Mika Kuoppala
2012-12-04 13:12 ` [PATCH 5/6] drm/i915: Add intel_ring_handle_seqno wrap Mika Kuoppala
2012-12-04 13:12 ` [PATCH 6/6] drm/i915: Set initial seqno value close to wrap boundary Mika Kuoppala
2012-12-04 14:05 ` Chris Wilson [this message]
2012-12-04 22:03 ` [PATCH 0/6] ring seqno wrap handling 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='6c3329$7g2496@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@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