From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v4 2/3] drm/i915/perf: prepare driver to receive multiple ctx handles
Date: Tue, 7 Apr 2020 19:43:28 +0300 [thread overview]
Message-ID: <799ed671-d5de-7602-b01a-f44e94212d3b@intel.com> (raw)
In-Reply-To: <158627655632.8918.7532038582567584503@build.alporthouse.com>
On 07/04/2020 19:22, Chris Wilson wrote:
> Quoting Lionel Landwerlin (2020-04-07 13:35:39)
>> -static struct intel_context *oa_context(struct i915_perf_stream *stream)
>> -{
>> - return stream->pinned_ctx ?: stream->engine->kernel_context;
>> -}
> Idle thought: create a
>
> stream->context = intel_context_create(stream->engine);
>
> so I can stop worrying about the kernel_context. (What's the cost of one
> more context, heh?)
> -Chris
Sure :)
-Lionel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-04-07 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 12:35 [Intel-gfx] [PATCH v4 1/3] drm/i915/perf: break OA config buffer object in 2 Lionel Landwerlin
2020-04-07 12:35 ` [Intel-gfx] [PATCH v4 2/3] drm/i915/perf: prepare driver to receive multiple ctx handles Lionel Landwerlin
2020-04-07 16:22 ` Chris Wilson
2020-04-07 16:43 ` Lionel Landwerlin [this message]
2020-04-08 13:01 ` Lionel Landwerlin
2020-04-07 12:35 ` [Intel-gfx] [PATCH v4 3/3] drm/i915/perf: enable filtering on multiple contexts Lionel Landwerlin
2020-04-07 14:58 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [v4,1/3] drm/i915/perf: break OA config buffer object in 2 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=799ed671-d5de-7602-b01a-f44e94212d3b@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