From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keith Packard <keithp@keithp.com>
Subject: Re: [PATCH] drm/i915: Use PIPE_CONTROL for flushing on
	gen6+.
Date: Mon, 26 Sep 2011 13:15:00 -0700
Message-ID: <yunlitbkqm3.fsf@aiko.keithp.com>
References: <1317063563-1526-1-git-send-email-kenneth@whitecape.org>
	<d08817$1l8egs@azsmga001.ch.intel.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0511837244=="
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from keithp.com (home.keithp.com [63.227.221.253])
	by gabe.freedesktop.org (Postfix) with ESMTP id C61009E797
	for <intel-gfx@lists.freedesktop.org>;
	Mon, 26 Sep 2011 13:15:05 -0700 (PDT)
In-Reply-To: <d08817$1l8egs@azsmga001.ch.intel.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: Chris Wilson <chris@chris-wilson.co.uk>, Kenneth Graunke <kenneth@whitecape.org>, intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

--===============0511837244==
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Mon, 26 Sep 2011 20:16:04 +0100, Chris Wilson <chris@chris-wilson.co.uk>=
 wrote:

> PIPE_CONTROL and its workarounds is a very bitter pill to swallow if
> MI_FLUSH continues to function.

If you look at the simulator source code, you'll see that it implements
MI_FLUSH as a specific kind of PIPE_CONTROL. And that MI_FLUSH isn't
being validated anymore. If this is all true, then this isn't a huge
change, other than exposing which PIPE_CONTROL workarounds we're
supposed to be using in the MI_FLUSH paths...

=2D-=20
keith.packard@intel.com

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iD8DBQFOgN1EQp8BWwlsTdMRAoYIAJ0XSPQFKNttlVUDMnswHcX7d3qWXACdHBu2
1G1SjXSsNera1/WeTdiwL40=
=z73Y
-----END PGP SIGNATURE-----
--=-=-=--

--===============0511837244==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

--===============0511837244==--