All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 12/39] drm/i915: Allow a context to define its set of engines
Date: Thu, 14 Mar 2019 17:58:00 +0000	[thread overview]
Message-ID: <9520c079-691c-dc06-49bf-eefeabe426d4@linux.intel.com> (raw)
In-Reply-To: <155258373009.4168.13341682459434181199@skylake-alporthouse-com>


On 14/03/2019 17:15, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-03-14 16:47:05)
>>
>> On 13/03/2019 14:43, Chris Wilson wrote:
>>> Over the last few years, we have debated how to extend the user API to
>>> support an increase in the number of engines, that may be sparse and
>>> even be heterogeneous within a class (not all video decoders created
>>> equal). We settled on using (class, instance) tuples to identify a
>>> specific engine, with an API for the user to construct a map of engines
>>> to capabilities. Into this picture, we then add a challenge of virtual
>>> engines; one user engine that maps behind the scenes to any number of
>>> physical engines. To keep it general, we want the user to have full
>>> control over that mapping. To that end, we allow the user to constrain a
>>> context to define the set of engines that it can access, order fully
>>> controlled by the user via (class, instance). With such precise control
>>> in context setup, we can continue to use the existing execbuf uABI of
>>> specifying a single index; only now it doesn't automagically map onto
>>> the engines, it uses the user defined engine map from the context.
>>>
>>> The I915_EXEC_DEFAULT slot is left empty, and invalid for use by
>>> execbuf. It's use will be revealed in the next patch.
>>>
>>> v2: Fixup freeing of local on success of get_engines()
>>> v3: Allow empty engines[]
>>>
>>> Testcase: igt/gem_ctx_engines
>>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>> ---
>>>    drivers/gpu/drm/i915/i915_gem_context.c       | 223 +++++++++++++++++-
>>>    drivers/gpu/drm/i915/i915_gem_context_types.h |   4 +
>>>    drivers/gpu/drm/i915/i915_gem_execbuffer.c    |  19 +-
>>>    drivers/gpu/drm/i915/i915_utils.h             |  23 ++
>>>    include/uapi/drm/i915_drm.h                   |  42 +++-
>>>    5 files changed, 298 insertions(+), 13 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/i915_gem_context.c b/drivers/gpu/drm/i915/i915_gem_context.c
>>> index bac548584091..07377b75b563 100644
>>> --- a/drivers/gpu/drm/i915/i915_gem_context.c
>>> +++ b/drivers/gpu/drm/i915/i915_gem_context.c
>>> @@ -86,7 +86,9 @@
>>>     */
>>>    
>>>    #include <linux/log2.h>
>>> +
>>>    #include <drm/i915_drm.h>
>>> +
>>>    #include "i915_drv.h"
>>>    #include "i915_globals.h"
>>>    #include "i915_trace.h"
>>> @@ -101,6 +103,21 @@ static struct i915_global_gem_context {
>>>        struct kmem_cache *slab_luts;
>>>    } global;
>>>    
>>> +static struct intel_engine_cs *
>>> +lookup_user_engine(struct i915_gem_context *ctx,
>>> +                unsigned long flags, u16 class, u16 instance)
>>
>> You didn't like reducing flags to 32-bit for now?
>>
>>> +#define LOOKUP_USER_INDEX BIT(0)
> 
> No, it's just a register and ^ implies unsigned long.

Yes I accepted the error of my ways later.

