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: Thu, 10 Oct 2019 18:22:25 +0300 [thread overview]
Message-ID: <2b005ce6-97dd-ceee-04aa-72147bfb8e74@intel.com> (raw)
In-Reply-To: <20191009211947.6815-7-chris@chris-wilson.co.uk>
On 10/10/2019 00:19, Chris Wilson wrote:
> From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>
> Introduce a new perf_ioctl command to change the OA configuration of the
> active stream. This allows the OA stream to be reconfigured between
> batch buffers, giving greater flexibility in sampling. We inject a
> request into the OA context to reconfigure the stream asynchronously on
> the GPU in between and ordered with execbuffer calls.
>
> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
So much simpler :)
> ---
> drivers/gpu/drm/i915/i915_perf.c | 34 +++++++++++++++++++++++++++++++-
> include/uapi/drm/i915_drm.h | 10 ++++++++++
> 2 files changed, 43 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
> index 12cc47aece21..3b77db8995f3 100644
> --- a/drivers/gpu/drm/i915/i915_perf.c
> +++ b/drivers/gpu/drm/i915/i915_perf.c
> @@ -2856,6 +2856,28 @@ static void i915_perf_disable_locked(struct i915_perf_stream *stream)
> stream->ops->disable(stream);
> }
>
> +static int i915_perf_config_locked(struct i915_perf_stream *stream,
> + unsigned long metrics_set)
> +{
> + struct i915_oa_config *config;
> + int err = 0;
> +
> + config = i915_perf_get_oa_config(stream->perf, metrics_set);
> + if (!config)
> + return -EINVAL;
> +
> + if (config != stream->oa_config) {
> + if (stream->pinned_ctx)
> + err = emit_oa_config(stream, stream->pinned_ctx);
> + if (err == 0)
> + config = xchg(&stream->oa_config, config);
> + }
> +
> + i915_oa_config_put(config);
> +
> + return err;
> +}
> +
> /**
> * i915_perf_ioctl - support ioctl() usage with i915 perf stream FDs
> * @stream: An i915 perf stream
> @@ -2879,6 +2901,8 @@ static long i915_perf_ioctl_locked(struct i915_perf_stream *stream,
> case I915_PERF_IOCTL_DISABLE:
> i915_perf_disable_locked(stream);
> return 0;
> + case I915_PERF_IOCTL_CONFIG:
> + return i915_perf_config_locked(stream, arg);
For REMOVE_CONFIG we passed a pointer to an u64, not sure whether we
should reuse the same pattern here?
I don't mind the current version.
-Lionel
> }
>
> return -EINVAL;
> @@ -4017,7 +4041,15 @@ void i915_perf_fini(struct drm_i915_private *i915)
> */
> int i915_perf_ioctl_version(void)
> {
> - return 1;
> + /*
> + * 1: Initial version
> + * I915_PERF_IOCTL_ENABLE
> + * I915_PERF_IOCTL_DISABLE
> + *
> + * 2: Added runtime modification of OA config.
> + * I915_PERF_IOCTL_CONFIG
> + */
> + return 2;
> }
>
> #if IS_ENABLED(CONFIG_DRM_I915_SELFTEST)
> diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h
> index 0c7b2815fbf1..5e66f7c60261 100644
> --- a/include/uapi/drm/i915_drm.h
> +++ b/include/uapi/drm/i915_drm.h
> @@ -1932,6 +1932,16 @@ struct drm_i915_perf_open_param {
> */
> #define I915_PERF_IOCTL_DISABLE _IO('i', 0x1)
>
> +/**
> + * Change metrics_set captured by a stream.
> + *
> + * Will not take effect until the stream is restart, or upon the next
> + * execbuf when attached to a specific context.
> + *
> + * This ioctl is available in perf revision 2.
> + */
> +#define I915_PERF_IOCTL_CONFIG _IO('i', 0x2)
> +
> /**
> * Common to all i915 perf records
> */
_______________________________________________
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 15:22 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 [this message]
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
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=2b005ce6-97dd-ceee-04aa-72147bfb8e74@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