Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Volkin, Bradley D" <bradley.d.volkin@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Add OACONTROL to the command parser register whitelist.
Date: Thu, 27 Mar 2014 08:57:08 -0700	[thread overview]
Message-ID: <20140327155708.GA4690@bdvolkin-ubuntu-desktop> (raw)
In-Reply-To: <20140327075721.GA26878@phenom.ffwll.local>

[snip]

On Thu, Mar 27, 2014 at 12:57:21AM -0700, Daniel Vetter wrote:
> Another one that blows is igt/gen7_forcewake_mt. Not sure yet whether it's
> an issue with the test or the checker:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=76670

For this one, the parser rejects an MI_STORE_REGISTER_MEM with the GGTT bit
set. We don't currently allow that, even from master. It sounds like there
might be released versions of the ddx that do this as well. If that's the
case, or if there are other situations where tests, etc rely on being able
to do whatever they want when setting the I915_DISPATCH_SECURE flag, then I
think we might as well stop parsing secure batches and let them go through
as before.

Thanks,
Brad

> 
> Cheers, Daniel
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-03-27 15:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26  5:52 [PATCH] drm/i915: Add OACONTROL to the command parser register whitelist Kenneth Graunke
2014-03-26  6:21 ` Daniel Vetter
2014-03-26 16:03   ` Volkin, Bradley D
2014-03-26 16:38     ` Daniel Vetter
2014-03-26 17:37       ` Kenneth Graunke
2014-03-26 18:26         ` Volkin, Bradley D
2014-03-26 21:48           ` Daniel Vetter
2014-03-26 22:34           ` Kenneth Graunke
2014-03-27  7:57           ` Daniel Vetter
2014-03-27 15:57             ` Volkin, Bradley D [this message]
2014-03-27 20:16               ` Daniel Vetter
2014-03-27 21:34                 ` Kenneth Graunke
2014-03-27 22:44                   ` Daniel Vetter
2014-03-27 23:22                     ` Kenneth Graunke
2014-05-16 19:05                       ` Jesse Barnes
2014-05-16 19:20                         ` Chris Wilson
2014-05-16 19:34                           ` Jesse Barnes
2014-05-16 19:49                             ` Chris Wilson
2014-05-16 20:12                               ` Jesse Barnes
2014-05-16 19:53                             ` Jesse Barnes
2014-05-16 20:12                               ` Volkin, Bradley D
2014-05-16 20:14                                 ` Jesse Barnes
2014-03-27 23:42                 ` Volkin, Bradley D
2014-03-28  7:36                   ` Chris Wilson
2014-03-26  9:57 ` Jani Nikula
2014-03-26 10:41   ` [PATCH v2] " Kenneth Graunke

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=20140327155708.GA4690@bdvolkin-ubuntu-desktop \
    --to=bradley.d.volkin@intel.com \
    --cc=daniel@ffwll.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox