intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v11 09/10] drm/i915/perf: execute OA configuration from command stream
Date: Thu, 29 Aug 2019 09:58:36 +0300	[thread overview]
Message-ID: <a0fe0f92-6971-e148-998a-8e988259efee@intel.com> (raw)
In-Reply-To: <d60f6253-a9f2-9f50-34b5-f11ea81912b9@intel.com>

On 29/08/2019 09:45, Lionel Landwerlin wrote:
> On 28/08/2019 22:41, Chris Wilson wrote:
>> Quoting Lionel Landwerlin (2019-08-28 15:33:26)
>>> +       rq = i915_request_create(i915->engine[RCS0]->kernel_context);
>>> +       if (IS_ERR(rq))
>>> +               return PTR_ERR(rq);
>>> +
>>> +       err = 
>>> i915_active_request_set(&i915->engine[RCS0]->last_oa_config,
>>> +                                     rq);
>> I am still not sold on putting the global oa_config timeline on the
>> engine, and still dislike the suggestion of using struct_mutex to
>> management it.
>
>
> Where else could we put it?


Note that I should probably move the exclusive_stream on the engine too.

The idea being that this should be attached to the engine where part of 
the OA unit is located.


-Lionel

>
>
>>
>> You will notice that i915_active_request_set() checks that you have the
>> mutex held that your initialised with (in this case that is a *NULL).
>> -Chris
>>
>
> Will fix that, thanks.
>
>
> -Lionel
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx


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

  reply	other threads:[~2019-08-29  6:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 14:33 [PATCH v11 00/10] drm/i915: Vulkan performance query support Lionel Landwerlin
2019-08-28 14:33 ` [PATCH v11 01/10] drm/syncobj: add sideband payload Lionel Landwerlin
2019-08-29  5:26   ` Zhou, David(ChunMing)
2019-08-29  6:40     ` Lionel Landwerlin
2019-09-04 16:08     ` Lionel Landwerlin
2019-08-28 14:33 ` [PATCH v11 02/10] drm/i915: introduce a mechanism to extend execbuf2 Lionel Landwerlin
2019-08-28 14:33 ` [PATCH v11 03/10] drm/i915: add syncobj timeline support Lionel Landwerlin
2019-08-28 14:33 ` [PATCH v11 04/10] drm/i915/perf: introduce a versioning of the i915-perf uapi Lionel Landwerlin
2019-08-28 14:33 ` [PATCH v11 05/10] drm/i915/perf: allow for CS OA configs to be created lazily Lionel Landwerlin
2019-08-29  2:41   ` kbuild test robot
2019-08-28 14:33 ` [PATCH v11 06/10] drm/i915/perf: implement active wait for noa configurations Lionel Landwerlin
2019-08-28 19:34   ` kbuild test robot
2019-08-28 19:39     ` Chris Wilson
2019-08-29  6:43       ` Lionel Landwerlin
2019-08-28 20:00   ` kbuild test robot
2019-08-28 14:33 ` [PATCH v11 07/10] drm/i915: add a new perf configuration execbuf parameter Lionel Landwerlin
2019-08-28 14:33 ` [PATCH v11 08/10] drm/i915/perf: allow holding preemption on filtered ctx Lionel Landwerlin
2019-08-28 14:33 ` [PATCH v11 09/10] drm/i915/perf: execute OA configuration from command stream Lionel Landwerlin
2019-08-28 19:41   ` Chris Wilson
2019-08-29  6:45     ` Lionel Landwerlin
2019-08-29  6:58       ` Lionel Landwerlin [this message]
2019-08-28 14:33 ` [PATCH v11 10/10] drm/i915: add support for perf configuration queries Lionel Landwerlin
2019-08-28 15:58 ` ✗ Fi.CI.BUILD: failure for drm/i915: Vulkan performance query support (rev11) Patchwork
2019-08-29  5:34 ` ✗ Fi.CI.BAT: failure for drm/i915: Vulkan performance query support (rev12) 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=a0fe0f92-6971-e148-998a-8e988259efee@intel.com \
    --to=lionel.g.landwerlin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).