From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 7/9] drm/i915/perf: Allow dynamic reconfiguration of the OA stream
Date: Fri, 11 Oct 2019 00:08:23 +0300 [thread overview]
Message-ID: <3aefde94-4dfd-ea9f-9d88-be7d7f858baa@intel.com> (raw)
In-Reply-To: <157073703290.31572.10913483979759707139@skylake-alporthouse-com>
On 10/10/2019 22:50, Chris Wilson wrote:
> Quoting Lionel Landwerlin (2019-10-10 17:07:11)
>> Yeah, that's a fine interface actually.
> One last thought for the interface, should we return the previous
> config-id?
>
> That limits the config-id space to long (min s32) so that we can report
> the negative error code (or exclude the top 4095 values).
> -Chris
>
No real use for it at the moment. I leave this up to your uAPI designer
experience :)
-Lionel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-10-10 21:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 21:19 [PATCH 1/9] drm/i915/perf: store the associated engine of a stream Chris Wilson
2019-10-09 21:19 ` [PATCH 2/9] drm/i915/perf: introduce a versioning of the i915-perf uapi Chris Wilson
2019-10-09 21:19 ` [PATCH 3/9] drm/i915/perf: allow for CS OA configs to be created lazily Chris Wilson
2019-10-09 21:19 ` [PATCH 4/9] drm/i915: add support for perf configuration queries Chris Wilson
2019-10-09 21:19 ` [PATCH 5/9] drm/i915/perf: implement active wait for noa configurations Chris Wilson
2019-10-09 21:19 ` [PATCH 6/9] drm/i915/perf: execute OA configuration from command stream Chris Wilson
2019-10-09 21:19 ` [PATCH 7/9] drm/i915/perf: Allow dynamic reconfiguration of the OA stream Chris Wilson
2019-10-10 15:22 ` Lionel Landwerlin
2019-10-10 15:44 ` Chris Wilson
[not found] ` <8e58da7d-9ec9-4225-3e24-d7e6665d8a17@intel.com>
2019-10-10 19:50 ` Chris Wilson
2019-10-10 21:08 ` Lionel Landwerlin [this message]
2019-10-09 21:19 ` [PATCH 8/9] drm/i915/perf: allow holding preemption on filtered ctx Chris Wilson
2019-10-09 21:19 ` [PATCH 9/9] drm/i915/execlists: Prevent merging requests with conflicting flags Chris Wilson
2019-10-10 16:09 ` Lionel Landwerlin
2019-10-10 0:07 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/9] drm/i915/perf: store the associated engine of a stream Patchwork
2019-10-10 0:34 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-10 10:25 ` ✓ Fi.CI.IGT: " 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=3aefde94-4dfd-ea9f-9d88-be7d7f858baa@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