All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/6] drm/i915: simplify testing for the global default context
Date: Tue, 22 Dec 2015 11:35:08 +0000	[thread overview]
Message-ID: <5679356C.2050503@intel.com> (raw)
In-Reply-To: <20151222090539.GA2641@nuc-i3427.alporthouse.com>

On 22/12/15 09:05, Chris Wilson wrote:
> On Mon, Dec 21, 2015 at 04:04:41PM +0000, Dave Gordon wrote:
>> There are quite a number of places where the driver tests whether a
>> given context is or is not the global default context, usually by
>> checking whether an engine's default_pointer points to the context. Now
>> that we have a 'is_global_default' flag in the context itself, these can
>> be rewritten to use it. This makes the logic more obvious, and usually
>> saves at least one memory reference.
>
> All these places do not need to exist. Please just fix execlists.
> -Chris

The patchset "to fix execlists" in one go would be too large to be 
accepted here and would take too long to develop, given the nature of 
the moving target. Ergo, we can fix execlists only by taking every 
opportunity to move towards a clearer design, even though each step 
fails to "fix execlists" on its own.

We therefore have to judge each patch on the basis of "does it make 
things better or worse", not "does it fix all known problems". IMHO, 
this patch (and the rest of the set) are small steps towards a better 
design, and you should therefore support their adoption, unless of 
course you think it actually makes things worse - in which case, point 
out what's worse and I'll change it.

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

  reply	other threads:[~2015-12-22 11:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 16:04 improve handling of the driver's internal default context Dave Gordon
2015-12-21 16:04 ` [PATCH 1/6] drm/i915: mark the global default (intel_)context as such Dave Gordon
2015-12-22  9:08   ` Chris Wilson
2015-12-22 11:26     ` Dave Gordon
2015-12-21 16:04 ` [PATCH 2/6] drm/i915: simplify testing for the global default context Dave Gordon
2015-12-22  9:05   ` Chris Wilson
2015-12-22 11:35     ` Dave Gordon [this message]
2015-12-21 16:04 ` [PATCH 3/6] drm/i915: simplify allocation of driver-internal requests Dave Gordon
2015-12-22  9:08   ` Chris Wilson
2015-12-22 11:36     ` Dave Gordon
2015-12-21 16:04 ` [PATCH 4/6] drm/i915: abolish separate per-engine default_context pointers Dave Gordon
2015-12-21 16:04 ` [PATCH 5/6] drm/i915: tidy up initialisation failure paths (legacy) Dave Gordon
2015-12-21 16:04 ` [PATCH 6/6] drm/i915: tidy up initialisation failure paths (GEM & LRC) Dave Gordon
2015-12-22  7:20 ` ✗ failure: Fi.CI.BAT Patchwork

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=5679356C.2050503@intel.com \
    --to=david.s.gordon@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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.