Per-context and per-client engine busyness
Subsystems (3)
Tvrtko Ursulin
maintainercover Per-context and per-client engine busyness
From: Tvrtko Ursulin <[email protected]>
Lightly tested (apart from patch 13) series to start the discussion early.
Please skip patches 1-9, and probably 10-11 as well, those ones are the current PMU effort which is yet unmerged but needed as a basis for patches 12-17.
Customer ask is to allow clients to query how much GPU engine time they are using per context.
In patch 12 I add this, and then patch 13 I expose it via the context get param. (It feels like a slight misuse of get param though.)
Patches 14-17 are not a customer ask as far as I know, but something I thought would be pretty cool. Basically bringing the ability to write a CPU top-like utility for GPU tasks.
I've prototyped a quick demo of intel-client-top which produces output like:
neverball[ 6011]: rcs0: 41.01% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%
Xorg[ 5664]: rcs0: 31.16% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%
xfwm4[ 5727]: rcs0: 0.00% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%As I say in the commit we could also extend this to show the overall engine busyness (via PMU), and also average load as queue-depth (also PMU), in the top header.
Another potential use for the per-client infrastructure is tieing it up with perf PMU. At the moment our perf PMU are global counters only. With the per- client infrastructure it should be possible to make it work in the task mode as well and so enable GPU busyness profiling of single tasks.
But this last part is not in this series, at least not yet.
Tvrtko Ursulin (17):
drm/i915: Extract intel_get_cagf
drm/i915/pmu: Expose a PMU interface for perf queries drm/i915/pmu: Suspend sampling when GPU is idle drm/i915: Wrap context schedule notification drm/i915: Engine busy time tracking
drm/i915/pmu: Wire up engine busy stats to PMU drm/i915/pmu: Add interrupt count metric
drm/i915: Convert intel_rc6_residency_us to ns drm/i915/pmu: Add RC6 residency metrics
drm/i915: Keep a count of requests waiting for a slot on GPU drm/i915/pmu: Add queued counter
drm/i915: Track per-context engine busyness drm/i915: Allow clients to query own per-engine busyness drm/i915: Expose list of clients in sysfs drm/i915: Update client name on context create drm/i915: Expose per-engine client busyness drm/i915: Add sysfs toggle to enable per-client engine stats
drivers/gpu/drm/i915/Makefile | 1 + drivers/gpu/drm/i915/i915_debugfs.c | 9 +- drivers/gpu/drm/i915/i915_drv.c | 3 + drivers/gpu/drm/i915/i915_drv.h | 39 +- drivers/gpu/drm/i915/i915_gem.c | 178 ++++++- drivers/gpu/drm/i915/i915_gem_context.c | 49 +- drivers/gpu/drm/i915/i915_gem_context.h | 5 + drivers/gpu/drm/i915/i915_gem_request.c | 6 + drivers/gpu/drm/i915/i915_pmu.c | 904 ++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/i915_pmu.h | 112 ++++ drivers/gpu/drm/i915/i915_reg.h | 3 + drivers/gpu/drm/i915/i915_sysfs.c | 99 +++- drivers/gpu/drm/i915/intel_engine_cs.c | 128 ++++- drivers/gpu/drm/i915/intel_lrc.c | 25 +- drivers/gpu/drm/i915/intel_pm.c | 41 +- drivers/gpu/drm/i915/intel_ringbuffer.h | 167 ++++++ include/uapi/drm/i915_drm.h | 69 ++- 17 files changed, 1788 insertions(+), 50 deletions(-) create mode 100644 drivers/gpu/drm/i915/i915_pmu.c create mode 100644 drivers/gpu/drm/i915/i915_pmu.h
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 1/17 drm/i915: Extract intel_get_cagf
From: Tvrtko Ursulin <[email protected]>
Code to be shared between debugfs and the PMU implementation.
v2: Checkpatch cleanup.
v3: Also consolidate i915_sysfs.c/gt_act_freq_mhz_show.
v4: Rebase.
--- drivers/gpu/drm/i915/i915_debugfs.c | 9 ++------- drivers/gpu/drm/i915/i915_drv.h | 2 ++ drivers/gpu/drm/i915/i915_sysfs.c | 11 +++-------- drivers/gpu/drm/i915/intel_pm.c | 14 ++++++++++++++ 4 files changed, 21 insertions(+), 15 deletions(-)
drivers/gpu/drm/i915/i915_debugfs.c +2 -7
@@ -1151,13 +1151,8 @@ static int i915_frequency_info(struct seq_file *m, void *unused) rpdownei =I915_READ (GEN6_RP_CUR_DOWN_EI ) &GEN6_CURIAVG_MASK ; rpcurdown =I915_READ (GEN6_RP_CUR_DOWN ) &GEN6_CURBSYTAVG_MASK ; rpprevdown =I915_READ (GEN6_RP_PREV_DOWN ) &GEN6_CURBSYTAVG_MASK ; -if (INTEL_GEN (dev_priv) >=9 ) - cagf = (rpstat &GEN9_CAGF_MASK ) >>GEN9_CAGF_SHIFT ; -else if (IS_HASWELL (dev_priv) ||IS_BROADWELL (dev_priv)) - cagf = (rpstat &HSW_CAGF_MASK ) >>HSW_CAGF_SHIFT ; -else - cagf = (rpstat &GEN6_CAGF_MASK ) >>GEN6_CAGF_SHIFT ; - cagf =intel_gpu_freq (dev_priv, cagf); + cagf =intel_gpu_freq (dev_priv, +intel_get_cagf (dev_priv, rpstat));intel_uncore_forcewake_put (dev_priv,FORCEWAKE_ALL );
drivers/gpu/drm/i915/i915_drv.h +2 -0
@@ -4202,6 +4202,8 @@ int intel_freq_opcode(struct drm_i915_private *dev_priv, int val);u64 intel_rc6_residency_us (struct drm_i915_private *dev_priv,const i915_reg_t reg); +u32 intel_get_cagf (struct drm_i915_private *dev_priv,u32 rpstat1); +#define I915_READ8 (reg) dev_priv->uncore.funcs.mmio_readb(dev_priv, (reg), true)#define I915_WRITE8 (reg, val) dev_priv->uncore.funcs.mmio_writeb(dev_priv, (reg), (val), true)
drivers/gpu/drm/i915/i915_sysfs.c +3 -8
@@ -252,14 +252,9 @@ static ssize_t gt_act_freq_mhz_show(struct device *kdev, freq =vlv_punit_read (dev_priv,PUNIT_REG_GPU_FREQ_STS ); ret =intel_gpu_freq (dev_priv, (freq >>8 ) &0xff ); }else { -u32 rpstat =I915_READ (GEN6_RPSTAT1 ); -if (INTEL_GEN (dev_priv) >=9 ) - ret = (rpstat &GEN9_CAGF_MASK ) >>GEN9_CAGF_SHIFT ; -else if (IS_HASWELL (dev_priv) ||IS_BROADWELL (dev_priv)) - ret = (rpstat &HSW_CAGF_MASK ) >>HSW_CAGF_SHIFT ; -else - ret = (rpstat &GEN6_CAGF_MASK ) >>GEN6_CAGF_SHIFT ; - ret =intel_gpu_freq (dev_priv, ret); + ret =intel_gpu_freq (dev_priv, +intel_get_cagf (dev_priv, +I915_READ (GEN6_RPSTAT1 ))); }mutex_unlock (&dev_priv->pcu_lock);
drivers/gpu/drm/i915/intel_pm.c +14 -0
@@ -9530,3 +9530,17 @@ u64 intel_rc6_residency_us(struct drm_i915_private *dev_priv,intel_runtime_pm_put (dev_priv);return DIV_ROUND_UP_ULL (time_hw * units, div); } + +u32 intel_get_cagf (struct drm_i915_private *dev_priv,u32 rpstat) +{ +u32 cagf; + +if (INTEL_GEN (dev_priv) >=9 ) + cagf = (rpstat &GEN9_CAGF_MASK ) >>GEN9_CAGF_SHIFT ; +else if (IS_HASWELL (dev_priv) ||IS_BROADWELL (dev_priv)) + cagf = (rpstat &HSW_CAGF_MASK ) >>HSW_CAGF_SHIFT ; +else + cagf = (rpstat &GEN6_CAGF_MASK ) >>GEN6_CAGF_SHIFT ; + +return cagf; +}
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 2/17 drm/i915/pmu: Expose a PMU interface for perf queries
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
From: Chris Wilson <[email protected]>
From: Tvrtko Ursulin <[email protected]>
From: Dmitry Rogozhkin <[email protected]>
The first goal is to be able to measure GPU (and invidual ring) busyness without having to poll registers from userspace. (Which not only incurs holding the forcewake lock indefinitely, perturbing the system, but also runs the risk of hanging the machine.) As an alternative we can use the perf event counter interface to sample the ring registers periodically and send those results to userspace.
Functionality we are exporting to userspace is via the existing perf PMU API and can be exercised via the existing tools. For example:
perf stat -a -e i915/rcs0-busy/ -I 1000
Will print the render engine busynnes once per second. All the performance counters can be enumerated (perf list) and have their unit of measure correctly reported in sysfs.
v1-v2 (Chris Wilson):
v2: Use a common timer for the ring sampling.
v3: (Tvrtko Ursulin)
* Decouple uAPI from i915 engine ids.
* Complete uAPI defines.
* Refactor some code to helpers for clarity.
* Skip sampling disabled engines.
* Expose counters in sysfs.
* Pass in fake regs to avoid null ptr deref in perf core.
* Convert to class/instance uAPI.
* Use shared driver code for rc6 residency, power and frequency.
v4: (Dmitry Rogozhkin)
* Register PMU with .task_ctx_nr=perf_invalid_context
* Expose cpumask for the PMU with the single CPU in the mask
* Properly support pmu->stop(): it should call pmu->read()
* Properly support pmu->del(): it should call stop(event, PERF_EF_UPDATE)
* Introduce refcounting of event subscriptions.
* Make pmu.busy_stats a refcounter to avoid busy stats going away with some deleted event.
* Expose cpumask for i915 PMU to avoid multiple events creation of the same type followed by counter aggregation by perf-stat.
* Track CPUs getting online/offline to migrate perf context. If (likely) cpumask will initially set CPU0, CONFIG_BOOTPARAM_HOTPLUG_CPU0 will be needed to see effect of CPU status tracking.
* End result is that only global events are supported and perf stat works correctly.
* Deny perf driver level sampling - it is prohibited for uncore PMU.
v5: (Tvrtko Ursulin)
* Don't hardcode number of engine samplers.
* Rewrite event ref-counting for correctness and simplicity.
* Store initial counter value when starting already enabled events to correctly report values to all listeners.
* Fix RC6 residency readout.
* Comments, GPL header.
v6:
* Add missing entry to v4 changelog.
* Fix accounting in CPU hotplug case by copying the approach from arch/x86/events/intel/cstate.c. (Dmitry Rogozhkin)
v7:
* Log failure message only on failure.
* Remove CPU hotplug notification state on unregister.
v8:
* Fix error unwind on failed registration.
* Checkpatch cleanup.
v9:
* Drop the energy metric, it is available via intel_rapl_perf. (Ville Syrjälä)
* Use HAS_RC6(p). (Chris Wilson)
* Handle unsupported non-engine events. (Dmitry Rogozhkin)
* Rebase for intel_rc6_residency_ns needing caller managed runtime pm.
* Drop HAS_RC6 checks from the read callback since creating those events will be rejected at init time already.
* Add counter units to sysfs so perf stat output is nicer.
* Cleanup the attribute tables for brevity and readability.
v10:
* Fixed queued accounting.
v11:
* Move intel_engine_lookup_user to intel_engine_cs.c
* Commit update. (Joonas Lahtinen)
v12:
* More accurate sampling. (Chris Wilson)
* Store and report frequency in MHz for better usability from perf stat.
* Removed metrics: queued, interrupts, rc6 counters.
* Sample engine busyness based on seqno difference only for less MMIO (and forcewake) on all platforms. (Chris Wilson)
v13:
* Comment spelling, use mul_u32_u32 to work around potential GCC issue and somne code alignment changes. (Chris Wilson)
v14:
* Rebase.
v15:
* Rebase for RPS refactoring.
v16:
* Use the dynamic slot in the CPU hotplug state machine so that we are free to setup our state as multi-instance. Previously we were re-using the CPUHP_AP_PERF_X86_UNCORE_ONLINE slot which is neither used as multi-instance, nor owned by our driver to start with.
* Register the CPU hotplug handlers after the PMU, otherwise the callback will get called before the PMU is initialized which can end up in perf_pmu_migrate_context with an un-initialized base.
* Added workaround for a probable bug in cpuhp core.
v17:
* Remove workaround for the cpuhp bug.
--- drivers/gpu/drm/i915/Makefile | 1 + drivers/gpu/drm/i915/i915_drv.c | 3 + drivers/gpu/drm/i915/i915_drv.h | 5 + drivers/gpu/drm/i915/i915_pmu.c | 688 ++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/i915_pmu.h | 104 +++++ drivers/gpu/drm/i915/i915_reg.h | 3 + drivers/gpu/drm/i915/intel_engine_cs.c | 35 ++ drivers/gpu/drm/i915/intel_ringbuffer.h | 26 ++ include/uapi/drm/i915_drm.h | 48 +++ 9 files changed, 913 insertions(+) create mode 100644 drivers/gpu/drm/i915/i915_pmu.c create mode 100644 drivers/gpu/drm/i915/i915_pmu.h
drivers/gpu/drm/i915/Makefile +1 -0
@@ -26,6 +26,7 @@ i915-y := i915_drv.o \ i915-$(CONFIG_COMPAT) += i915_ioc32.o i915-$(CONFIG_DEBUG_FS) += i915_debugfs.o intel_pipe_crc.o +i915-$(CONFIG_PERF_EVENTS) += i915_pmu.o # GEM code i915-y += i915_cmd_parser.o \
drivers/gpu/drm/i915/i915_drv.c +3 -0
@@ -48,6 +48,7 @@#include "i915_drv.h" #include "i915_trace.h" +#include "i915_pmu.h" #include "i915_vgpu.h" #include "intel_drv.h" #include "intel_uc.h"
@@ -1216,6 +1217,7 @@ static void i915_driver_register(struct drm_i915_private *dev_priv)struct drm_device *dev = &dev_priv->drm;i915_gem_shrinker_init (dev_priv); +i915_pmu_register (dev_priv);/* * Notify a valid surface after modesetting,
@@ -1270,6 +1272,7 @@ static void i915_driver_unregister(struct drm_i915_private *dev_priv)intel_opregion_unregister (dev_priv);i915_perf_unregister (dev_priv); +i915_pmu_unregister (dev_priv);i915_teardown_sysfs (dev_priv);i915_guc_log_unregister (dev_priv);
drivers/gpu/drm/i915/i915_drv.h +5 -0
@@ -40,6 +40,7 @@#include <linux/hash.h> #include <linux/intel-iommu.h> #include <linux/kref.h> +#include <linux/perf_event.h> #include <linux/pm_qos.h> #include <linux/reservation.h> #include <linux/shmem_fs.h>
@@ -2281,6 +2282,8 @@ struct drm_i915_private {struct i915_gem_context *kernel_context;/* Context only to be used for injecting preemption commands */ struct i915_gem_context *preempt_context; +struct intel_engine_cs *engine_class[MAX_ENGINE_CLASS +1 ] + [MAX_ENGINE_INSTANCE +1 ];struct i915_vma *semaphore;struct drm_dma_handle *status_page_dmah;
@@ -2751,6 +2754,8 @@ struct drm_i915_private {int irq; } lpe_audio; +struct i915_pmu pmu; +/* * NOTE: This is the dri1/ums dungeon, don't add stuff here. Your patch * will be rejected. Instead look for a better place.
drivers/gpu/drm/i915/i915_pmu.c new file +688 -0
688 lines not on this page · raw message
drivers/gpu/drm/i915/i915_pmu.h new file +104 -0
104 lines not on this page · raw message
drivers/gpu/drm/i915/i915_reg.h +3 -0
@@ -186,6 +186,9 @@ static inline bool i915_mmio_reg_valid(i915_reg_t reg)#define VIDEO_ENHANCEMENT_CLASS 2#define COPY_ENGINE_CLASS 3#define OTHER_CLASS 4 +#define MAX_ENGINE_CLASS 4 + +#define MAX_ENGINE_INSTANCE 1/* PCI config space */
drivers/gpu/drm/i915/intel_engine_cs.c +35 -0
@@ -203,6 +203,15 @@ intel_engine_setup(struct drm_i915_private *dev_priv,GEM_BUG_ON (info->class >=ARRAY_SIZE (intel_engine_classes)); class_info = &intel_engine_classes[info->class]; +if (GEM_WARN_ON (info->class >MAX_ENGINE_CLASS )) +return -EINVAL ; + +if (GEM_WARN_ON (info->instance >MAX_ENGINE_INSTANCE )) +return -EINVAL ; + +if (GEM_WARN_ON (dev_priv->engine_class[info->class][info->instance])) +return -EINVAL ; +GEM_BUG_ON (dev_priv->engine[id]); engine =kzalloc (sizeof (*engine),GFP_KERNEL );if (!engine)
@@ -230,6 +239,7 @@ intel_engine_setup(struct drm_i915_private *dev_priv,ATOMIC_INIT_NOTIFIER_HEAD (&engine->context_status_notifier); + dev_priv->engine_class[info->class][info->instance] = engine; dev_priv->engine[id] = engine;return 0 ; }
@@ -1784,6 +1794,31 @@ void intel_engine_dump(struct intel_engine_cs *engine, struct drm_printer *m)drm_printf (m,"\n" ); } +static u8 user_class_map[I915_ENGINE_CLASS_MAX ] = { + [I915_ENGINE_CLASS_OTHER ] =OTHER_CLASS , + [I915_ENGINE_CLASS_RENDER ] =RENDER_CLASS , + [I915_ENGINE_CLASS_COPY ] =COPY_ENGINE_CLASS , + [I915_ENGINE_CLASS_VIDEO ] =VIDEO_DECODE_CLASS , + [I915_ENGINE_CLASS_VIDEO_ENHANCE ] =VIDEO_ENHANCEMENT_CLASS , +}; + +struct intel_engine_cs * +intel_engine_lookup_user (struct drm_i915_private *i915,u8 class,u8 instance) +{ +if (class >=ARRAY_SIZE (user_class_map)) +return NULL ; + + class = user_class_map[class]; + +if (WARN_ON_ONCE (class >MAX_ENGINE_CLASS )) +return NULL ; + +if (instance >MAX_ENGINE_INSTANCE ) +return NULL ; + +return i915->engine_class[class][instance]; +} +#if IS_ENABLED (CONFIG_DRM_I915_SELFTEST )#include "selftests/mock_engine.c" #endif
drivers/gpu/drm/i915/intel_ringbuffer.h +26 -0
@@ -5,6 +5,7 @@#include "i915_gem_batch_pool.h" #include "i915_gem_request.h" #include "i915_gem_timeline.h" +#include "i915_pmu.h" #include "i915_selftest.h" struct drm_printer ;
@@ -345,6 +346,28 @@ struct intel_engine_cs { I915_SELFTEST_DECLARE(bool mock : 1); } breadcrumbs; +struct { +/** +* @enable: Bitmask of enable sample events on this engine. +* +* Bits correspond to sample event types, for instance +* I915_SAMPLE_QUEUED is bit 0 etc. +*/ +u32 enable; +/** +* @enable_count: Reference count for the enabled samplers. +* +* Index number corresponds to the bit number from @enable. +*/ +unsigned int enable_count[I915_PMU_SAMPLE_BITS ]; +/** +* @sample: Counter values for sampling events. +* +* Our internal timer stores the current counters in this field. +*/ +struct i915_pmu_sample sample[I915_ENGINE_SAMPLE_MAX ]; + } pmu; +/* * A pool of objects to use as shadow copies of client batch buffers * when the command parser is enabled. Prevents the client from
@@ -873,4 +896,7 @@ bool intel_engine_can_store_dword(struct intel_engine_cs *engine);void intel_engine_dump (struct intel_engine_cs *engine,struct drm_printer *p); +struct intel_engine_cs * +intel_engine_lookup_user (struct drm_i915_private *i915,u8 class,u8 instance); +#endif /* _INTEL_RINGBUFFER_H_ */
include/uapi/drm/i915_drm.h +48 -0
54 lines not on this page · raw message
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 3/17 drm/i915/pmu: Suspend sampling when GPU is idle
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
If only a subset of events is enabled we can afford to suspend the sampling timer when the GPU is idle and so save some cycles and power.
v2: Rebase and limit timer even more.
v3: Rebase.
v4: Rebase.
v5: Skip action if perf PMU failed to register.
v6: Checkpatch cleanup.
v7:
* Add a common helper to start the timer if needed. (Chris Wilson)
* Add comment explaining bitwise logic in pmu_needs_timer.
v8: Fix some comments styles. (Chris Wilson)
v9: Rebase.
v10: Move function declarations to i915_pmu.h.
--- drivers/gpu/drm/i915/i915_gem.c | 1 + drivers/gpu/drm/i915/i915_gem_request.c | 1 + drivers/gpu/drm/i915/i915_pmu.c | 88 +++++++++++++++++++++++++++++---- drivers/gpu/drm/i915/i915_pmu.h | 8 +++ 4 files changed, 88 insertions(+), 10 deletions(-)
drivers/gpu/drm/i915/i915_gem.c +1 -0
@@ -3349,6 +3349,7 @@ i915_gem_idle_work_handler(struct work_struct *work)intel_engines_mark_idle (dev_priv);i915_gem_timelines_mark_idle (dev_priv); +i915_pmu_gt_idle (dev_priv);GEM_BUG_ON (!dev_priv->gt.awake); dev_priv->gt.awake = false;
drivers/gpu/drm/i915/i915_gem_request.c +1 -0
@@ -258,6 +258,7 @@ static void mark_busy(struct drm_i915_private *i915)i915_update_gfx_val (i915);if (INTEL_GEN (i915) >=6 )gen6_rps_busy (i915); +i915_pmu_gt_active (i915); queue_delayed_work(i915->wq, &i915->gt.retire_work,
drivers/gpu/drm/i915/i915_pmu.c +78 -10
119 lines not on this page · raw message
drivers/gpu/drm/i915/i915_pmu.h +8 -0
@@ -83,6 +83,10 @@ struct i915_pmu {*/ unsigned int enable_count[I915_PMU_MASK_BITS ];/** +* @timer_enabled: Should the internal sampling timer be running. +*/ +bool timer_enabled; +/** * @sample: Current and previous (raw) counters for sampling events. * * These counters are updated from the i915 PMU sampling timer.
@@ -96,9 +100,13 @@ struct i915_pmu {#ifdef CONFIG_PERF_EVENTS void i915_pmu_register (struct drm_i915_private *i915);void i915_pmu_unregister (struct drm_i915_private *i915); +void i915_pmu_gt_idle (struct drm_i915_private *i915); +void i915_pmu_gt_active (struct drm_i915_private *i915);#else static inline void i915_pmu_register (struct drm_i915_private *i915) {}static inline void i915_pmu_unregister (struct drm_i915_private *i915) {} +static inline void i915_pmu_gt_idle (struct drm_i915_private *i915) {} +static inline void i915_pmu_gt_active (struct drm_i915_private *i915) {}#endif #endif
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 4/17 drm/i915: Wrap context schedule notification
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
No functional change just something which will be handy in the following patch.
--- drivers/gpu/drm/i915/intel_lrc.c | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/intel_lrc.c +14 -3
@@ -400,6 +400,18 @@ execlists_context_status_change(struct drm_i915_gem_request *rq, status, rq); } +static inline void +execlists_context_schedule_in (struct drm_i915_gem_request *rq) +{ +execlists_context_status_change (rq,INTEL_CONTEXT_SCHEDULE_IN ); +} + +static inline void +execlists_context_schedule_out (struct drm_i915_gem_request *rq) +{ +execlists_context_status_change (rq,INTEL_CONTEXT_SCHEDULE_OUT ); +} +static void execlists_update_context_pdps (struct i915_hw_ppgtt *ppgtt,u32 *reg_state) {
@@ -451,7 +463,7 @@ static void execlists_submit_ports(struct intel_engine_cs *engine)if (rq) {GEM_BUG_ON (count > !n);if (!count++) -execlists_context_status_change (rq,INTEL_CONTEXT_SCHEDULE_IN ); +execlists_context_schedule_in (rq);port_set (&port[n],port_pack (rq, count)); desc =execlists_update_context (rq);GEM_DEBUG_EXEC (port[n].context_id =upper_32_bits (desc));
@@ -887,8 +899,7 @@ static void intel_lrc_irq_handler(unsigned long data)if (--count ==0 ) {GEM_BUG_ON (status &GEN8_CTX_STATUS_PREEMPTED );GEM_BUG_ON (!i915_gem_request_completed (rq)); -execlists_context_status_change (rq,INTEL_CONTEXT_SCHEDULE_OUT ); - +execlists_context_schedule_out (rq);trace_i915_gem_request_out (rq);i915_gem_request_put (rq);
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 5/17 drm/i915: Engine busy time tracking
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
Track total time requests have been executing on the hardware.
We add new kernel API to allow software tracking of time GPU engines are spending executing requests.
Both per-engine and global API is added with the latter also being exported for use by external users.
v2:
* Squashed with the internal API.
* Dropped static key.
* Made per-engine.
* Store time in monotonic ktime.
v3: Moved stats clearing to disable.
v4:
* Comments.
* Don't export the API just yet.
v5: Whitespace cleanup.
v6:
* Rename ref to active.
* Drop engine aggregate stats for now.
* Account initial busy period after enabling stats.
v7:
* Rebase.
v8:
* Move context in notification after the notifier. (Chris Wilson)
v9:
In cases where stats tracking is getting disabled while there is an active context on an engine, add up the current value to the total. This also implies we don't clear the total when tracking is disabled any longer. There is no real need to do so because we define the stats as relative while enabled, meaning comparison between two samples while tracking is enabled is the valid usage. However, when busy stats will later be plugged into the perf PMU API, it is beneficial to not reset the total, since the PMU core likes to do some counter disable/enable cycles on startup, and while doing so during a single long context executing on an engine we would lose some accuracy and so make unit testing more difficult than needs to be.
v10:
* Fix accounting for preemption.
--- drivers/gpu/drm/i915/intel_engine_cs.c | 87 +++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/intel_lrc.c | 3 ++ drivers/gpu/drm/i915/intel_ringbuffer.h | 92 +++++++++++++++++++++++++++++++++ 3 files changed, 182 insertions(+)
drivers/gpu/drm/i915/intel_engine_cs.c +87 -0
@@ -237,6 +237,8 @@ intel_engine_setup(struct drm_i915_private *dev_priv,/* Nothing to do here, execute in order of dependencies */ engine->schedule =NULL ; +spin_lock_init (&engine->stats.lock); +ATOMIC_INIT_NOTIFIER_HEAD (&engine->context_status_notifier); dev_priv->engine_class[info->class][info->instance] = engine;
@@ -1819,6 +1821,91 @@ intel_engine_lookup_user(struct drm_i915_private *i915, u8 class, u8 instance)return i915->engine_class[class][instance]; } +/** +* intel_enable_engine_stats() - Enable engine busy tracking on engine +* @engine: engine to enable stats collection +* +* Start collecting the engine busyness data for @engine. +* +* Returns 0 on success or a negative error code. +*/ +int intel_enable_engine_stats (struct intel_engine_cs *engine) +{ +unsigned long flags; + +if (!i915_modparams.enable_execlists) +return -ENODEV ; + +spin_lock_irqsave (&engine->stats.lock, flags); +if (engine->stats.enabled == ~0 ) + goto busy; +if (engine->stats.enabled++ ==0 ) + engine->stats.enabled_at =ktime_get (); +spin_unlock_irqrestore (&engine->stats.lock, flags); + +return 0 ; + +busy: +spin_unlock_irqrestore (&engine->stats.lock, flags); + +return -EBUSY ; +} + +static ktime_t __intel_engine_get_busy_time (struct intel_engine_cs *engine) +{ +ktime_t total = engine->stats.total; + +/* +* If the engine is executing something at the moment +* add it to the total. +*/ +if (engine->stats.active) + total =ktime_add (total, +ktime_sub (ktime_get (), engine->stats.start)); + +return total; +} + +/** +* intel_engine_get_busy_time() - Return current accumulated engine busyness +* @engine: engine to report on +* +* Returns accumulated time @engine was busy since engine stats were enabled. +*/ +ktime_t intel_engine_get_busy_time (struct intel_engine_cs *engine) +{ +ktime_t total; +unsigned long flags; + +spin_lock_irqsave (&engine->stats.lock, flags); + total =__intel_engine_get_busy_time (engine); +spin_unlock_irqrestore (&engine->stats.lock, flags); + +return total; +} + +/** +* intel_disable_engine_stats() - Disable engine busy tracking on engine +* @engine: engine to disable stats collection +* +* Stops collecting the engine busyness data for @engine. +*/ +void intel_disable_engine_stats (struct intel_engine_cs *engine) +{ +unsigned long flags; + +if (!i915_modparams.enable_execlists) +return ; + +spin_lock_irqsave (&engine->stats.lock, flags); +WARN_ON_ONCE (engine->stats.enabled ==0 ); +if (--engine->stats.enabled ==0 ) { + engine->stats.total =__intel_engine_get_busy_time (engine); + engine->stats.active =0 ; + } +spin_unlock_irqrestore (&engine->stats.lock, flags); +} +#if IS_ENABLED (CONFIG_DRM_I915_SELFTEST )#include "selftests/mock_engine.c" #endif
drivers/gpu/drm/i915/intel_lrc.c +3 -0
@@ -404,11 +404,13 @@ static inline void execlists_context_schedule_in(struct drm_i915_gem_request *rq) {execlists_context_status_change (rq,INTEL_CONTEXT_SCHEDULE_IN ); +intel_engine_context_in (rq->engine); }static inline void execlists_context_schedule_out (struct drm_i915_gem_request *rq) { +intel_engine_context_out (rq->engine);execlists_context_status_change (rq,INTEL_CONTEXT_SCHEDULE_OUT ); }
@@ -712,6 +714,7 @@ execlist_cancel_port_requests(struct intel_engine_execlists *execlists)struct drm_i915_gem_request *rq =port_request (port);GEM_BUG_ON (!execlists->active); +intel_engine_context_out (rq->engine);execlists_context_status_change (rq,INTEL_CONTEXT_SCHEDULE_PREEMPTED );i915_gem_request_put (rq);
drivers/gpu/drm/i915/intel_ringbuffer.h +92 -0
102 lines not on this page · raw message
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 6/17 drm/i915/pmu: Wire up engine busy stats to PMU
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
We can use engine busy stats instead of the sampling timer for better accuracy.
By doing this we replace the stohastic sampling with busyness metric derived directly from engine activity. This is context switch interrupt driven, so as accurate as we can get from software tracking.
As a secondary benefit, we can also not run the sampling timer in cases only busyness metric is enabled.
v2: Rebase.
v3:
* Rebase, comments.
* Leave engine busyness controls out of workers.
v4: Checkpatch cleanup.
v5: Added comment to pmu_needs_timer change.
v6:
* Rebase.
* Fix style of some comments. (Chris Wilson)
v7: Rebase and commit message update. (Chris Wilson)
v8: Add delayed stats disabling to improve accuracy in face of
CPU hotplug events.
v9: Rebase.
--- drivers/gpu/drm/i915/i915_pmu.c | 78 ++++++++++++++++++++++++++++++++- drivers/gpu/drm/i915/intel_ringbuffer.h | 14 ++++++ 2 files changed, 90 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/i915_pmu.c +76 -2
@@ -90,6 +90,11 @@ static unsigned int event_enabled_bit(struct perf_event *event)return config_enabled_bit (event->attr.config); } +static bool supports_busy_stats (void ) +{ +return i915_modparams.enable_execlists; +} +static bool pmu_needs_timer (struct drm_i915_private *i915,bool gpu_active) {u64 enable;
@@ -115,6 +120,12 @@ static bool pmu_needs_timer(struct drm_i915_private *i915, bool gpu_active)*/ if (!gpu_active) enable &= ~ENGINE_SAMPLE_MASK ; +/* +* Also there is software busyness tracking available we do not +* need the timer for I915_SAMPLE_BUSY counter. +*/ +else if (supports_busy_stats ()) + enable &= ~BIT (I915_SAMPLE_BUSY );/* * If some bits remain it means we need the sampling timer running.
@@ -363,6 +374,9 @@ static u64 __i915_pmu_event_read(struct perf_event *event)if (WARN_ON_ONCE (!engine)) {/* Do nothing */ + }else if (sample ==I915_SAMPLE_BUSY && + engine->pmu.busy_stats) { + val =ktime_to_ns (intel_engine_get_busy_time (engine)); }else { val = engine->pmu.sample[sample].cur; }
@@ -399,6 +413,12 @@ static void i915_pmu_event_read(struct perf_event *event)local64_add (new - prev, &event->count); } +static bool engine_needs_busy_stats (struct intel_engine_cs *engine) +{ +return supports_busy_stats () && + (engine->pmu.enable &BIT (I915_SAMPLE_BUSY )); +} +static void i915_pmu_enable (struct perf_event *event) { struct drm_i915_private *i915 =
@@ -438,7 +458,21 @@ static void i915_pmu_enable(struct perf_event *event)GEM_BUG_ON (sample >=I915_PMU_SAMPLE_BITS );GEM_BUG_ON (engine->pmu.enable_count[sample] == ~0 ); - engine->pmu.enable_count[sample]++; +if (engine->pmu.enable_count[sample]++ ==0 ) { +/* +* Enable engine busy stats tracking if needed or +* alternatively cancel the scheduled disable. +* +* If the delayed disable was pending, cancel it and +* in this case do not enable since it already is. +*/ +if (engine_needs_busy_stats (engine) && + !engine->pmu.busy_stats) { + engine->pmu.busy_stats = true; +if (!cancel_delayed_work (&engine->pmu.disable_busy_stats)) +intel_enable_engine_stats (engine); + } + } }/*
@@ -451,6 +485,14 @@ static void i915_pmu_enable(struct perf_event *event)spin_unlock_irqrestore (&i915->pmu.lock, flags); } +static void __disable_busy_stats (struct work_struct *work) +{ +struct intel_engine_cs *engine = +container_of (work,typeof (*engine), pmu.disable_busy_stats.work); + +intel_disable_engine_stats (engine); +} +static void i915_pmu_disable (struct perf_event *event) { struct drm_i915_private *i915 =
@@ -474,8 +516,26 @@ static void i915_pmu_disable(struct perf_event *event)* Decrement the reference count and clear the enabled * bitmask when the last listener on an event goes away. */ -if (--engine->pmu.enable_count[sample] ==0 ) +if (--engine->pmu.enable_count[sample] ==0 ) { engine->pmu.enable &= ~BIT (sample); +if (!engine_needs_busy_stats (engine) && + engine->pmu.busy_stats) { + engine->pmu.busy_stats = false; +/* +* We request a delayed disable to handle the +* rapid on/off cycles on events, which can +* happen when tools like perf stat start, in a +* nicer way. +* +* In addition, this also helps with busy stats +* accuracy with background CPU offline/online +* migration events. +*/ +queue_delayed_work (system_wq, + &engine->pmu.disable_busy_stats, +round_jiffies_up_relative (HZ )); + } + } }GEM_BUG_ON (bit >=I915_PMU_MASK_BITS );
@@ -702,6 +762,8 @@ static void i915_pmu_unregister_cpuhp_state(struct drm_i915_private *i915)void i915_pmu_register (struct drm_i915_private *i915) { +struct intel_engine_cs *engine; +enum intel_engine_id id;int ret;if (INTEL_GEN (i915) <=2 ) {
@@ -723,6 +785,10 @@ void i915_pmu_register(struct drm_i915_private *i915)hrtimer_init (&i915->pmu.timer,CLOCK_MONOTONIC ,HRTIMER_MODE_REL ); i915->pmu.timer.function = i915_sample; +for_each_engine (engine, i915, id) +INIT_DELAYED_WORK (&engine->pmu.disable_busy_stats, + __disable_busy_stats); + ret =perf_pmu_register (&i915->pmu.base,"i915" ,-1 );if (ret) goto err;
@@ -742,6 +808,9 @@ void i915_pmu_register(struct drm_i915_private *i915)void i915_pmu_unregister (struct drm_i915_private *i915) { +struct intel_engine_cs *engine; +enum intel_engine_id id; +if (!i915->pmu.base.event_init)return ;
@@ -749,6 +818,11 @@ void i915_pmu_unregister(struct drm_i915_private *i915)hrtimer_cancel (&i915->pmu.timer); +for_each_engine (engine, i915, id) { +GEM_BUG_ON (engine->pmu.busy_stats); +flush_delayed_work (&engine->pmu.disable_busy_stats); + } +i915_pmu_unregister_cpuhp_state (i915);perf_pmu_unregister (&i915->pmu.base);
drivers/gpu/drm/i915/intel_ringbuffer.h +14 -0
@@ -366,6 +366,20 @@ struct intel_engine_cs {* Our internal timer stores the current counters in this field. */ struct i915_pmu_sample sample[I915_ENGINE_SAMPLE_MAX ]; +/** +* @busy_stats: Has enablement of engine stats tracking been +* requested. +*/ +bool busy_stats; +/** +* @disable_busy_stats: Work item for busy stats disabling. +* +* Same as with @enable_busy_stats action, with the difference +* that we delay it in case there are rapid enable-disable +* actions, which can happen during tool startup (like perf +* stat). +*/ +struct delayed_work disable_busy_stats; } pmu;/*
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 7/17 drm/i915/pmu: Add interrupt count metric
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
For clients like intel-gpu-overlay it is easier to read the count via the perf API than having to parse /proc.
--- drivers/gpu/drm/i915/i915_pmu.c | 23 +++++++++++++++++++++++ include/uapi/drm/i915_drm.h | 4 +++- 2 files changed, 26 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_pmu.c +23 -0
@@ -277,6 +277,22 @@ static enum hrtimer_restart i915_sample(struct hrtimer *hrtimer)return HRTIMER_RESTART ; } +static u64 count_interrupts (struct drm_i915_private *i915) +{ +/* open-coded kstat_irqs() */ +struct irq_desc *desc =irq_to_desc (i915->drm.pdev->irq); +u64 sum =0 ; +int cpu; + +if (!desc || !desc->kstat_irqs) +return 0 ; + +for_each_possible_cpu (cpu) + sum += *per_cpu_ptr (desc->kstat_irqs, cpu); + +return sum; +} +static void i915_pmu_event_destroy (struct perf_event *event) {WARN_ON (event->parent);
@@ -343,6 +359,8 @@ static int i915_pmu_event_init(struct perf_event *event)if (INTEL_GEN (i915) <6 ) ret = -ENODEV ;break ; +case I915_PMU_INTERRUPTS : +break ;default : ret = -ENOENT ;break ;
@@ -392,6 +410,9 @@ static u64 __i915_pmu_event_read(struct perf_event *event)div_u64 (i915->pmu.sample[__I915_SAMPLE_FREQ_REQ].cur,FREQUENCY );break ; +case I915_PMU_INTERRUPTS : + val =count_interrupts (i915); +break ; } }
@@ -654,6 +675,8 @@ static struct attribute *i915_pmu_events_attrs[] = {I915_EVENT (actual-frequency,I915_PMU_ACTUAL_FREQUENCY ,"MHz" ),I915_EVENT (requested-frequency,I915_PMU_REQUESTED_FREQUENCY ,"MHz" ), +I915_EVENT_ATTR (interrupts,I915_PMU_INTERRUPTS ), + NULL, };
include/uapi/drm/i915_drm.h +3 -1
@@ -132,7 +132,9 @@ enum drm_i915_pmu_engine_sample {#define I915_PMU_ACTUAL_FREQUENCY __I915_PMU_OTHER(0)#define I915_PMU_REQUESTED_FREQUENCY __I915_PMU_OTHER(1) -#define I915_PMU_LAST I915_PMU_REQUESTED_FREQUENCY +#define I915_PMU_INTERRUPTS __I915_PMU_OTHER(2) + +#define I915_PMU_LAST I915_PMU_INTERRUPTS/* Each region is a minimum of 16k, and there are at most 255 of them. */
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 8/17 drm/i915: Convert intel_rc6_residency_us to ns
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
Will be used for exposing the PMU counters.
v2:
* Move intel_runtime_pm_get/put to the callers. (Chris Wilson)
* Restore full unit conversion precision.
--- drivers/gpu/drm/i915/i915_drv.h | 8 +++++++- drivers/gpu/drm/i915/i915_sysfs.c | 9 +++++++-- drivers/gpu/drm/i915/intel_pm.c | 27 +++++++++++++-------------- 3 files changed, 27 insertions(+), 17 deletions(-)
drivers/gpu/drm/i915/i915_drv.h +7 -1
@@ -4204,11 +4204,17 @@ void vlv_phy_reset_lanes(struct intel_encoder *encoder);int intel_gpu_freq (struct drm_i915_private *dev_priv,int val);int intel_freq_opcode (struct drm_i915_private *dev_priv,int val); -u64 intel_rc6_residency_us (struct drm_i915_private *dev_priv, +u64 intel_rc6_residency_ns (struct drm_i915_private *dev_priv,const i915_reg_t reg);u32 intel_get_cagf (struct drm_i915_private *dev_priv,u32 rpstat1); +static inline u64 intel_rc6_residency_us (struct drm_i915_private *dev_priv, +const i915_reg_t reg) +{ +return DIV_ROUND_UP_ULL (intel_rc6_residency_ns (dev_priv, reg),1000 ); +} +#define I915_READ8 (reg) dev_priv->uncore.funcs.mmio_readb(dev_priv, (reg), true)#define I915_WRITE8 (reg, val) dev_priv->uncore.funcs.mmio_writeb(dev_priv, (reg), (val), true)
drivers/gpu/drm/i915/i915_sysfs.c +7 -2
@@ -42,8 +42,13 @@ static inline struct drm_i915_private *kdev_minor_to_i915(struct device *kdev)static u32 calc_residency (struct drm_i915_private *dev_priv,i915_reg_t reg) { -return DIV_ROUND_CLOSEST_ULL (intel_rc6_residency_us (dev_priv, reg), -1000 ); +u64 res; + +intel_runtime_pm_get (dev_priv); + res =intel_rc6_residency_us (dev_priv, reg); +intel_runtime_pm_put (dev_priv); + +return DIV_ROUND_CLOSEST_ULL (res,1000 ); } static ssize_t
drivers/gpu/drm/i915/intel_pm.c +13 -14
@@ -9499,36 +9499,35 @@ static u64 vlv_residency_raw(struct drm_i915_private *dev_priv,return lower | (u64 )upper <<8 ; } -u64 intel_rc6_residency_us (struct drm_i915_private *dev_priv, +u64 intel_rc6_residency_ns (struct drm_i915_private *dev_priv,const i915_reg_t reg) { -u64 time_hw, units, div; +u64 time_hw; +u32 mul, div;if (!intel_rc6_enabled ())return 0 ; -intel_runtime_pm_get (dev_priv); -/* On VLV and CHV, residency time is in CZ units rather than 1.28us */ if (IS_VALLEYVIEW (dev_priv) ||IS_CHERRYVIEW (dev_priv)) { - units =1000 ; + mul =1000000 ; div = dev_priv->czclk_freq; - time_hw =vlv_residency_raw (dev_priv, reg); - }else if (IS_GEN9_LP (dev_priv)) { - units =1000 ; - div =1200 ;/* 833.33ns */ - time_hw =I915_READ (reg); }else { - units =128000 ;/* 1.28us */ - div =100000 ; +/* 833.33ns units on Gen9LP, 1.28us elsewhere. */ +if (IS_GEN9_LP (dev_priv)) { + mul =10000 ; + div =12 ; + }else { + mul =1280 ; + div =1 ; + } time_hw =I915_READ (reg); } -intel_runtime_pm_put (dev_priv); -return DIV_ROUND_UP_ULL (time_hw * units, div); +return DIV_ROUND_UP_ULL (time_hw * mul, div); }u32 intel_get_cagf (struct drm_i915_private *dev_priv,u32 rpstat)
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 9/17 drm/i915/pmu: Add RC6 residency metrics
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
For clients like intel-gpu-overlay it is easier to read the counters via the perf API than having to parse sysfs.
--- drivers/gpu/drm/i915/i915_pmu.c | 31 +++++++++++++++++++++++++++++++ include/uapi/drm/i915_drm.h | 6 +++++- 2 files changed, 36 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_pmu.c +31 -0
@@ -361,6 +361,15 @@ static int i915_pmu_event_init(struct perf_event *event)break ;case I915_PMU_INTERRUPTS :break ; +case I915_PMU_RC6_RESIDENCY : +if (!HAS_RC6 (i915)) + ret = -ENODEV ; +break ; +case I915_PMU_RC6p_RESIDENCY: +case I915_PMU_RC6pp_RESIDENCY: +if (!HAS_RC6p (i915)) + ret = -ENODEV ; +break ;default : ret = -ENOENT ;break ;
@@ -413,6 +422,24 @@ static u64 __i915_pmu_event_read(struct perf_event *event)case I915_PMU_INTERRUPTS : val =count_interrupts (i915);break ; +case I915_PMU_RC6_RESIDENCY : +intel_runtime_pm_get (i915); + val =intel_rc6_residency_ns (i915, +IS_VALLEYVIEW (i915) ? +VLV_GT_RENDER_RC6 : +GEN6_GT_GFX_RC6 ); +intel_runtime_pm_put (i915); +break ; +case I915_PMU_RC6p_RESIDENCY: +intel_runtime_pm_get (i915); + val =intel_rc6_residency_ns (i915, GEN6_GT_GFX_RC6p); +intel_runtime_pm_put (i915); +break ; +case I915_PMU_RC6pp_RESIDENCY: +intel_runtime_pm_get (i915); + val =intel_rc6_residency_ns (i915, GEN6_GT_GFX_RC6pp); +intel_runtime_pm_put (i915); +break ; } }
@@ -677,6 +704,10 @@ static struct attribute *i915_pmu_events_attrs[] = {I915_EVENT_ATTR (interrupts,I915_PMU_INTERRUPTS ), +I915_EVENT (rc6-residency,I915_PMU_RC6_RESIDENCY ,"ns" ), +I915_EVENT (rc6p-residency, I915_PMU_RC6p_RESIDENCY,"ns" ), +I915_EVENT (rc6pp-residency, I915_PMU_RC6pp_RESIDENCY,"ns" ), + NULL, };
include/uapi/drm/i915_drm.h +5 -1
@@ -134,7 +134,11 @@ enum drm_i915_pmu_engine_sample {#define I915_PMU_INTERRUPTS __I915_PMU_OTHER(2) -#define I915_PMU_LAST I915_PMU_INTERRUPTS +#define I915_PMU_RC6_RESIDENCY __I915_PMU_OTHER(3) +#define I915_PMU_RC6p_RESIDENCY __I915_PMU_OTHER(4) +#define I915_PMU_RC6pp_RESIDENCY __I915_PMU_OTHER(5) + +#define I915_PMU_LAST I915_PMU_RC6pp_RESIDENCY/* Each region is a minimum of 16k, and there are at most 255 of them. */
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 10/17 drm/i915: Keep a count of requests waiting for a slot on GPU
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
Keep a per-engine number of runnable (waiting for GPU time) requests.
--- drivers/gpu/drm/i915/i915_gem_request.c | 5 +++++ drivers/gpu/drm/i915/intel_engine_cs.c | 6 ++++-- drivers/gpu/drm/i915/intel_lrc.c | 1 + drivers/gpu/drm/i915/intel_ringbuffer.h | 8 ++++++++ 4 files changed, 18 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/i915_gem_request.c +5 -0
@@ -478,6 +478,9 @@ void __i915_gem_request_submit(struct drm_i915_gem_request *request) engine->emit_breadcrumb (request, request->ring->vaddr + request->postfix); +GEM_BUG_ON (engine->queued ==0 ); + engine->queued--; +spin_lock (&request->timeline->lock);list_move_tail (&request->link, &timeline->requests);spin_unlock (&request->timeline->lock);
@@ -523,6 +526,8 @@ void __i915_gem_request_unsubmit(struct drm_i915_gem_request *request) timeline = request->timeline;GEM_BUG_ON (timeline == engine->timeline); + engine->queued++; +spin_lock (&timeline->lock);list_move (&request->link, &timeline->requests);spin_unlock (&timeline->lock);
drivers/gpu/drm/i915/intel_engine_cs.c +4 -2
@@ -1658,12 +1658,14 @@ void intel_engine_dump(struct intel_engine_cs *engine, struct drm_printer *m)u64 addr;drm_printf (m,"%s\n" , engine->name); -drm_printf (m,"\tcurrent seqno %x, last %x, hangcheck %x [%d ms], inflight %d\n" , +drm_printf (m,"\tcurrent seqno %x, last %x, hangcheck %x [%d ms], inflight %d, queued %d\n" ,intel_engine_get_seqno (engine),intel_engine_last_submit (engine), engine->hangcheck.seqno,jiffies_to_msecs (jiffies - engine->hangcheck.action_timestamp), - engine->timeline->inflight_seqnos); + engine->timeline->inflight_seqnos, + i915_modparams.enable_execlists ||INTEL_GEN (dev_priv) >=9 ? + engine->queued :-1 );drm_printf (m,"\tReset count: %d\n" ,i915_reset_engine_count (error, engine));
drivers/gpu/drm/i915/intel_lrc.c +1 -0
@@ -938,6 +938,7 @@ static void insert_request(struct intel_engine_cs *engine, {struct i915_priolist *p =lookup_priolist (engine, pt, prio); + engine->queued++;list_add_tail (&pt->link, &ptr_mask_bits (p,1 )->requests);if (ptr_unmask_bits (p,1 ))tasklet_hi_schedule (&engine->execlists.irq_tasklet);
drivers/gpu/drm/i915/intel_ringbuffer.h +8 -0
@@ -303,6 +303,14 @@ struct intel_engine_cs {struct intel_ring *buffer;struct intel_timeline *timeline; +/** +* @queued: Number of runnable requests submitted to the backend. +* +* Count of requests waiting for the GPU to execute them. +* +* Valid only with execlists and GuC submissions backends. +*/ +unsigned int queued;struct intel_render_state *render_state;
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 11/17 drm/i915/pmu: Add queued counter
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
We add a PMU counter to expose the number of requests currently submitted to the GPU, plus the number of runnable requests waiting on GPU time.
This is useful to analyze the overall load of the system.
--- drivers/gpu/drm/i915/i915_pmu.c | 30 +++++++++++++++++++++++++----- include/uapi/drm/i915_drm.h | 6 ++++++ 2 files changed, 31 insertions(+), 5 deletions(-)
drivers/gpu/drm/i915/i915_pmu.c +25 -5
@@ -36,7 +36,8 @@#define ENGINE_SAMPLE_MASK \ (BIT(I915_SAMPLE_BUSY) | \ BIT(I915_SAMPLE_WAIT) | \ - BIT(I915_SAMPLE_SEMA)) + BIT(I915_SAMPLE_SEMA) | \ + BIT(I915_SAMPLE_QUEUED))#define ENGINE_SAMPLE_BITS (1 << I915_PMU_SAMPLE_BITS)
@@ -228,6 +229,12 @@ static void engines_sample(struct drm_i915_private *dev_priv)update_sample (&engine->pmu.sample[I915_SAMPLE_SEMA ],PERIOD , !!(val &RING_WAIT_SEMAPHORE )); + +if (engine->pmu.enable &BIT (I915_SAMPLE_QUEUED )) +update_sample (&engine->pmu.sample[I915_SAMPLE_QUEUED ], +1 /I915_SAMPLE_QUEUED_SCALE , + engine->queued + + (last_seqno - current_seqno)); }if (fw)
@@ -315,6 +322,10 @@ static int engine_event_init(struct perf_event *event)if (INTEL_GEN (i915) <6 )return -ENODEV ;break ; +case I915_SAMPLE_QUEUED : +if (INTEL_GEN (i915) <8 || !i915_modparams.enable_execlists) +return -ENODEV ; +break ;default :return -ENOENT ; }
@@ -404,6 +415,10 @@ static u64 __i915_pmu_event_read(struct perf_event *event) }else if (sample ==I915_SAMPLE_BUSY && engine->pmu.busy_stats) { val =ktime_to_ns (intel_engine_get_busy_time (engine)); + }else if (sample ==I915_SAMPLE_QUEUED ) { + val = +div_u64 (engine->pmu.sample[I915_SAMPLE_QUEUED ].cur, +FREQUENCY ); }else { val = engine->pmu.sample[sample].cur; }
@@ -684,13 +699,18 @@ static ssize_t i915_pmu_event_show(struct device *dev, I915_EVENT_STR(_name.unit, _unit)#define I915_ENGINE_EVENT (_name, _class, _instance, _sample) \ - I915_EVENT_ATTR(_name, __I915_PMU_ENGINE(_class, _instance, _sample)), \ + I915_EVENT_ATTR(_name, __I915_PMU_ENGINE(_class, _instance, _sample)) + +#define I915_ENGINE_EVENT_NS (_name, _class, _instance, _sample) \ + I915_ENGINE_EVENT(_name, _class, _instance, _sample), \ I915_EVENT_STR(_name.unit, "ns")#define I915_ENGINE_EVENTS (_name, _class, _instance) \ - I915_ENGINE_EVENT(_name##_instance-busy, _class, _instance, I915_SAMPLE_BUSY), \ - I915_ENGINE_EVENT(_name##_instance-sema, _class, _instance, I915_SAMPLE_SEMA), \ - I915_ENGINE_EVENT(_name##_instance-wait, _class, _instance, I915_SAMPLE_WAIT) + I915_ENGINE_EVENT_NS(_name##_instance-busy, _class, _instance, I915_SAMPLE_BUSY), \ + I915_ENGINE_EVENT_NS(_name##_instance-sema, _class, _instance, I915_SAMPLE_SEMA), \ + I915_ENGINE_EVENT_NS(_name##_instance-wait, _class, _instance, I915_SAMPLE_WAIT), \ + I915_ENGINE_EVENT(_name##_instance-queued, _class, _instance, I915_SAMPLE_QUEUED), \ + I915_EVENT_STR(_name##_instance-queued.scale, __stringify(I915_SAMPLE_QUEUED_SCALE))static struct attribute *i915_pmu_events_attrs[] = {I915_ENGINE_EVENTS (rcs,I915_ENGINE_CLASS_RENDER ,0 ),
include/uapi/drm/i915_drm.h +6 -0
@@ -104,9 +104,12 @@ enum drm_i915_pmu_engine_sample {I915_SAMPLE_BUSY =0 ,I915_SAMPLE_WAIT =1 ,I915_SAMPLE_SEMA =2 , +I915_SAMPLE_QUEUED =3 , I915_ENGINE_SAMPLE_MAX /* non-ABI */ }; +#define I915_SAMPLE_QUEUED_SCALE 1e-2/* No braces please. */ +#define I915_PMU_SAMPLE_BITS (4)#define I915_PMU_SAMPLE_MASK (0xf)#define I915_PMU_SAMPLE_INSTANCE_BITS (8)
@@ -127,6 +130,9 @@ enum drm_i915_pmu_engine_sample {#define I915_PMU_ENGINE_SEMA (class, instance) \ __I915_PMU_ENGINE(class, instance, I915_SAMPLE_SEMA) +#define I915_PMU_ENGINE_QUEUED (class, instance) \ + __I915_PMU_ENGINE(class, instance, I915_SAMPLE_QUEUED) +#define __I915_PMU_OTHER (x) (__I915_PMU_ENGINE(0xff, 0xff, 0xf) + 1 + (x))#define I915_PMU_ACTUAL_FREQUENCY __I915_PMU_OTHER(0)
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 12/17 drm/i915: Track per-context engine busyness
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
Some customers want to know how much of the GPU time are their clients using in order to make dynamic load balancing decisions.
With the hooks already in place which track the overall engine busyness, we can extend that slightly to split that time between contexts.
--- drivers/gpu/drm/i915/i915_gem_context.h | 4 ++++ drivers/gpu/drm/i915/intel_lrc.c | 14 +++++++----- drivers/gpu/drm/i915/intel_ringbuffer.h | 39 ++++++++++++++++++++++++++++----- 3 files changed, 46 insertions(+), 11 deletions(-)
drivers/gpu/drm/i915/i915_gem_context.h +4 -0
@@ -158,6 +158,10 @@ struct i915_gem_context {u64 lrc_desc;int pin_count;bool initialised; +struct { +ktime_t start; +ktime_t total; + } stats; } engine[I915_NUM_ENGINES ];/** ring_size: size for allocating the per-engine ring buffer */
drivers/gpu/drm/i915/intel_lrc.c +9 -5
@@ -401,16 +401,19 @@ execlists_context_status_change(struct drm_i915_gem_request *rq, }static inline void -execlists_context_schedule_in (struct drm_i915_gem_request *rq) +execlists_context_schedule_in (struct drm_i915_gem_request *rq, +unsigned int port) {execlists_context_status_change (rq,INTEL_CONTEXT_SCHEDULE_IN ); -intel_engine_context_in (rq->engine); +intel_engine_context_in (rq->engine, + &rq->ctx->engine[rq->engine->id], + port ==0 ); }static inline void execlists_context_schedule_out (struct drm_i915_gem_request *rq) { -intel_engine_context_out (rq->engine); +intel_engine_context_out (rq->engine, &rq->ctx->engine[rq->engine->id]);execlists_context_status_change (rq,INTEL_CONTEXT_SCHEDULE_OUT ); }
@@ -465,7 +468,7 @@ static void execlists_submit_ports(struct intel_engine_cs *engine)if (rq) {GEM_BUG_ON (count > !n);if (!count++) -execlists_context_schedule_in (rq); +execlists_context_schedule_in (rq, n);port_set (&port[n],port_pack (rq, count)); desc =execlists_update_context (rq);GEM_DEBUG_EXEC (port[n].context_id =upper_32_bits (desc));
@@ -714,7 +717,8 @@ execlist_cancel_port_requests(struct intel_engine_execlists *execlists)struct drm_i915_gem_request *rq =port_request (port);GEM_BUG_ON (!execlists->active); -intel_engine_context_out (rq->engine); +intel_engine_context_out (rq->engine, + &rq->ctx->engine[rq->engine->id]);execlists_context_status_change (rq,INTEL_CONTEXT_SCHEDULE_PREEMPTED );i915_gem_request_put (rq);
drivers/gpu/drm/i915/intel_ringbuffer.h +33 -6
@@ -3,6 +3,7 @@#include <linux/hashtable.h> #include "i915_gem_batch_pool.h" +#include "i915_gem_context.h" #include "i915_gem_request.h" #include "i915_gem_timeline.h" #include "i915_pmu.h"
@@ -953,25 +954,37 @@ void intel_engine_dump(struct intel_engine_cs *engine, struct drm_printer *p);struct intel_engine_cs *intel_engine_lookup_user (struct drm_i915_private *i915,u8 class,u8 instance); -static inline void intel_engine_context_in (struct intel_engine_cs *engine) +static inline void +intel_engine_context_in (struct intel_engine_cs *engine, +struct intel_context *ce, +bool submit) {unsigned long flags; +ktime_t now;if (READ_ONCE (engine->stats.enabled) ==0 )return ;spin_lock_irqsave (&engine->stats.lock, flags); + now = submit ?ktime_get () :0 ; + ce->stats.start = now; +if (engine->stats.enabled >0 ) { -if (engine->stats.active++ ==0 ) - engine->stats.start =ktime_get (); +if (engine->stats.active++ ==0 ) { +if (!now) + now =ktime_get (); + engine->stats.start = now; + }GEM_BUG_ON (engine->stats.active ==0 ); }spin_unlock_irqrestore (&engine->stats.lock, flags); } -static inline void intel_engine_context_out (struct intel_engine_cs *engine) +static inline void +intel_engine_context_out (struct intel_engine_cs *engine, +struct intel_context *ce) {unsigned long flags;
@@ -981,14 +994,28 @@ static inline void intel_engine_context_out(struct intel_engine_cs *engine)spin_lock_irqsave (&engine->stats.lock, flags);if (engine->stats.enabled >0 ) { +struct execlist_port *next_port = &engine->execlists.port[1 ]; +ktime_t now =ktime_get ();ktime_t last; +GEM_BUG_ON (!ce->stats.start); + ce->stats.total =ktime_add (ce->stats.total, +ktime_sub (now, ce->stats.start)); +if (port_isset (next_port)) { +struct drm_i915_gem_request *next_req = +port_request (next_port); +struct intel_context *next_ce = + &next_req->ctx->engine[engine->id]; + + next_ce->stats.start = now; + } +if (engine->stats.active && --engine->stats.active ==0 ) {/* * Decrement the active context count and in case GPU * is now idle add up to the running total. */ - last =ktime_sub (ktime_get (), engine->stats.start); + last =ktime_sub (now, engine->stats.start); engine->stats.total =ktime_add (engine->stats.total, last);
@@ -998,7 +1025,7 @@ static inline void intel_engine_context_out(struct intel_engine_cs *engine)* the first event in which case we account from the * time stats gathering was turned on. */ - last =ktime_sub (ktime_get (), engine->stats.enabled_at); + last =ktime_sub (now, engine->stats.enabled_at); engine->stats.total =ktime_add (engine->stats.total, last);
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 13/17 drm/i915: Allow clients to query own per-engine busyness
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
Some customers want to know how much of the GPU time are their clients using in order to make dynamic load balancing decisions.
With the accounting infrastructure in place in the previous patch, we add a new context param (I915_CONTEXT_GET_ENGINE_BUSY) which takes a class and instance of an engine for which the client would like to know its utilization.
Utilization is reported as monotonically increasing number of nano- seconds the engine spent executing jobs belonging to this context.
--- drivers/gpu/drm/i915/i915_gem_context.c | 34 ++++++++++++++++++++++++++++++--- drivers/gpu/drm/i915/i915_gem_context.h | 1 + include/uapi/drm/i915_drm.h | 9 ++++++++- 3 files changed, 40 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/i915_gem_context.c +31 -3
@@ -129,6 +129,9 @@ static void i915_gem_context_free(struct i915_gem_context *ctx)for (i =0 ; i <I915_NUM_ENGINES ; i++) {struct intel_context *ce = &ctx->engine[i]; +if (ce->stats.enabled) +intel_disable_engine_stats (ctx->i915->engine[i]); +if (!ce->state)continue ;
@@ -1041,6 +1044,7 @@ int i915_gem_context_getparam_ioctl(struct drm_device *dev, void *data, {struct drm_i915_file_private *file_priv = file->driver_priv;struct drm_i915_gem_context_param *args = data; +struct drm_i915_private *i915 =to_i915 (dev);struct i915_gem_context *ctx;int ret =0 ;
@@ -1059,10 +1063,10 @@ int i915_gem_context_getparam_ioctl(struct drm_device *dev, void *data,case I915_CONTEXT_PARAM_GTT_SIZE :if (ctx->ppgtt) args->value = ctx->ppgtt->base.total; -else if (to_i915 (dev)->mm.aliasing_ppgtt) - args->value =to_i915 (dev)->mm.aliasing_ppgtt->base.total; +else if (i915->mm.aliasing_ppgtt) + args->value = i915->mm.aliasing_ppgtt->base.total;else - args->value =to_i915 (dev)->ggtt.base.total; + args->value = i915->ggtt.base.total;break ;case I915_CONTEXT_PARAM_NO_ERROR_CAPTURE : args->value =i915_gem_context_no_error_capture (ctx);
@@ -1073,6 +1077,29 @@ int i915_gem_context_getparam_ioctl(struct drm_device *dev, void *data,case I915_CONTEXT_PARAM_PRIORITY : args->value = ctx->priority;break ; +case I915_CONTEXT_GET_ENGINE_BUSY : + ret =i915_mutex_lock_interruptible (dev); +if (!ret) { +struct intel_engine_cs *engine; + + ret = -EINVAL ; + engine =intel_engine_lookup_user (i915, + args->class, + args->instance); + +if (engine) { + ret =0 ; +if (!ctx->engine[engine->id].stats.enabled) + ret =intel_enable_engine_stats (engine); + +if (!ret) + args->value = +ktime_to_ns (ctx->engine[engine->id].stats.total); + } + +mutex_unlock (&dev->struct_mutex); + } +break ;default : ret = -EINVAL ;break ;
@@ -1148,6 +1175,7 @@ int i915_gem_context_setparam_ioctl(struct drm_device *dev, void *data, }break ; +case I915_CONTEXT_GET_ENGINE_BUSY :default : ret = -EINVAL ;break ;
drivers/gpu/drm/i915/i915_gem_context.h +1 -0
@@ -159,6 +159,7 @@ struct i915_gem_context {int pin_count;bool initialised;struct { +bool enabled;ktime_t start;ktime_t total; } stats;
include/uapi/drm/i915_drm.h +8 -1
@@ -1434,7 +1434,14 @@ struct drm_i915_gem_context_param {#define I915_CONTEXT_MAX_USER_PRIORITY 1023/* inclusive */ #define I915_CONTEXT_DEFAULT_PRIORITY 0#define I915_CONTEXT_MIN_USER_PRIORITY -1023/* inclusive */ -__u64 value; +#define I915_CONTEXT_GET_ENGINE_BUSY 0x7 +union { +__u64 value; +struct { +__u8 class; +__u8 instance; + }; + }; };enum drm_i915_oa_format {
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 14/17 drm/i915: Expose list of clients in sysfs
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
Expose a list of clients with open file handles in sysfs.
This will be a basis for a top-like utility showing per-client and per- engine GPU load.
Currently we only expose each client's pid and name under opaque numbered directories in /sys/class/drm/card0/clients/.
For instance:
/sys/class/drm/card0/clients/3/name: Xorg/sys/class/drm/card0/clients/3/pid: 5664
--- drivers/gpu/drm/i915/i915_drv.h | 13 +++++ drivers/gpu/drm/i915/i915_gem.c | 112 +++++++++++++++++++++++++++++++++++--- drivers/gpu/drm/i915/i915_sysfs.c | 8 +++ 3 files changed, 126 insertions(+), 7 deletions(-)
drivers/gpu/drm/i915/i915_drv.h +13 -0
@@ -622,6 +622,16 @@ struct drm_i915_file_private {*/ #define I915_MAX_CLIENT_CONTEXT_BANS 3atomic_t context_bans; + +unsigned int client_sysfs_id; +unsigned int client_pid; +char *client_name; +struct kobject *client_root; + +struct { +struct device_attribute pid; +struct device_attribute name; + } attr; };/* Used by dp and fdi links */
@@ -2756,6 +2766,9 @@ struct drm_i915_private {struct i915_pmu pmu; +struct kobject *clients_root; +atomic_t client_serial; +/* * NOTE: This is the dri1/ums dungeon, don't add stuff here. Your patch * will be rejected. Instead look for a better place.
drivers/gpu/drm/i915/i915_gem.c +105 -7
143 lines not on this page · raw message
drivers/gpu/drm/i915/i915_sysfs.c +8 -0
@@ -564,6 +564,11 @@ void i915_setup_sysfs(struct drm_i915_private *dev_priv)struct device *kdev = dev_priv->drm.primary->kdev;int ret; + dev_priv->clients_root = +kobject_create_and_add ("clients" , &kdev->kobj); +if (!dev_priv->clients_root) +DRM_ERROR ("Per-client sysfs setup failed\n" ); +#ifdef CONFIG_PM if (HAS_RC6 (dev_priv)) { ret = sysfs_merge_group(&kdev->kobj,
@@ -624,4 +629,7 @@ void i915_teardown_sysfs(struct drm_i915_private *dev_priv)sysfs_unmerge_group (&kdev->kobj, &rc6_attr_group);sysfs_unmerge_group (&kdev->kobj, &rc6p_attr_group);#endif + +if (dev_priv->clients_root) +kobject_put (dev_priv->clients_root); }
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 15/17 drm/i915: Update client name on context create
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
Some clients have the DRM fd passed to them over a socket by the X server.
Grab the real client and pid when they create their first context and update the exposed data for more useful enumeration.
--- drivers/gpu/drm/i915/i915_drv.h | 8 ++++++++ drivers/gpu/drm/i915/i915_gem.c | 4 ++-- drivers/gpu/drm/i915/i915_gem_context.c | 15 +++++++++++++-- 3 files changed, 23 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/i915_drv.h +8 -0
@@ -3787,6 +3787,14 @@ i915_gem_object_pin_to_display_plane(struct drm_i915_gem_object *obj,void i915_gem_object_unpin_from_display_plane (struct i915_vma *vma);int i915_gem_object_attach_phys (struct drm_i915_gem_object *obj,int align); + +int +i915_gem_add_client (struct drm_i915_private *i915, +struct drm_i915_file_private *file_priv, +struct task_struct *task, +unsigned int serial); +void i915_gem_remove_client (struct drm_i915_file_private *file_priv); +int i915_gem_open (struct drm_i915_private *i915,struct drm_file *file);void i915_gem_release (struct drm_device *dev,struct drm_file *file);
drivers/gpu/drm/i915/i915_gem.c +2 -2
@@ -5251,7 +5251,7 @@ show_client_pid(struct device *kdev, struct device_attribute *attr, char *buf)return snprintf (buf,PAGE_SIZE ,"%u" , file_priv->client_pid); } -static int +int i915_gem_add_client(struct drm_i915_private *i915, struct drm_i915_file_private *file_priv, struct task_struct *task,
@@ -5306,7 +5306,7 @@ i915_gem_add_client(struct drm_i915_private *i915,return ret; } -static void i915_gem_remove_client (struct drm_i915_file_private *file_priv) +void i915_gem_remove_client (struct drm_i915_file_private *file_priv) {sysfs_remove_file (file_priv->client_root, (struct attribute *)&file_priv->attr.pid);
drivers/gpu/drm/i915/i915_gem_context.c +13 -2
@@ -972,6 +972,7 @@ static bool client_is_banned(struct drm_i915_file_private *file_priv)int i915_gem_context_create_ioctl (struct drm_device *dev,void *data,struct drm_file *file) { +unsigned int pid =pid_nr (get_task_pid (current,PIDTYPE_PID ));struct drm_i915_private *dev_priv =to_i915 (dev);struct drm_i915_gem_context_create *args = data;struct drm_i915_file_private *file_priv = file->driver_priv;
@@ -986,8 +987,7 @@ int i915_gem_context_create_ioctl(struct drm_device *dev, void *data,if (client_is_banned (file_priv)) {DRM_DEBUG ("client %s[%d] banned from creating ctx\n" , - current->comm, -pid_nr (get_task_pid (current,PIDTYPE_PID ))); + current->comm, pid);return -EIO ; }
@@ -996,6 +996,17 @@ int i915_gem_context_create_ioctl(struct drm_device *dev, void *data,if (ret)return ret; +if (file_priv->client_pid != pid) { +unsigned int id = file_priv->client_sysfs_id; + +i915_gem_remove_client (file_priv); + ret =i915_gem_add_client (dev_priv, file_priv, current, id); +if (ret) { +mutex_unlock (&dev->struct_mutex); +return ret; + } + } + ctx =i915_gem_create_context (dev_priv, file_priv);mutex_unlock (&dev->struct_mutex);if (IS_ERR (ctx))
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 16/17 drm/i915: Expose per-engine client busyness
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
Expose per-client and per-engine busyness under the previously added sysfs client root.
The new file is named 'busy' and contains a list of, one line for each engine, monotonically increasing nano-second resolution times each client's jobs were executing on the GPU.
$ cat /sys/class/drm/card0/clients/5/busy 32516602 0 0 0
This data can serve as an interface to implement a top like utility for GPU jobs. For instance I have prototyped a tool in IGT which produces periodic output like:
neverball[ 6011]: rcs0: 41.01% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%
Xorg[ 5664]: rcs0: 31.16% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%
xfwm4[ 5727]: rcs0: 0.00% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%This tools can also be extended to use the i915 PMU and show overall engine busyness, and engine loads using the queue depth metric.
--- drivers/gpu/drm/i915/i915_drv.h | 1 + drivers/gpu/drm/i915/i915_gem.c | 65 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 66 insertions(+)
drivers/gpu/drm/i915/i915_drv.h +1 -0
@@ -631,6 +631,7 @@ struct drm_i915_file_private {struct {struct device_attribute pid;struct device_attribute name; +struct device_attribute busy; } attr; };
drivers/gpu/drm/i915/i915_gem.c +65 -0
87 lines not on this page · raw message
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Tvrtko Ursulin
maintainerRFC 17/17 drm/i915: Add sysfs toggle to enable per-client engine stats
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
By default we are not collecting any per-engine and per-context statistcs.
Add a new sysfs toggle to enable this facility:
$ echo 1 >/sys/class/drm/card0/clients/enable_stats
--- drivers/gpu/drm/i915/i915_drv.h | 2 ++ drivers/gpu/drm/i915/i915_sysfs.c | 71 +++++++++++++++++++++++++++++++++++++++ 2 files changed, 73 insertions(+)
drivers/gpu/drm/i915/i915_drv.h +2 -0
@@ -2769,6 +2769,8 @@ struct drm_i915_private {struct kobject *clients_root;atomic_t client_serial; +struct device_attribute client_stats_attr; +bool client_stats_enabled;/* * NOTE: This is the dri1/ums dungeon, don't add stuff here. Your patch
drivers/gpu/drm/i915/i915_sysfs.c +71 -0
92 lines not on this page · raw message
Signature · 6 lines
2.9.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoting Tvrtko Ursulin (2017-10-25 16:36:15)
Quoted 17 lines
From: Tvrtko Ursulin <[email protected]>
Lightly tested (apart from patch 13) series to start the discussion early.
Please skip patches 1-9, and probably 10-11 as well, those ones are the current PMU effort which is yet unmerged but needed as a basis for patches 12-17.
Customer ask is to allow clients to query how much GPU engine time they are using per context.
In patch 12 I add this, and then patch 13 I expose it via the context get param. (It feels like a slight misuse of get param though.)
Patches 14-17 are not a customer ask as far as I know, but something I thought would be pretty cool. Basically bringing the ability to write a CPU top-like utility for GPU tasks.
Quoted 5 lines
I've prototyped a quick demo of intel-client-top which produces output like:
neverball[ 6011]: rcs0: 41.01% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00% Xorg[ 5664]: rcs0: 31.16% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00% xfwm4[ 5727]: rcs0: 0.00% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%
+1
+2 for a graph ;)
Quoted 8 lines
As I say in the commit we could also extend this to show the overall engine busyness (via PMU), and also average load as queue-depth (also PMU), in the top header.
Another potential use for the per-client infrastructure is tieing it up with perf PMU. At the moment our perf PMU are global counters only. With the per- client infrastructure it should be possible to make it work in the task mode as well and so enable GPU busyness profiling of single tasks.
ctx->pid can be misleading, as it set on creation, but the context can be transferred over fd to the real client. (Typically that applies to the default context, 0.)
In the back of my head, I thought we would need add-ctx, rm-ctx events for PMU, sort of like how perf tracks new processes and mmaps. -Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoting Chris Wilson (2017-10-25 16:47:13)
Quoted 10 lines
Quoting Tvrtko Ursulin (2017-10-25 16:36:15)
Quoted 5 lines
From: Tvrtko Ursulin <[email protected]>
Another potential use for the per-client infrastructure is tieing it up with perf PMU. At the moment our perf PMU are global counters only. With the per- client infrastructure it should be possible to make it work in the task mode as well and so enable GPU busyness profiling of single tasks.
ctx->pidcan be misleading, as it set on creation, but the context can be transferred over fd to the real client. (Typically that applies to the default context, 0.)
Ok, I see that you update the pid when a new context is created. Still have the likes of libva that may use DRI3 without creating a context itself.
Back to the general niggle; I really would like to avoid adding custom i915 interfaces for this, that should be a last resort if we can find no way through e.g. perf.
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 4 lines · Chris Wilson
Quoting Chris Wilson (2017-10-25 16:47:13)
Quoted 2 lines
Quoting Tvrtko Ursulin (2017-10-25 16:36:15)
Quoted 1 line
From: Tvrtko Ursulin <[email protected]>
Quoted 8 lines
Quoted 5 lines
I've prototyped a quick demo of intel-client-top which produces output like:
neverball[ 6011]: rcs0: 41.01% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00% Xorg[ 5664]: rcs0: 31.16% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00% xfwm4[ 5727]: rcs0: 0.00% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%+1
+2 for a graph ;)
Where are those placement students when you need them! :)
Quoted 11 lines
Quoted 9 lines
Quoted 4 lines
Another potential use for the per-client infrastructure is tieing it up with perf PMU. At the moment our perf PMU are global counters only. With the per- client infrastructure it should be possible to make it work in the task mode as well and so enable GPU busyness profiling of single tasks.
ctx->pidcan be misleading, as it set on creation, but the context can be transferred over fd to the real client. (Typically that applies to the default context, 0.)
Ok, I see that you update the pid when a new context is created. Stillhave the likes of libva that may use DRI3 without creating a context itself.
Hm, how rude of the protocol to provide this anonymization service!
I guess I could update on submission as well and then there is no escape.
Quoted 3 lines
Back to the general niggle; I really would like to avoid adding custom i915 interfaces for this, that should be a last resort if we can find no way through e.g. perf.
I certainly plan to investigate adding pid filtering to the PMU. It is supposed to be possible but I haven't tried it yet. Also not sure if it will be exactly suitable for a top like tool. Will see if I manage to have it working.
But what do you say about the simple per-context API (patch 13)? Do you find using ctx get param for this acceptable or you can think of a different way?
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoting Tvrtko Ursulin (2017-10-26 08:34:24)
Quoted 26 lines · Chris Wilson
Quoted 4 lines
Quoting Chris Wilson (2017-10-25 16:47:13)
Quoted 2 lines
Quoting Tvrtko Ursulin (2017-10-25 16:36:15)
Quoted 1 line
From: Tvrtko Ursulin <[email protected]>
Quoted 8 lines
Quoted 5 lines
I've prototyped a quick demo of intel-client-top which produces output like:
neverball[ 6011]: rcs0: 41.01% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00% Xorg[ 5664]: rcs0: 31.16% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00% xfwm4[ 5727]: rcs0: 0.00% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%+1
+2 for a graph ;)Where are those placement students when you need them! :)
Quoted 9 lines
Quoted 9 lines
Quoted 4 lines
Another potential use for the per-client infrastructure is tieing it up with perf PMU. At the moment our perf PMU are global counters only. With the per- client infrastructure it should be possible to make it work in the task mode as well and so enable GPU busyness profiling of single tasks.
ctx->pidcan be misleading, as it set on creation, but the context can be transferred over fd to the real client. (Typically that applies to the default context, 0.)
Ok, I see that you update the pid when a new context is created. Still
Quoted 6 lines
Quoted 2 lines
have the likes of libva that may use DRI3 without creating a context itself.
Hm, how rude of the protocol to provide this anonymization service!
I guess I could update on submission as well and then there is no escape.
(Just make it conditional; a pid per request was one of the low hanging expenses. In general, I'd rather not use pid here as ctx is our encapsulation, but meh, it's a tid vs pid debate. Answer is usually both and which to use depends on circumstance.)
Quoted 4 lines
Quoted 3 lines
Back to the general niggle; I really would like to avoid adding custom i915 interfaces for this, that should be a last resort if we can find no way through e.g. perf.
Quoted 8 lines
I certainly plan to investigate adding pid filtering to the PMU. It is supposed to be possible but I haven't tried it yet. Also not sure if it will be exactly suitable for a top like tool. Will see if I manage to have it working.
But what do you say about the simple per-context API (patch 13)? Do you find using ctx get param for this acceptable or you can think of a different way?
Certainly not with a struct_mutex! ;)
I can see a parallel to sysinfo for GETPARAM and getrusage for context. We probably want to plan for more than just accumulated gputime though. (An extensible struct?) So yes, if you have something that wants to monitor themselves, we will just have to bite the bullet. -Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 4 lines · Tvrtko Ursulin
Quoted 3 lines · Chris Wilson
Quoting Chris Wilson (2017-10-25 16:47:13)
Quoted 2 lines
Quoting Tvrtko Ursulin (2017-10-25 16:36:15)
Quoted 1 line
From: Tvrtko Ursulin <[email protected]>
Quoted 8 lines
Quoted 7 lines
Quoted 5 lines
I've prototyped a quick demo of intel-client-top which produces output like:
neverball[ 6011]: rcs0: 41.01% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00% Xorg[ 5664]: rcs0: 31.16% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00% xfwm4[ 5727]: rcs0: 0.00% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%+1
+2 for a graph ;)Where are those placement students when you need them! :)
I won't be your student, but I could like to wire this into gputop.
Quoted 27 lines
Quoted 11 lines
Quoted 9 lines
Quoted 5 lines
Another potential use for the per-client infrastructure is tieing it up with perf PMU. At the moment our perf PMU are global counters only. With the per- client infrastructure it should be possible to make it work in the task mode as well and so enable GPU busyness profiling of single tasks.
ctx->pidcan be misleading, as it set on creation, but the context can be transferred over fd to the real client. (Typically that applies to the default context, 0.)
Ok, I see that you update the pid when a new context is created. Stillhave the likes of libva that may use DRI3 without creating a context itself.
Hm, how rude of the protocol to provide this anonymization service!
I guess I could update on submission as well and then there is no escape.
Quoted 3 lines
Back to the general niggle; I really would like to avoid adding custom i915 interfaces for this, that should be a last resort if we can find no way through e.g. perf.
I certainly plan to investigate adding pid filtering to the PMU. It is supposed to be possible but I haven't tried it yet. Also not sure if it will be exactly suitable for a top like tool. Will see if I manage to have it working.
But what do you say about the simple per-context API (patch 13)? Do you find using ctx get param for this acceptable or you can think of a different way?
Quoted 7 lines
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoting Lionel Landwerlin (2017-10-26 10:50:57)
Quoted 7 lines · Tvrtko Ursulin
Quoted 6 lines · Chris Wilson
Quoted 5 lines
Quoting Chris Wilson (2017-10-25 16:47:13)
Quoted 4 lines
Quoting Tvrtko Ursulin (2017-10-25 16:36:15)
Quoted 1 line
From: Tvrtko Ursulin <[email protected]>
I've prototyped a quick demo of intel-client-top which produces output like:
Quoted 8 lines
Quoted 6 lines
Quoted 5 lines
Quoted 3 lines
neverball[ 6011]: rcs0: 41.01% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00% Xorg[ 5664]: rcs0: 31.16% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00% xfwm4[ 5727]: rcs0: 0.00% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%+1
+2 for a graph ;)Where are those placement students when you need them! :)
I won't be your student, but I could like to wire this into gputop.
See intel_gpu_overlay for a set of graphs where this would fit in nicely (but not neatly). It's certainly not a robust user-friendly UI (or code), but for measuring kernel-level activity, there's nothing else that tries to put all the information in the same place. Hint ;)
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 7 lines · Lionel Landwerlin
Quoted 6 lines · Tvrtko Ursulin
Quoted 5 lines · Chris Wilson
Quoting Chris Wilson (2017-10-25 16:47:13)
Quoted 4 lines
Quoting Tvrtko Ursulin (2017-10-25 16:36:15)
Quoted 1 line
From: Tvrtko Ursulin <[email protected]>
I've prototyped a quick demo of intel-client-top which produces output like:
Quoted 8 lines
Quoted 6 lines
Quoted 5 lines
Quoted 3 lines
neverball[ 6011]: rcs0: 41.01% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%
Xorg[ 5664]: rcs0: 31.16% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%
xfwm4[ 5727]: rcs0: 0.00% bcs0: 0.00% vcs0: 0.00% vecs0: 0.00%+1
+2 for a graph ;)Where are those placement students when you need them! :)
I won't be your student, but I could like to wire this into gputop.
I was thinking gputop as well but did find the time to look at it yet.
If you want to play with it, I have uploaded my kernel and igt branches which implement this to below locations*.
But be aware the sysfs interface is at the moment a prototype and we haven't decided we are going with it 100%. So don't invest too much in any experiments you might decide to do. You'll see in the intel_client_top demo that I have also not invested a huge amount to make it nice and polished (and bug free!).
*)
https://cgit.freedesktop.org/~tursulin/drm-intel/log/?h=context-stats
https://cgit.freedesktop.org/~tursulin/intel-gpu-tools/log/?h=context-stats
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoting Tvrtko Ursulin (2017-10-26 14:00:28)
Quoted 16 lines · Lionel Landwerlin
Quoted 14 lines · Tvrtko Ursulin
Quoted 13 lines · Chris Wilson
Quoted 12 lines
Quoting Chris Wilson (2017-10-25 16:47:13)
Quoted 11 lines
Quoting Tvrtko Ursulin (2017-10-25 16:36:15)
Quoted 1 line
From: Tvrtko Ursulin <[email protected]>
I've prototyped a quick demo of intel-client-top which produces output like:
neverball[ 6011]: rcs0: 41.01% bcs0: 0.00% vcs0:
0.00% vecs0: 0.00%
Xorg[ 5664]: rcs0: 31.16% bcs0: 0.00% vcs0:
0.00% vecs0: 0.00%
xfwm4[ 5727]: rcs0: 0.00% bcs0: 0.00% vcs0:
0.00% vecs0: 0.00%
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
Quoted 2 lines
+1
+2 for a graph ;)Where are those placement students when you need them! :)
I won't be your student, but I could like to wire this into gputop.
I was thinking gputop as well but did find the time to look at it yet.
We don't even ship gputop or the perf generator in igt... Can we at least make noises towards owning that code...
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 16 lines · Chris Wilson
Quoting Tvrtko Ursulin (2017-10-26 14:00:28)
Quoted 15 lines · Lionel Landwerlin
Quoted 14 lines · Tvrtko Ursulin
Quoted 13 lines · Chris Wilson
Quoted 12 lines
Quoting Chris Wilson (2017-10-25 16:47:13)
Quoted 11 lines
Quoting Tvrtko Ursulin (2017-10-25 16:36:15)
Quoted 1 line
From: Tvrtko Ursulin <[email protected]>
I've prototyped a quick demo of intel-client-top which produces output like:
neverball[ 6011]: rcs0: 41.01% bcs0: 0.00% vcs0:
0.00% vecs0: 0.00%
Xorg[ 5664]: rcs0: 31.16% bcs0: 0.00% vcs0:
0.00% vecs0: 0.00%
xfwm4[ 5727]: rcs0: 0.00% bcs0: 0.00% vcs0:
0.00% vecs0: 0.00%
Quoted 9 lines
Quoted 5 lines
Quoted 4 lines
Quoted 3 lines
Quoted 2 lines
+1
+2 for a graph ;)Where are those placement students when you need them! :)
I won't be your student, but I could like to wire this into gputop.
I was thinking gputop as well but did find the time to look at it yet.
We don't even ship gputop or the perf generator in igt... Can we at least make noises towards owning that code...
-Chris
It would be nice to have stuff in single repo but gputop has quite a few dependencies that I'm not sure igt will want.
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoting Lionel Landwerlin (2017-10-26 18:13:13)
Quoted 20 lines · Chris Wilson
Quoted 19 lines
Quoting Tvrtko Ursulin (2017-10-26 14:00:28)
Quoted 18 lines · Lionel Landwerlin
Quoted 17 lines · Tvrtko Ursulin
Quoted 16 lines · Chris Wilson
Quoted 6 lines
Quoting Chris Wilson (2017-10-25 16:47:13)
Quoted 5 lines
Quoting Tvrtko Ursulin (2017-10-25 16:36:15)
Quoted 1 line
From: Tvrtko Ursulin <[email protected]>
I've prototyped a quick demo of intel-client-top which produces output like:
Quoted 8 lines
Quoted 6 lines
neverball[ 6011]: rcs0: 41.01% bcs0: 0.00% vcs0:
0.00% vecs0: 0.00%
Xorg[ 5664]: rcs0: 31.16% bcs0: 0.00% vcs0:
0.00% vecs0: 0.00%
xfwm4[ 5727]: rcs0: 0.00% bcs0: 0.00% vcs0:
0.00% vecs0: 0.00%+1
+2 for a graph ;)Where are those placement students when you need them! :)
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
Quoted 1 line
I won't be your student, but I could like to wire this into gputop.
I was thinking gputop as well but did find the time to look at it yet.
We don't even ship gputop or the perf generator in igt... Can we at least make noises towards owning that code...
-ChrisIt would be nice to have stuff in single repo but gputop has quite a few dependencies that I'm not sure igt will want.
Just add the dependencies as optional to the build scripts; we don't have to add them to the common libs or make them mandatory except if we want to build all the tools. (If they are that bad, just pull it in as a submodule.) But it would be nice to exploit the synergies between the existing tools and test/perf harnesses; even if long term ubergpuprofiler takes over as the defacto tool for all gpus.
And we have to purge the current intel_gpu_top; killing machines since 2011.
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 36 lines · Chris Wilson
Quoting Lionel Landwerlin (2017-10-26 18:13:13)
Quoted 20 lines · Chris Wilson
Quoted 19 lines
Quoting Tvrtko Ursulin (2017-10-26 14:00:28)
Quoted 18 lines · Lionel Landwerlin
Quoted 17 lines · Tvrtko Ursulin
Quoted 16 lines · Chris Wilson
Quoted 6 lines
Quoting Chris Wilson (2017-10-25 16:47:13)
Quoted 5 lines
Quoting Tvrtko Ursulin (2017-10-25 16:36:15)
Quoted 1 line
From: Tvrtko Ursulin <[email protected]>
I've prototyped a quick demo of intel-client-top which produces output like:
Quoted 8 lines
Quoted 6 lines
neverball[ 6011]: rcs0: 41.01% bcs0: 0.00% vcs0:
0.00% vecs0: 0.00%
Xorg[ 5664]: rcs0: 31.16% bcs0: 0.00% vcs0:
0.00% vecs0: 0.00%
xfwm4[ 5727]: rcs0: 0.00% bcs0: 0.00% vcs0:
0.00% vecs0: 0.00%+1
+2 for a graph ;)Where are those placement students when you need them! :)
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
Quoted 1 line
I won't be your student, but I could like to wire this into gputop.
I was thinking gputop as well but did find the time to look at it yet.
We don't even ship gputop or the perf generator in igt... Can we at least make noises towards owning that code...
-ChrisIt would be nice to have stuff in single repo but gputop has quite a few dependencies that I'm not sure igt will want.
Just add the dependencies as optional to the build scripts; we don't have to add them to the common libs or make them mandatory except if we want to build all the tools. (If they are that bad, just pull it in as a submodule.) But it would be nice to exploit the synergies between the existing tools and test/perf harnesses; even if long term ubergpuprofiler takes over as the defacto tool for all gpus.
Quoted 4 lines
And we have to purge the current
intel_gpu_top; killing machines since 2011.
-Chris
It's just a massive amount of deps right now.
Including: node, emscripten, protobuf, a websocket lib, libuv and more.
I also had the good taste of pulling in some bits of mesa for the device descriptions (which contains bits that igt doesn't have). It's hard to look forward to improve all of that when there are cool features to implement.
Completely agree on the synergy part. I'll try to work towards that.
-
Lionel
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.BAT: failure for Per-context and per-client engine busyness
In reply to Tvrtko Ursulin== Series Details ==
== Series Details ==
Series: Per-context and per-client engine busyness
URL : https://patchwork.freedesktop.org/series/32645/
State : failure
== Summary ==
Series 32645v1 Per-context and per-client engine busyness
https://patchwork.freedesktop.org/api/1.0/series/32645/revisions/1/mbox/
Test chamelium:
Subgroup dp-hpd-fast:
skip -> INCOMPLETE (fi-gdg-551)
skip -> INCOMPLETE (fi-blb-e6850)
skip -> INCOMPLETE (fi-pnv-d510)
skip -> INCOMPLETE (fi-bwr-2160)
skip -> INCOMPLETE (fi-elk-e7500)
skip -> INCOMPLETE (fi-ilk-650)
Test kms_busy:
Subgroup basic-flip-c:
incomplete -> PASS (fi-bxt-j4205)
Test kms_pipe_crc_basic:
Subgroup read-crc-pipe-b:
incomplete -> PASS (fi-cnl-y)fi-bdw-5557u total:289 pass:268 dwarn:0 dfail:0 fail:0 skip:21 time:451s fi-bdw-gvtdvm total:289 pass:265 dwarn:0 dfail:0 fail:0 skip:24 time:445s fi-blb-e6850 total:1 pass:0 dwarn:0 dfail:0 fail:0 skip:0 fi-bsw-n3050 total:289 pass:243 dwarn:0 dfail:0 fail:0 skip:46 time:516s fi-bwr-2160 total:1 pass:0 dwarn:0 dfail:0 fail:0 skip:0 fi-bxt-dsi total:289 pass:259 dwarn:0 dfail:0 fail:0 skip:30 time:509s fi-bxt-j4205 total:289 pass:260 dwarn:0 dfail:0 fail:0 skip:29 time:510s fi-cfl-s total:289 pass:253 dwarn:4 dfail:0 fail:0 skip:32 time:596s fi-cnl-y total:289 pass:262 dwarn:0 dfail:0 fail:0 skip:27 time:625s fi-elk-e7500 total:1 pass:0 dwarn:0 dfail:0 fail:0 skip:0 fi-gdg-551 total:1 pass:0 dwarn:0 dfail:0 fail:0 skip:0 fi-glk-1 total:289 pass:261 dwarn:0 dfail:0 fail:0 skip:28 time:593s fi-glk-dsi total:289 pass:258 dwarn:0 dfail:0 fail:1 skip:30 time:497s fi-ilk-650 total:1 pass:0 dwarn:0 dfail:0 fail:0 skip:0 fi-kbl-7500u total:289 pass:264 dwarn:1 dfail:0 fail:0 skip:24 time:487s fi-kbl-7560u total:289 pass:270 dwarn:0 dfail:0 fail:0 skip:19 time:569s fi-kbl-7567u total:289 pass:269 dwarn:0 dfail:0 fail:0 skip:20 time:477s fi-kbl-r total:289 pass:262 dwarn:0 dfail:0 fail:0 skip:27 time:607s fi-pnv-d510 total:1 pass:0 dwarn:0 dfail:0 fail:0 skip:0 fi-skl-6260u total:289 pass:269 dwarn:0 dfail:0 fail:0 skip:20 time:456s fi-skl-6600u total:289 pass:262 dwarn:0 dfail:0 fail:0 skip:27 time:596s fi-skl-6700hq total:289 pass:263 dwarn:0 dfail:0 fail:0 skip:26 time:678s fi-skl-6700k total:289 pass:265 dwarn:0 dfail:0 fail:0 skip:24 time:820s fi-skl-6770hq total:289 pass:269 dwarn:0 dfail:0 fail:0 skip:20 time:515s fi-skl-gvtdvm total:289 pass:266 dwarn:0 dfail:0 fail:0 skip:23 time:445s
5e39e3539f6330cf7d08cc83d34bc693f0be8920 drm-tip: 2017y-10m-25d-13h-19m-05s UTC integration manifest 8af669aa9fba drm/i915: Add sysfs toggle to enable per-client engine stats 64c0a4cd0f38 drm/i915: Expose per-engine client busynessfdfbe3ea421f drm/i915: Update client name on context create3e74faecd529 drm/i915: Expose list of clients in sysfs05406c098c15 drm/i915: Allow clients to query own per-engine busynessa5e0ad392563 drm/i915: Track per-context engine busynessd6d4d00164a1 drm/i915/pmu: Add queued counter0e0084c7ee2f drm/i915: Keep a count of requests waiting for a slot on GPU 2be78d207cb2 drm/i915/pmu: Add RC6 residency metrics6bac29bad85e drm/i915: Convert intel_rc6_residency_us to ns1601eac359aa drm/i915/pmu: Add interrupt count metric28ca08373489 drm/i915/pmu: Wire up engine busy stats to PMUb4fd8b1d62d0 drm/i915: Engine busy time trackingf47889163b37 drm/i915: Wrap context schedule notificationaaf52c17699a drm/i915/pmu: Suspend sampling when GPU is idle46ce4f2b1959 drm/i915/pmu: Expose a PMU interface for perf queriesb9a9c1e05ebb drm/i915: Extract intel_get_cagf
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_6187/
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx