From: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Ben Widawsky <ben@bwidawsk.net>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915: Force sync command ordering (Gen6+)
Date: Wed, 7 Dec 2011 11:58:05 -0800 [thread overview]
Message-ID: <20111207115805.13f5cfde@jbarnes-desktop> (raw)
In-Reply-To: <20111207103841.7627b5fe@jbarnes-desktop>
[-- Attachment #1.1: Type: text/plain, Size: 1427 bytes --]
On Wed, 7 Dec 2011 10:38:41 -0800
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Wed, 07 Dec 2011 10:35:45 -0800
> Eric Anholt <eric@anholt.net> wrote:
>
> > On Sat, 22 Oct 2011 19:41:24 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> > > The docs say this is required for Gen7, and since the bit was added for
> > > Gen6, we are also setting it there pit pf paranoia. Particularly as
> > > Chris points out, if PIPE_CONTROL counts as a 3d state packet.
> > >
> > > This was found through doc inspection by Ken and applies to Gen6+;
> > >
> > > Cc: Keith Packard <keithp@keithp.com>
> > > Reported-by: Kenneth Graunke <kenneth@whitecape.org>
> > > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> > > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> >
> > Reviewed-by: Eric Anholt <eric@anholt.net>
> >
> > however, it doesn't appear to help Ivybridge IRQ troubles.
>
> You could try something like the below to force the use of PIPE_NOTIFY
> instead. Only lightly tested on IVB when we had lots of other bugs, so
> I'm not sure if it works at all.
Though if it's the blit ring hanging, you'd have to try using a
flush_dw notify (if such a thing exists) instead... I don't think the
BLT ring gets much exercise outside Linux so there could well be some
bugs.
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-12-07 19:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 2:41 [PATCH 1/3] drm/i915: relative_constants_mode race fix Ben Widawsky
2011-10-23 2:41 ` [PATCH 2/3] drm/i915: Force sync command ordering (Gen6+) Ben Widawsky
2011-12-07 18:35 ` Eric Anholt
2011-12-07 18:38 ` Jesse Barnes
2011-12-07 19:58 ` Jesse Barnes [this message]
2011-12-07 20:54 ` Eric Anholt
2011-12-07 21:03 ` Jesse Barnes
2011-12-09 2:35 ` Eric Anholt
2011-12-14 21:33 ` Jesse Barnes
2011-12-15 14:50 ` Eugeni Dodonov
2011-10-23 2:41 ` [PATCH 3/3] drm/i915: extract constant offset setting Ben Widawsky
2011-10-23 20:30 ` [PATCH 1/3] drm/i915: relative_constants_mode race fix Ben Widawsky
2011-11-23 21:34 ` Keith Packard
2011-11-23 21:59 ` Ben Widawsky
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=20111207115805.13f5cfde@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=ben@bwidawsk.net \
--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.