> 
>>> +{
>>> +     if (flags & LOOKUP_USER_INDEX) {
>>> +             if (instance >= ctx->nengine)
>>> +                     return NULL;
>>> +
>>> +             return ctx->engines[instance];
>>> +     }
>>> +
>>> +     return intel_engine_lookup_user(ctx->i915, class, instance);
>>> +}
>>> +
>>>    struct i915_lut_handle *i915_lut_handle_alloc(void)
>>>    {
>>>        return kmem_cache_alloc(global.slab_luts, GFP_KERNEL);
>>> @@ -235,6 +252,8 @@ static void i915_gem_context_free(struct i915_gem_context *ctx)
>>>        release_hw_id(ctx);
>>>        i915_ppgtt_put(ctx->ppgtt);
>>>    
>>> +     kfree(ctx->engines);
>>> +
>>>        rbtree_postorder_for_each_entry_safe(it, n, &ctx->hw_contexts, node)
>>>                intel_context_put(it);
>>>    
>>> @@ -1371,9 +1390,9 @@ static int set_sseu(struct i915_gem_context *ctx,
>>>        if (user_sseu.flags || user_sseu.rsvd)
>>>                return -EINVAL;
>>>    
>>> -     engine = intel_engine_lookup_user(i915,
>>> -                                       user_sseu.engine_class,
>>> -                                       user_sseu.engine_instance);
>>> +     engine = lookup_user_engine(ctx, 0,
>>> +                                 user_sseu.engine_class,
>>> +                                 user_sseu.engine_instance);
>>>        if (!engine)
>>>                return -EINVAL;
>>>    
>>> @@ -1391,9 +1410,163 @@ static int set_sseu(struct i915_gem_context *ctx,
>>>    
>>>        args->size = sizeof(user_sseu);
>>>    
>>> +     return 0;
>>> +};
>>> +
>>> +struct set_engines {
>>> +     struct i915_gem_context *ctx;
>>> +     struct intel_engine_cs **engines;
>>> +     unsigned int nengine;
>>> +};
>>> +
>>> +static const i915_user_extension_fn set_engines__extensions[] = {
>>> +};
>>> +
>>> +static int
>>> +set_engines(struct i915_gem_context *ctx,
>>> +         const struct drm_i915_gem_context_param *args)
>>> +{
>>> +     struct i915_context_param_engines __user *user;
>>> +     struct set_engines set = { .ctx = ctx };
>>> +     u64 size, extensions;
>>> +     unsigned int n;
>>> +     int err;
>>> +
>>> +     user = u64_to_user_ptr(args->value);
>>> +     size = args->size;
>>> +     if (!size)
>>> +             goto out;
>>> +
>>> +     BUILD_BUG_ON(!IS_ALIGNED(sizeof(*user), sizeof(*user->class_instance)));
>>> +     if (size < sizeof(*user) ||
>>> +         !IS_ALIGNED(size, sizeof(*user->class_instance)))
>>> +             return -EINVAL;
>>> +
>>> +     set.nengine = (size - sizeof(*user)) / sizeof(*user->class_instance);
>>> +     if (set.nengine > I915_EXEC_RING_MASK + 1)
>>> +             return -EINVAL;
>>> +
>>> +     set.engines = kmalloc_array(set.nengine,
>>> +                                 sizeof(*set.engines),
>>> +                                 GFP_KERNEL);
>>> +     if (!set.engines)
>>> +             return -ENOMEM;
>>> +
>>> +     for (n = 0; n < set.nengine; n++) {
>>> +             u16 class, inst;
>>> +
>>> +             if (get_user(class, &user->class_instance[n].engine_class) ||
>>> +                 get_user(inst, &user->class_instance[n].engine_instance)) {
>>> +                     kfree(set.engines);
>>> +                     return -EFAULT;
>>> +             }
>>> +
>>> +             if (class == (u16)I915_ENGINE_CLASS_INVALID &&
>>> +                 inst == (u16)I915_ENGINE_CLASS_INVALID_NONE) {
>>> +                     set.engines[n] = NULL;
>>> +                     continue;
>>> +             }
>>> +
>>> +             set.engines[n] = lookup_user_engine(ctx, 0, class, inst);
>>> +             if (!set.engines[n]) {
>>> +                     kfree(set.engines);
>>> +                     return -ENOENT;
>>> +             }
>>> +     }
>>> +
>>> +     err = -EFAULT;
>>> +     if (!get_user(extensions, &user->extensions))
>>> +             err = i915_user_extensions(u64_to_user_ptr(extensions),
>>> +                                        set_engines__extensions,
>>> +                                        ARRAY_SIZE(set_engines__extensions),
>>> +                                        &set);
>>> +     if (err) {
>>> +             kfree(set.engines);
>>> +             return err;
>>> +     }
>>> +
>>> +out:
>>> +     mutex_lock(&ctx->i915->drm.struct_mutex);
>>> +     kfree(ctx->engines);
>>> +     ctx->engines = set.engines;
>>> +     ctx->nengine = set.nengine;
>>> +     mutex_unlock(&ctx->i915->drm.struct_mutex);
>>> +
>>>        return 0;
>>>    }
>>>    
>>> +static int
>>> +get_engines(struct i915_gem_context *ctx,
>>> +         struct drm_i915_gem_context_param *args)
>>> +{
>>> +     struct i915_context_param_engines *local;
>>> +     size_t n, count, size;
>>> +     int err = 0;
>>> +
>>> +restart:
>>> +     if (!READ_ONCE(ctx->engines)) {
>>
>> ZERO_OR_NULL_PTR?
> 
> NULL => default, size = 0;
> 
> ZERO_SIZE_PTR => nengines == 0, size = sizeof(base)

Yes if you care about such level of idempotency (to use the name from 
your IGT :) ). I thought that there is no point in returning a size of 8 
back and zeroed extensions pointer.

> 
>>> +             args->size = 0;
>>> +             return 0;
>>> +     }
>>> +
>>> +     count = READ_ONCE(ctx->nengine);
>>> +
>>> +     /* Be paranoid in case we have an impedance mismatch */
>>> +     if (!check_struct_size(local, class_instance, count, &size))
>>> +             return -ENOMEM;
>>> +     if (unlikely(overflows_type(size, args->size)))
>>> +             return -ENOMEM;
>>> +
>>> +     if (!args->size) {
>>> +             args->size = size;
>>> +             return 0;
>>> +     }
>>> +     if (args->size < size)
>>> +             return -EINVAL;
>>
>> else if would read nicer if no blank line.
> 
> Blank line it is.
> 
>>> +
>>> +     local = kmalloc(size, GFP_KERNEL);
>>> +     if (!local)
>>> +             return -ENOMEM;
>>> +
>>> +     if (mutex_lock_interruptible(&ctx->i915->drm.struct_mutex)) {
>>> +             err = -EINTR;
>>> +             goto out;
>>> +     }
>>> +
>>> +     if (!ctx->engines || ctx->nengine != count) {
>>
>> Count check would be sufficient AFAICT.
> 
> Not quite. We may have gone from no engines back to default config
> before taking the lock, so count would be the same, but args->size
> should report differently.
> 
>>> +             mutex_unlock(&ctx->i915->drm.struct_mutex);
>>> +             kfree(local);
>>> +             goto restart;
>>> +     }
>>> +
>>> +     local->extensions = 0;
>>> +     for (n = 0; n < count; n++) {
>>> +             if (ctx->engines[n]) {
>>> +                     local->class_instance[n].engine_class =
>>> +                             ctx->engines[n]->uabi_class;
>>> +                     local->class_instance[n].engine_instance =
>>> +                             ctx->engines[n]->instance;
>>> +             } else {
>>> +                     local->class_instance[n].engine_class =
>>> +                             I915_ENGINE_CLASS_INVALID;
>>> +                     local->class_instance[n].engine_instance =
>>> +                             I915_ENGINE_CLASS_INVALID_NONE;
>>> +             }
>>> +     }
>>> +
>>> +     mutex_unlock(&ctx->i915->drm.struct_mutex);
>>> +
>>> +     if (copy_to_user(u64_to_user_ptr(args->value), local, size)) {
>>> +             err = -EFAULT;
>>> +             goto out;
>>> +     }
>>> +     args->size = size;
>>> +
>>> +out:
>>> +     kfree(local);
>>> +     return err;
>>> +}
>>> +
>>>    static int ctx_setparam(struct i915_gem_context *ctx,
>>>                        struct drm_i915_gem_context_param *args)
>>>    {
>>> @@ -1466,6 +1639,10 @@ static int ctx_setparam(struct i915_gem_context *ctx,
>>>                ret = set_ppgtt(ctx, args);
>>>                break;
>>>    
>>> +     case I915_CONTEXT_PARAM_ENGINES:
>>> +             ret = set_engines(ctx, args);
>>> +             break;
>>> +
>>>        case I915_CONTEXT_PARAM_BAN_PERIOD:
>>>        default:
>>>                ret = -EINVAL;
>>> @@ -1519,6 +1696,30 @@ static int clone_sseu(struct i915_gem_context *dst,
>>>        return 0;
>>>    }
>>>    
>>> +static int clone_engines(struct i915_gem_context *dst,
>>> +                      struct i915_gem_context *src)
>>> +{
>>> +     struct intel_engine_cs **engines;
>>> +     unsigned int nengine;
>>> +
>>> +     mutex_lock(&src->i915->drm.struct_mutex); /* serialise src->engine[] */
>>> +     nengine = src->nengine;
>>> +     if (!ZERO_OR_NULL_PTR(src->engines))
>>
>> A comment taking note of the reason for the ZERO_PTR trick.
> 
> I must have deleted /* XXX why kmemdup, why? */

Indeed why kmemdup? :) I thought it was about allowing count = 0 in the 
set_engines and storing ZERO_PTR in ctx->engines in that case. In which 
case it fall through the else branch and copies over the ZERO_PTR. 
Unless you wanted to complain that kmemdup does not handle ZERO_PTR in 
the source?

> 
>>> +             engines = kmemdup(src->engines,
>>> +                               sizeof(*src->engines) * nengine,
>>> +                               GFP_KERNEL);
>>> +     else
>>> +             engines = src->engines;
>>> +     mutex_unlock(&src->i915->drm.struct_mutex);
>>> +     if (!engines && nengine)
>>> +             return -ENOMEM;
>>> +
>>> +     kfree(dst->engines);
>>> +     dst->engines = engines;
>>> +     dst->nengine = nengine;
>>> +     return 0;
>>> +}
>>> +
>>>    static int create_clone(struct i915_user_extension __user *ext, void *data)
>>>    {
>>>        struct drm_i915_gem_context_create_ext_clone local;
>>> @@ -1587,6 +1788,12 @@ static int create_clone(struct i915_user_extension __user *ext, void *data)
>>>                }
>>>        }
>>>    
>>> +     if (local.flags & I915_CONTEXT_CLONE_ENGINES) {
>>> +             err = clone_engines(dst, src);
>>> +             if (err)
>>> +                     return err;
>>> +     }
>>> +
>>>        return 0;
>>>    }
>>>    
>>> @@ -1705,9 +1912,9 @@ static int get_sseu(struct i915_gem_context *ctx,
>>>        if (user_sseu.flags || user_sseu.rsvd)
>>>                return -EINVAL;
>>>    
>>> -     engine = intel_engine_lookup_user(ctx->i915,
>>> -                                       user_sseu.engine_class,
>>> -                                       user_sseu.engine_instance);
>>> +     engine = lookup_user_engine(ctx, 0,
>>> +                                 user_sseu.engine_class,
>>> +                                 user_sseu.engine_instance);
>>
>> Belongs to a later patch but OK.
> 
> Hmm, you'd rather have it later. I felt introducing the concept that we
> have ctx->engines[] implied we should also be aware when looking up
> engines in a context related fashion. I felt they were connected enough
> that the interface deserved to be in this patch with use through the
> uAPI later.

Yeah makes sense as well. It's OK.

> 
>>> @@ -110,6 +112,8 @@ struct i915_gem_context {
>>>    #define CONTEXT_CLOSED                      1
>>>    #define CONTEXT_FORCE_SINGLE_SUBMISSION     2
>>>    
>>> +     unsigned int nengine;
>>
>> Can I tempt you to pluralise this? I at least find it more obvious in
>> plural.
> 
> Bah, historical precedent is
> int   nengine;
> void *engines;

Not everything historical is good! :)

> 
>>> diff --git a/drivers/gpu/drm/i915/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
>>> index ee6d301a9627..70a26f0a9f1e 100644
>>> --- a/drivers/gpu/drm/i915/i915_gem_execbuffer.c
>>> +++ b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
>>> @@ -2090,13 +2090,20 @@ static const enum intel_engine_id user_ring_map[I915_USER_RINGS + 1] = {
>>>    };
>>>    
>>>    static struct intel_engine_cs *
>>> -eb_select_engine(struct drm_i915_private *dev_priv,
>>> +eb_select_engine(struct i915_execbuffer *eb,
>>>                 struct drm_file *file,
>>>                 struct drm_i915_gem_execbuffer2 *args)
>>>    {
>>>        unsigned int user_ring_id = args->flags & I915_EXEC_RING_MASK;
>>>        struct intel_engine_cs *engine;
>>>    
>>> +     if (eb->ctx->engines) {
>>> +             if (user_ring_id >= eb->ctx->nengine)
>>
>> So empty engine array blocks off submission. It's probably okay, just
>> need to remember throughout the code not to check "if (ctx->engines)"
>> only. I guess someone will get burnt on that sooner or later, but I
>> don't think it's a big deal.
> 
> But as you say, it should only matter at the uAPI boundary. After this
> point, we have our intel_engine_cs assigned; and hopefully we end up
> with intel_context as being our primarily source of truth internally.
> 
> The gem_context should only be used in the GEM boundary, so expect some
> more cleanup!
> 
>>> +static inline bool
>>> +__check_struct_size(size_t base, size_t arr, size_t count, size_t *size)
>>> +{
>>> +     size_t sz;
>>> +
>>> +     if (check_mul_overflow(count, arr, &sz))
>>> +             return false;
>>> +
>>> +     if (check_add_overflow(sz, base, &sz))
>>> +             return false;
>>> +
>>> +     *size = sz;
>>> +     return true;
>>> +}
>>> +
>>> +#define check_struct_size(T, A, C, SZ) \
>>> +     likely(__check_struct_size(sizeof(*(T)), \
>>> +                                sizeof(*(T)->A) + __must_be_array((T)->A), \
>>> +                                C, SZ))
>>
>> A comment explaining usage would be nice.
> 
> /* see struct_size() */

Come on, a bit more than that! Look at those self-documenting args, T, 
A, C, SZ! It needs to say what it will calculate, where it stores it and 
what it returns. If you want to have more hope people will actually use 
the helpers you add.

Regards,

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

  reply	other threads:[~2019-03-14 17:58 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 14:43 [PATCH 01/39] drm/i915: Hold a ref to the ring while retiring Chris Wilson
2019-03-13 14:43 ` [PATCH 02/39] drm/i915: Lock the gem_context->active_list while dropping the link Chris Wilson
2019-03-13 14:43 ` [PATCH 03/39] drm/i915: Hold a reference to the active HW context Chris Wilson
2019-03-13 14:43 ` [PATCH 04/39] drm/i915: Stop needlessly acquiring wakeref for debugfs/drop_caches_set Chris Wilson
2019-03-13 14:43 ` [PATCH 05/39] drm/i915/selftests: Provide stub reset functions Chris Wilson
2019-03-13 14:43 ` [PATCH 06/39] drm/i915: Switch to use HWS indices rather than addresses Chris Wilson
2019-03-13 14:43 ` [PATCH 07/39] drm/i915: Introduce the i915_user_extension_method Chris Wilson
2019-03-14 14:52   ` Tvrtko Ursulin
2019-03-14 14:59     ` Chris Wilson
2019-03-14 16:10       ` Tvrtko Ursulin
2019-03-13 14:43 ` [PATCH 08/39] drm/i915: Create/destroy VM (ppGTT) for use with contexts Chris Wilson
2019-03-13 20:11   ` Rodrigo Vivi
2019-03-13 20:47     ` Chris Wilson
2019-03-13 21:15       ` Rodrigo Vivi
2019-03-14 16:07   ` Tvrtko Ursulin
2019-03-14 16:46     ` Chris Wilson
2019-03-13 14:43 ` [PATCH 09/39] drm/i915: Extend CONTEXT_CREATE to set parameters upon construction Chris Wilson
2019-03-13 14:43 ` [PATCH 10/39] drm/i915: Allow contexts to share a single timeline across all engines Chris Wilson
2019-03-14 16:09   ` Tvrtko Ursulin
2019-03-13 14:43 ` [PATCH 11/39] drm/i915: Allow userspace to clone contexts on creation Chris Wilson
2019-03-14 16:18   ` Tvrtko Ursulin
2019-03-14 16:54     ` Chris Wilson
2019-03-14 17:49       ` Tvrtko Ursulin
2019-03-14 17:55         ` Chris Wilson
2019-03-14 16:56     ` Chris Wilson
2019-03-13 14:43 ` [PATCH 12/39] drm/i915: Allow a context to define its set of engines Chris Wilson
2019-03-14 16:47   ` Tvrtko Ursulin
2019-03-14 17:15     ` Chris Wilson
2019-03-14 17:58       ` Tvrtko Ursulin [this message]
2019-03-14 18:09         ` Chris Wilson
2019-03-13 14:43 ` [PATCH 13/39] drm/i915: Extend I915_CONTEXT_PARAM_SSEU to support local ctx->engine[] Chris Wilson
2019-03-14 16:49   ` Tvrtko Ursulin
2019-03-14 17:04     ` Chris Wilson
2019-03-14 17:19       ` Tvrtko Ursulin
2019-03-13 14:43 ` [PATCH 14/39] drm/i915: Load balancing across a virtual engine Chris Wilson
2019-03-13 14:43 ` [PATCH 15/39] drm/i915: Extend execution fence to support a callback Chris Wilson
2019-03-14 16:50   ` Tvrtko Ursulin
2019-03-13 14:43 ` [PATCH 16/39] drm/i915/execlists: Virtual engine bonding Chris Wilson
2019-03-14 17:26   ` Tvrtko Ursulin
2019-03-15  9:45     ` Chris Wilson
2019-03-13 14:43 ` [PATCH 17/39] drm/i915: Allow specification of parallel execbuf Chris Wilson
2019-03-14 17:27   ` Tvrtko Ursulin
2019-03-13 14:43 ` [PATCH 18/39] drm/i915/execlists: Skip direct submission if only lite-restore Chris Wilson
2019-03-13 14:43 ` [PATCH 19/39] drm/i915: Split GEM object type definition to its own header Chris Wilson
2019-03-13 14:43 ` [PATCH 20/39] drm/i915: Pull GEM ioctls interface to its own file Chris Wilson
2019-03-13 14:43 ` [PATCH 21/39] drm/i915: Move object->pages API to i915_gem_object.[ch] Chris Wilson
2019-03-13 14:43 ` [PATCH 22/39] drm/i915: Move shmem object setup to its own file Chris Wilson
2019-03-13 14:43 ` [PATCH 23/39] drm/i915: Move phys objects " Chris Wilson
2019-03-13 14:43 ` [PATCH 24/39] drm/i915: Move mmap and friends " Chris Wilson
2019-03-13 14:43 ` [PATCH 25/39] drm/i915: Move GEM domain management " Chris Wilson
2019-03-13 14:43 ` [PATCH 26/39] drm/i915: Move more GEM objects under gem/ Chris Wilson
2019-03-13 14:43 ` [PATCH 27/39] drm/i915: Pull scatterlist utils out of i915_gem.h Chris Wilson
2019-03-13 14:43 ` [PATCH 28/39] drm/i915: Move GEM object domain management from struct_mutex to local Chris Wilson
2019-03-13 14:43 ` [PATCH 29/39] drm/i915: Move GEM object waiting to its own file Chris Wilson
2019-03-13 14:43 ` [PATCH 30/39] drm/i915: Move GEM object busy checking " Chris Wilson
2019-03-13 14:43 ` [PATCH 31/39] drm/i915: Move GEM client throttling " Chris Wilson
2019-03-13 14:43 ` [PATCH 32/39] drm/i915: Drop the deferred active reference Chris Wilson
2019-03-13 14:43 ` [PATCH 33/39] drm/i915: Move object close under its own lock Chris Wilson
2019-03-13 14:43 ` [PATCH 34/39] drm/i915: Rename intel_context.active to .inflight Chris Wilson
2019-03-13 14:43 ` [PATCH 35/39] drm/i915: Keep contexts pinned until after the next kernel context switch Chris Wilson
2019-03-13 14:46   ` Chris Wilson
2019-03-13 14:43 ` [PATCH 36/39] drm/i915: Stop retiring along engine Chris Wilson
2019-03-13 14:43 ` [PATCH 37/39] drm/i915: Replace engine->timeline with a plain list Chris Wilson
2019-03-13 14:44 ` [PATCH 38/39] drm/i915/execlists: Preempt-to-busy Chris Wilson
2019-03-13 14:44 ` [PATCH 39/39] drm/i915: Remove logical HW ID Chris Wilson
2019-03-13 23:55 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/39] drm/i915: Hold a ref to the ring while retiring Patchwork
2019-03-14  0:12 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-03-14  0:22 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-03-14 18:26 ` ✗ Fi.CI.BAT: failure for series starting with [01/39] drm/i915: Hold a ref to the ring while retiring (rev2) 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=9520c079-691c-dc06-49bf-eefeabe426d4@linux.intel.com \
    --to=tvrtko.ursulin@linux.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.