From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [CI 1/9] drm/i915/gt: Show the per-engine runtime in sysfs
Date: Fri, 22 Jan 2021 13:13:05 +0000 [thread overview]
Message-ID: <c7ca37ce-0db5-e273-c2ac-eefcbf75931e@linux.intel.com> (raw)
In-Reply-To: <20210122122903.23893-1-chris@chris-wilson.co.uk>
On 22/01/2021 12:28, Chris Wilson wrote:
> Since we already report the per-engine runtime via PMU (using sampling
> if a direct measure is not available), and in debugfs, also trivially
> include the information for each engine under sysfs as a read-only
> property. We only present the total milliseconds to hide any misleading
> accuracy and to purposely reduce the precision of the global
> unprivileged information.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/sysfs_engines.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/sysfs_engines.c b/drivers/gpu/drm/i915/gt/sysfs_engines.c
> index 967031056202..57ef5383dd4e 100644
> --- a/drivers/gpu/drm/i915/gt/sysfs_engines.c
> +++ b/drivers/gpu/drm/i915/gt/sysfs_engines.c
> @@ -411,6 +411,19 @@ heartbeat_default(struct kobject *kobj, struct kobj_attribute *attr, char *buf)
> static struct kobj_attribute heartbeat_interval_def =
> __ATTR(heartbeat_interval_ms, 0444, heartbeat_default, NULL);
>
> +static ssize_t
> +runtime_show(struct kobject *kobj, struct kobj_attribute *attr, char *buf)
> +{
> + struct intel_engine_cs *engine = kobj_to_engine(kobj);
> + ktime_t dummy;
> +
> + return sprintf(buf, "%llu\n",
> + ktime_to_ms(intel_engine_get_busy_time(engine, &dummy)));
> +}
> +
> +static struct kobj_attribute runtime_attr =
> +__ATTR(runtime_ms, 0444, runtime_show, NULL);
> +
> static void kobj_engine_release(struct kobject *kobj)
> {
> kfree(kobj);
> @@ -521,6 +534,10 @@ void intel_engines_add_sysfs(struct drm_i915_private *i915)
> sysfs_create_file(kobj, &preempt_timeout_attr.attr))
> goto err_engine;
>
> + if (intel_engine_supports_stats(engine) &&
> + sysfs_create_file(kobj, &runtime_attr.attr))
> + goto err_engine;
> +
> add_defaults(container_of(kobj, struct kobj_engine, base));
>
> if (0) {
>
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:[~2021-01-22 13:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 12:28 [Intel-gfx] [CI 1/9] drm/i915/gt: Show the per-engine runtime in sysfs Chris Wilson
2021-01-22 12:28 ` [Intel-gfx] [CI 2/9] drm/i915: Expose list of clients " Chris Wilson
2021-01-22 12:28 ` [Intel-gfx] [CI 3/9] drm/i915: Update client name on context create Chris Wilson
2021-01-22 12:28 ` [Intel-gfx] [CI 4/9] drm/i915: Make GEM contexts track DRM clients Chris Wilson
2021-01-22 12:28 ` [Intel-gfx] [CI 5/9] drm/i915: Track runtime spent in closed and unreachable GEM contexts Chris Wilson
2021-01-22 12:29 ` [Intel-gfx] [CI 6/9] drm/i915: Track all user contexts per client Chris Wilson
2021-01-22 12:29 ` [Intel-gfx] [CI 7/9] drm/i915: Expose per-engine client busyness Chris Wilson
2021-01-22 12:29 ` [Intel-gfx] [CI 8/9] drm/i915: Track context current active time Chris Wilson
2021-01-22 12:29 ` [Intel-gfx] [CI 9/9] drm/i915: Prefer software tracked context busyness Chris Wilson
2021-01-22 13:13 ` Tvrtko Ursulin [this message]
2021-01-22 17:43 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/9] drm/i915/gt: Show the per-engine runtime in sysfs Patchwork
2021-01-22 17:44 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-01-22 18:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-01-23 3:17 ` [Intel-gfx] ✓ 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=c7ca37ce-0db5-e273-c2ac-eefcbf75931e@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