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 - Neither keys or values are 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 - <str> - String excluding any above defined reserved characters or whitespace.
45 ---------------------------------
47 - drm-driver: <str>
53 --------------------------------
55 - drm-pdev: <aaaa:bb.cc.d>
60 - drm-client-id: <uint>
67 scope of each device, in which case `drm-pdev` shall be present as well.
72 - drm-engine-<str>: <uint> ns
75 and unique name (str), with possible values documented in the driver specific
78 Value shall be in specified time units which the respective GPU engine spent
87 - drm-engine-capacity-<str>: <uint>
89 Engine identifier string must be the same as the one specified in the
90 drm-engine-<str> tag and shall contain a greater than zero number in case the
91 exported engine corresponds to a group of identical hardware engines.
96 - drm-memory-<str>: <uint> [KiB|MiB]
106 indicating kibi- or mebi-bytes.
108 - drm-cycles-<str> <uint>
110 Engine identifier string must be the same as the one specified in the
111 drm-engine-<str> tag and shall contain the number of busy cycles for the given
112 engine.
120 - drm-maxfreq-<str> <uint> [Hz|MHz|KHz]
122 Engine identifier string must be the same as the one specified in the
123 drm-engine-<str> tag and shall contain the maximum frequency for the given
124 engine.  Taken together with drm-cycles-<str>, this can be used to calculate
125 percentage utilization of the engine, whereas drm-engine-<str> only reflects
126 time active without considering what frequency the engine is operating as a
130 Driver specific implementations
133 :ref:`i915-usage-stats`