From: Eric Anholt <eric@anholt.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Ben Widawsky <ben@bwidawsk.net>,
"drivers, Intel" <Intel-gfx@lists.freedesktop.org>
Subject: Re: Is MI_FLUSH_ENABLE bit 12?
Date: Tue, 06 Dec 2011 11:56:07 -0800 [thread overview]
Message-ID: <87k469iieg.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <20111205145709.5a12cee4@jbarnes-desktop>
[-- Attachment #1.1: Type: text/plain, Size: 2390 bytes --]
On Mon, 5 Dec 2011 14:57:09 -0800, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Wed, 30 Nov 2011 13:54:47 -0800
> Eric Anholt <eric@anholt.net> wrote:
>
> > On Wed, 30 Nov 2011 03:42:00 +0000, Ben Widawsky <ben@bwidawsk.net> wrote:
> > Non-text part: multipart/signed
> > > On Tue, Nov 29, 2011 at 04:47:57PM -0800, Eric Anholt wrote:
> > > > On Mon, 28 Nov 2011 18:48:04 -0800, "Keith Packard" <keithp@keithp.com> wrote:
> > > > Non-text part: multipart/mixed
> > > > Non-text part: multipart/signed
> > > > >
> > > > > Just reading through vol1c.4 of the bspec this evening and found something odd.
> > > > >
> > > > > Bit 11 of MI_MODE is "Invalidate UHPTR enable".
> > > > > Bit 12 of MI_MODE is "MI_FLUSH Enable"
> > > > >
> > > > > And, yet, in i915_reg.h:
> > > > >
> > > > > #define MI_MODE 0x0209c
> > > > > # define VS_TIMER_DISPATCH (1 << 6)
> > > > > # define MI_FLUSH_ENABLE (1 << 11)
> > > > >
> > > > > Are we off-by-one on MI_FLUSH_ENABLE? Seems like this would cause
> > > > > serious problems...
> > > >
> > > > I think we are. On the other hand, based on actual behavior plus
> > > > reading of simulator, I believe that the bit does nothing, regardless.
> > >
> > > I do not think so. We've (Chris, I, and perhaps Jesse?) been through
> > > this excercise at least twice before, and both times resulted in hangs
> > > when we switched to bit 12 on Ironlake, not sure about other platforms.
> >
> > There is no MI_FLUSH enable bit on Ironlake in my copy of the docs. Bit
> > 12 is MBZ on that hardware.
>
> It's one of those "been there forever" bits. A comment wouldn't hurt,
> but we should also put in a doc change request (in fact I think I did
> that but it went into a black hole).
Well, by "been there forever", you mean "introduced in:
commit a69ffdbfcba8eabf2ca9d384b578e6f28b339c61
Author: Zhenyu Wang <zhenyuw@linux.intel.com>
Date: Mon Aug 30 16:12:42 2010 +0800
drm/i915: Enable MI_FLUSH on Sandybridge
MI_FLUSH is being deprecated, but still available on Sandybridge.
Make sure it's enabled as userspace still uses MI_FLUSH.
Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: stable@kernel.org
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>"
It should be removed on Ironlake, and fixed to be 12 on SNB or just
removed.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 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-06 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 2:48 Is MI_FLUSH_ENABLE bit 12? Keith Packard
2011-11-30 0:47 ` Eric Anholt
2011-11-30 3:42 ` Ben Widawsky
2011-11-30 8:08 ` Keith Packard
2011-11-30 21:54 ` Eric Anholt
2011-12-05 22:57 ` Jesse Barnes
2011-12-06 19:56 ` Eric Anholt [this message]
2011-12-06 20:21 ` Jesse Barnes
2011-12-06 21:04 ` 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=87k469iieg.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=ben@bwidawsk.net \
--cc=jbarnes@virtuousgeek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox