From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/execlists: Assign virtual_engine->uncore from first sibling
Date: Tue, 8 Oct 2019 10:13:23 +0100 [thread overview]
Message-ID: <3baadc0e-b0ce-e4ca-eb4a-3695d90da1db@linux.intel.com> (raw)
In-Reply-To: <20191008070342.4045-1-chris@chris-wilson.co.uk>
On 08/10/2019 08:03, Chris Wilson wrote:
> Copy across the engine->uncore shortcut to the virtual_engine from its
> first physical engine, similar to the handling of the engine->gt
> backpointer.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/gt/intel_lrc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> index 432b8b60c4c0..6db762c509b8 100644
> --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> @@ -4170,6 +4170,7 @@ intel_execlists_create_virtual(struct i915_gem_context *ctx,
>
> ve->base.i915 = ctx->i915;
> ve->base.gt = siblings[0]->gt;
> + ve->base.uncore = siblings[0]->uncore;
> ve->base.id = -1;
> ve->base.class = OTHER_CLASS;
> ve->base.uabi_class = I915_ENGINE_CLASS_INVALID;
>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
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-08 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 7:03 [PATCH] drm/i915/execlists: Assign virtual_engine->uncore from first sibling Chris Wilson
2019-10-08 8:38 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-10-08 9:13 ` Tvrtko Ursulin [this message]
2019-10-08 10:48 ` ✗ Fi.CI.IGT: failure " 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=3baadc0e-b0ce-e4ca-eb4a-3695d90da1db@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox