From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Cc: Intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 05/21] wsim/media-bench: i915 balancing
Date: Mon, 13 May 2019 13:41:47 +0100 [thread overview]
Message-ID: <56b0d138-df0b-0a5b-210e-c1b09f8af609@linux.intel.com> (raw)
In-Reply-To: <155749408753.28545.943075052498428067@skylake-alporthouse-com>
On 10/05/2019 14:14, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-05-08 13:10:42)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Support i915 virtual engine from gem_wsim (-b i915) and media-bench.pl
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> ---
>> + /*
>> + * Create and configure contexts.
>> + */
>> + for (i = 0; i < wrk->nr_ctxs; i += 2) {
>> + struct ctx *ctx = &wrk->ctx_list[i];
>> + uint32_t ctx_id, share_vm = 0;
>>
>> - wrk->ctx_list[w->context].id = arg.ctx_id;
>> + if (ctx->id)
>> + continue;
>>
>> - if (flags & GLOBAL_BALANCE) {
>> - wrk->ctx_list[w->context].static_vcs = context_vcs_rr;
>> - context_vcs_rr ^= 1;
>> - } else {
>> - wrk->ctx_list[w->context].static_vcs = ctx_vcs;
>> - ctx_vcs ^= 1;
>> - }
>> + if (flags & I915) {
>
> vm sharing shouldn't be a i915-balancer only option. For single jobs split
> across multiple contexts, I would expect they will want to share vm.
Could do but I wanted to limit the new features to new features. :)
Pencil in for later okay?
>> + struct drm_i915_gem_context_create_ext_setparam ext = {
>> + .base.name = I915_CONTEXT_CREATE_EXT_SETPARAM,
>> + .param.param = I915_CONTEXT_PARAM_VM,
>> + };
>> + struct drm_i915_gem_context_create_ext args = { };
>>
>> - if (wrk->prio) {
>> + /* Find existing context to share ppgtt with. */
>> + for (j = 0; j < wrk->nr_ctxs; j++) {
>> struct drm_i915_gem_context_param param = {
>> - .ctx_id = arg.ctx_id,
>> - .param = I915_CONTEXT_PARAM_PRIORITY,
>> - .value = wrk->prio,
>> + .param = I915_CONTEXT_PARAM_VM,
>> };
>> - gem_context_set_param(fd, ¶m);
>> +
>> + if (!wrk->ctx_list[j].id)
>> + continue;
>> +
>> + param.ctx_id = wrk->ctx_list[j].id;
>> +
>> + gem_context_get_param(fd, ¶m);
>> + igt_assert(param.value);
>> +
>> + share_vm = param.value;
>> +
>> + ext.param.value = share_vm;
>> + args.flags =
>> + I915_CONTEXT_CREATE_FLAGS_USE_EXTENSIONS;
>> + args.extensions = to_user_pointer(&ext);
>> + break;
>> }
>> +
>> + if (!ctx->targets_instance)
>> + args.flags |=
>> + I915_CONTEXT_CREATE_FLAGS_SINGLE_TIMELINE;
>> +
>> + drmIoctl(fd, DRM_IOCTL_I915_GEM_CONTEXT_CREATE_EXT,
>> + &args);
>> +
>> + ctx_id = args.ctx_id;
>> + } else {
>> + struct drm_i915_gem_context_create args = {};
>> +
>> + drmIoctl(fd, DRM_IOCTL_I915_GEM_CONTEXT_CREATE, &args);
>> + ctx_id = args.ctx_id;
>> + }
>> +
>> + igt_assert(ctx_id);
>> + ctx->id = ctx_id;
>> +
>> + if (flags & GLOBAL_BALANCE) {
>> + ctx->static_vcs = context_vcs_rr;
>> + context_vcs_rr ^= 1;
>> + } else {
>> + ctx->static_vcs = ctx_vcs;
>> + ctx_vcs ^= 1;
>> + }
>> +
>> + __ctx_set_prio(ctx_id, wrk->prio);
>> +
>> + /*
>> + * Do we need a separate context to satisfy this workloads which
>> + * both want to target specific engines and be balanced by i915?
>> + */
>> + if ((flags & I915) && ctx->wants_balance &&
>> + ctx->targets_instance) {
>> + struct drm_i915_gem_context_create_ext_setparam ext = {
>> + .base.name = I915_CONTEXT_CREATE_EXT_SETPARAM,
>> + .param.param = I915_CONTEXT_PARAM_VM,
>> + .param.value = share_vm,
>> + };
>> + struct drm_i915_gem_context_create_ext args = {
>> + .extensions = to_user_pointer(&ext),
>> + .flags =
>> + I915_CONTEXT_CREATE_FLAGS_USE_EXTENSIONS |
>> + I915_CONTEXT_CREATE_FLAGS_SINGLE_TIMELINE,
>> + };
>> +
>> + igt_assert(share_vm);
>> +
>> + drmIoctl(fd, DRM_IOCTL_I915_GEM_CONTEXT_CREATE_EXT,
>> + &args);
>> +
>> + igt_assert(args.ctx_id);
>> + ctx_id = args.ctx_id;
>> + wrk->ctx_list[i + 1].id = args.ctx_id;
>> +
>> + __ctx_set_prio(ctx_id, wrk->prio);
>> + }
>> +
>> + if (ctx->wants_balance) {
>> + I915_DEFINE_CONTEXT_ENGINES_LOAD_BALANCE(load_balance, 2) = {
>> + .base.name = I915_CONTEXT_ENGINES_EXT_LOAD_BALANCE,
>> + .num_siblings = 2,
>> + .engines = {
>> + { .engine_class = I915_ENGINE_CLASS_VIDEO,
>> + .engine_instance = 0 },
>> + { .engine_class = I915_ENGINE_CLASS_VIDEO,
>> + .engine_instance = 1 },
>> + },
>> + };
>> + I915_DEFINE_CONTEXT_PARAM_ENGINES(set_engines, 3) = {
>> + .extensions = to_user_pointer(&load_balance),
>> + .engines = {
>> + { .engine_class = I915_ENGINE_CLASS_INVALID,
>> + .engine_instance = I915_ENGINE_CLASS_INVALID_NONE },
>> + { .engine_class = I915_ENGINE_CLASS_VIDEO,
>> + .engine_instance = 0 },
>> + { .engine_class = I915_ENGINE_CLASS_VIDEO,
>> + .engine_instance = 1 },
>> + },
>> + };
>> +
>> + struct drm_i915_gem_context_param param = {
>> + .ctx_id = ctx_id,
>> + .param = I915_CONTEXT_PARAM_ENGINES,
>> + .size = sizeof(set_engines),
>> + .value = to_user_pointer(&set_engines),
>> + };
>> +
>> + gem_context_set_param(fd, ¶m);
>> }
>
> if (share_vm)
> gem_vm_destroy(share_vm);
>
> Just to drop the local handle as the context has acquired its own
> reference.
Well spotted!
> Other than that, it does what it sets out to do: create a context with
> choice of engines and load balancing amongst them.
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Thanks,
Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-05-13 12:41 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 12:10 [igt-dev] [PATCH i-g-t 00/21] Media scalability tooling Tvrtko Ursulin
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 01/21] scripts/trace.pl: Fix after intel_engine_notify removal Tvrtko Ursulin
2019-05-08 12:17 ` Chris Wilson
2019-05-09 9:27 ` [Intel-gfx] " Tvrtko Ursulin
2019-05-10 12:33 ` Chris Wilson
2019-05-13 12:16 ` Tvrtko Ursulin
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 02/21] headers: bump Tvrtko Ursulin
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 03/21] trace.pl: Virtual engine support Tvrtko Ursulin
2019-05-10 12:52 ` Chris Wilson
2019-05-13 12:30 ` Tvrtko Ursulin
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 04/21] trace.pl: Virtual engine preemption support Tvrtko Ursulin
2019-05-10 12:55 ` [igt-dev] [Intel-gfx] " Chris Wilson
2019-05-13 12:38 ` Tvrtko Ursulin
2019-05-08 12:10 ` [Intel-gfx] [PATCH i-g-t 05/21] wsim/media-bench: i915 balancing Tvrtko Ursulin
2019-05-10 13:14 ` [igt-dev] " Chris Wilson
2019-05-13 12:41 ` Tvrtko Ursulin [this message]
2019-05-13 12:54 ` Chris Wilson
2019-05-10 13:23 ` [Intel-gfx] " Chris Wilson
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 06/21] gem_wsim: Use IGT uapi headers Tvrtko Ursulin
2019-05-10 13:15 ` Chris Wilson
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 07/21] gem_wsim: Factor out common error handling Tvrtko Ursulin
2019-05-10 13:15 ` Chris Wilson
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 08/21] gem_wsim: More wsim_err Tvrtko Ursulin
2019-05-10 13:16 ` [Intel-gfx] " Chris Wilson
2019-05-08 12:10 ` [Intel-gfx] [PATCH i-g-t 09/21] gem_wsim: Submit fence support Tvrtko Ursulin
2019-05-10 13:18 ` [igt-dev] " Chris Wilson
2019-05-08 12:10 ` [Intel-gfx] [PATCH i-g-t 10/21] gem_wsim: Extract str to engine lookup Tvrtko Ursulin
2019-05-10 13:20 ` [igt-dev] " Chris Wilson
2019-05-13 13:08 ` Tvrtko Ursulin
2019-05-08 12:10 ` [Intel-gfx] [PATCH i-g-t 11/21] gem_wsim: Engine map support Tvrtko Ursulin
2019-05-10 13:26 ` [igt-dev] " Chris Wilson
2019-05-13 13:18 ` Tvrtko Ursulin
2019-05-13 13:29 ` Chris Wilson
2019-05-13 13:40 ` Tvrtko Ursulin
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 12/21] gem_wsim: Save some lines by changing to implicit NULL checking Tvrtko Ursulin
2019-05-10 13:28 ` Chris Wilson
2019-05-08 12:10 ` [Intel-gfx] [PATCH i-g-t 13/21] gem_wsim: Compact int command parsing with a macro Tvrtko Ursulin
2019-05-10 13:29 ` [igt-dev] " Chris Wilson
2019-05-13 13:24 ` Tvrtko Ursulin
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 14/21] gem_wsim: Engine map load balance command Tvrtko Ursulin
2019-05-10 13:31 ` Chris Wilson
2019-05-15 11:44 ` Tvrtko Ursulin
2019-05-15 11:48 ` Chris Wilson
2019-05-15 11:55 ` Tvrtko Ursulin
2019-05-08 12:10 ` [Intel-gfx] [PATCH i-g-t 15/21] gem_wsim: Engine bond command Tvrtko Ursulin
2019-05-10 13:36 ` [igt-dev] " Chris Wilson
2019-05-13 13:28 ` Tvrtko Ursulin
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 16/21] gem_wsim: Some more example workloads Tvrtko Ursulin
2019-05-08 12:27 ` Chris Wilson
2019-05-08 13:50 ` Tvrtko Ursulin
2019-05-08 13:56 ` Chris Wilson
2019-05-08 14:16 ` Tvrtko Ursulin
2019-05-10 13:37 ` Chris Wilson
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 17/21] gem_wsim: Infinite batch support Tvrtko Ursulin
2019-05-10 13:48 ` Chris Wilson
2019-05-13 13:59 ` Tvrtko Ursulin
2019-05-13 14:11 ` Chris Wilson
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 18/21] gem_wsim: Command line switch for specifying low slice count workloads Tvrtko Ursulin
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 19/21] gem_wsim: Per context SSEU control Tvrtko Ursulin
2019-05-14 21:53 ` Chris Wilson
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 20/21] gem_wsim: Allow RCS virtual engine with " Tvrtko Ursulin
2019-05-08 12:10 ` [igt-dev] [PATCH i-g-t 21/21] tests/i915_query: Engine discovery tests Tvrtko Ursulin
2019-05-08 12:53 ` [igt-dev] ✓ Fi.CI.BAT: success for Media scalability tooling (rev2) Patchwork
2019-05-08 16:01 ` [igt-dev] ✓ 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=56b0d138-df0b-0a5b-210e-c1b09f8af609@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=tvrtko.ursulin@intel.com \
/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