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 4/5] drm/i915: Expose RPCS (SSEU) configuration to userspace (Gen11 only)
Date: Wed, 30 Jan 2019 09:59:41 +0000	[thread overview]
Message-ID: <9c035028-14cf-0d18-ab90-400e273da7f1@linux.intel.com> (raw)
In-Reply-To: <154884154934.21797.10897784414372879426@skylake-alporthouse-com>


On 30/01/2019 09:45, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-01-30 09:34:15)
>> +       rq = i915_request_alloc(engine, i915->kernel_context);
>> +       if (IS_ERR(rq)) {
>> +               ret = PTR_ERR(rq);
>> +               goto out_put;
>> +       }
>> +
>> +       /* Queue this switch after all other activity by this context. */
>> +       prev = i915_gem_active_raw(&ce->ring->timeline->last_request,
>> +                                  &i915->drm.struct_mutex);
>> +       if (prev && !i915_request_completed(prev)) {
>> +               ret = i915_request_await_dma_fence(rq, &prev->fence);
>> +               if (ret < 0)
>> +                       goto out_add;
>> +       }
>> +
>> +       ret = gen8_emit_rpcs_config(rq, ce, sseu);
>> +       if (ret)
>> +               goto out_add;
>> +
>> +       /* Order all following requests to be after. */
>> +       i915_timeline_set_barrier(ce->ring->timeline, rq);
> 
> You are making me regret not adding __must_check everywhere.
> 
> If you set the barrier before the emit_rpcs_config, then as we maintain
> barrier ordering, it will be ok if we have to not emit the config
> change.

Ah rings a bell.. forgot about it..

Regards,

Tvrtko

> 
>> +
>> +       /*
>> +        * Guarantee context image and the timeline remains pinned until the
>> +        * modifying request is retired by setting the ce activity tracker.
>> +        *
>> +        * But we only need to take one pin on the account of it. Or in other
>> +        * words transfer the pinned ce object to tracked active request.
>> +        */
>> +       if (!i915_gem_active_isset(&ce->active_tracker))
>> +               __intel_context_pin(ce);
>> +       i915_gem_active_set(&ce->active_tracker, rq);
> 
> Hello ce->active_tracker, I have great plans for you.
> -Chris
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-01-30  9:59 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30  9:34 [PATCH 0/5] Per context dynamic (sub)slice power-gating Tvrtko Ursulin
2019-01-30  9:34 ` [PATCH 1/5] drm/i915: Record the sseu configuration per-context & engine Tvrtko Ursulin
2019-01-30  9:40   ` Chris Wilson
2019-01-30  9:56     ` Tvrtko Ursulin
2019-01-30 10:14   ` [PATCH v16 " Tvrtko Ursulin
2019-01-30  9:34 ` [PATCH 2/5] drm/i915/perf: lock powergating configuration to default when active Tvrtko Ursulin
2019-01-30  9:34 ` [PATCH 3/5] drm/i915: Add timeline barrier support Tvrtko Ursulin
2019-01-30  9:34 ` [PATCH 4/5] drm/i915: Expose RPCS (SSEU) configuration to userspace (Gen11 only) Tvrtko Ursulin
2019-01-30  9:45   ` Chris Wilson
2019-01-30  9:59     ` Tvrtko Ursulin [this message]
2019-01-30 10:15   ` [PATCH v29 " Tvrtko Ursulin
2019-01-31  8:47     ` [PATCH v30 " Tvrtko Ursulin
2019-01-31  9:15       ` Chris Wilson
2019-01-31  9:34         ` Tvrtko Ursulin
2019-01-31 10:47       ` [PATCH v31 " Tvrtko Ursulin
2019-01-31 10:59         ` Chris Wilson
2019-01-31 11:46         ` Joonas Lahtinen
2019-01-30  9:34 ` [PATCH 5/5] drm/i915/selftests: Context SSEU reconfiguration tests Tvrtko Ursulin
2019-01-30  9:47 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev21) Patchwork
2019-01-30  9:50 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-30 10:12 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-30 11:12 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev23) Patchwork
2019-01-30 11:15 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-30 11:31 ` ✗ Fi.CI.IGT: failure for Per context dynamic (sub)slice power-gating (rev21) Patchwork
2019-01-30 11:45 ` ✓ Fi.CI.BAT: success for Per context dynamic (sub)slice power-gating (rev23) Patchwork
2019-01-30 13:12 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev24) Patchwork
2019-01-30 13:15 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-30 13:34 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-30 13:52 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev25) Patchwork
2019-01-30 13:55 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-30 14:14 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-01-30 16:23 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev26) Patchwork
2019-01-30 16:26 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-30 16:45 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-30 20:51 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-31  7:25   ` Tvrtko Ursulin
2019-01-31  7:30     ` Chris Wilson
2019-01-31  8:26 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev27) Patchwork
2019-01-31  8:29 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-31  8:48 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-31  9:49 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev28) Patchwork
2019-01-31  9:51 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-31 10:14 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-31 11:11 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev29) Patchwork
2019-01-31 11:14 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-31 11:32 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-31 21:49 ` ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2019-01-25 15:24 [PATCH 0/5] Per context dynamic (sub)slice power-gating Tvrtko Ursulin
2019-01-25 15:24 ` [PATCH 4/5] drm/i915: Expose RPCS (SSEU) configuration to userspace (Gen11 only) Tvrtko Ursulin
2019-01-26 10:57   ` Chris Wilson

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=9c035028-14cf-0d18-ab90-400e273da7f1@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    /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.