Lines Matching +full:engine +full:- +full:specific

1 .. _drm-client-usage-stats:
8 `fops->show_fdinfo()` as part of the driver specific file operations registered
15 output is split between common and driver specific parts. Having said that,
22 - File shall contain one key value pair per one line of text.
23 - Colon character (`:`) must be used to delimit keys and values.
24 - All keys shall be prefixed with `drm-`.
25 - Whitespace between the delimiter and first non-whitespace character shall be
27 - Keys are not allowed to contain whitespace characters.
28 - Numerical key value pairs can end with optional unit string.
29 - Data type of the value is fixed as defined in the specification.
32 ---------
36 3. Driver specific.
39 ----------
41 - <uint> - Unsigned integer without defining the maximum value.
42 - <keystr> - String excluding any above defined reserved characters or whitespace.
43 - <valstr> - String.
46 ---------------------------------
48 - drm-driver: <valstr>
54 --------------------------------
59 - drm-pdev: <aaaa:bb.cc.d>
64 - drm-client-id: <uint>
71 scope of each device, in which case `drm-pdev` shall be present as well.
76 - drm-client-name: <valstr>
84 - drm-engine-<keystr>: <uint> ns
87 and unique name (keystr), with possible values documented in the driver specific
90 Value shall be in specified time units which the respective GPU engine spent
99 - drm-engine-capacity-<keystr>: <uint>
101 Engine identifier string must be the same as the one specified in the
102 drm-engine-<keystr> tag and shall contain a greater than zero number in case the
103 exported engine corresponds to a group of identical hardware engines.
108 - drm-cycles-<keystr>: <uint>
110 Engine identifier string must be the same as the one specified in the
111 drm-engine-<keystr> tag and shall contain the number of busy cycles for the given
112 engine.
120 - drm-total-cycles-<keystr>: <uint>
122 Engine identifier string must be the same as the one specified in the
123 drm-cycles-<keystr> tag and shall contain the total number cycles for the given
124 engine.
127 of drm-cycles-<keystr>. For drivers that implement this interface, the engine
131 A driver may implement either this key or drm-maxfreq-<keystr>, but not both.
133 - drm-maxfreq-<keystr>: <uint> [Hz|MHz|KHz]
135 Engine identifier string must be the same as the one specified in the
136 drm-engine-<keystr> tag and shall contain the maximum frequency for the given
137 engine.  Taken together with drm-cycles-<keystr>, this can be used to calculate
138 percentage utilization of the engine, whereas drm-engine-<keystr> only reflects
139 time active without considering what frequency the engine is operating as a
142 A driver may implement either this key or drm-total-cycles-<keystr>, but not
158 indicating kibi- or mebi-bytes.
160 - drm-total-<region>: <uint> [KiB|MiB]
164 instantiated to count under this category. To avoid double-counting, if a buffer
168 - drm-shared-<region>: <uint> [KiB|MiB]
171 than one handle). The same requirement to avoid double-counting that applies to
172 drm-total-<region> also applies here.
174 - drm-resident-<region>: <uint> [KiB|MiB]
179 - drm-memory-<region>: <uint> [KiB|MiB]
182 drm-resident-<region>.
184 - drm-purgeable-<region>: <uint> [KiB|MiB]
192 - drm-active-<region>: <uint> [KiB|MiB]
205 are not provided by drm_show_fdinfo().  But even driver specific stats should
208 Driver specific implementations
209 -------------------------------
211 * :ref:`i915-usage-stats`
212 * :ref:`panfrost-usage-stats`
213 * :ref:`panthor-usage-stats`
214 * :ref:`xe-usage-stats`