public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Kenneth Graunke <kenneth@whitecape.org>
To: Daniel Vetter <daniel.vetter@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 16:22:44 -0700	[thread overview]
Message-ID: <5334B2C4.5000702@whitecape.org> (raw)
In-Reply-To: <CAKMK7uEXx00NaP7oZoP-PUUy4zK_0dqtQgPWGV0bs-AvpEJkmw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1276 bytes --]

On 03/27/2014 03:44 PM, Daniel Vetter wrote:
> On Thu, Mar 27, 2014 at 10:34 PM, Kenneth Graunke <kenneth@whitecape.org> wrote:
>> Why are we parsing batches with I915_EXEC_SECURE at all?  Secure batches
>> are only issued from trusted code which is guaranteed to be running as
>> root.  I don't see any benefit to scanning those batches, and there's
>> definitely overhead.
>>
>> I mean, sure, it may be reasonable in the short term as a way to test
>> the command parser, but I certainly hope we don't *ship* that.
> 
> Everyone runs X as root, but I kinda want X to also be able to run as
> non-root. The cmd parser has a special list of drm master register
> lists which should allow this, but if we just bypass the cmd parser
> for all normal X installs we'll have 0 test coverage on this. Which
> means broken like hell.
> 
> Hence I actually intend to ship this, yes. Chris doesn't like it either really.
> -Daniel

Seriously?  Hurt performance on every user's system just so you can test
things?  That a classic case of the tail wagging the dog.

Why not make a i915.enable_cmd_parser=2 value which enables it all the
time and use that when running igt?  Clearly being able to test this is
valuable, but enabling it universally is *not* OK.


[-- Attachment #1.2: OpenPGP digital signature --]
[-- 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

  reply	other threads:[~2014-03-27 23:22 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
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 [this message]
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=5334B2C4.5000702@whitecape.org \
    --to=kenneth@whitecape.org \
    --cc=daniel.vetter@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