Lines Matching +full:panfrost +full:- +full:gpu

1 .. _drm-client-usage-stats:
8 `fops->show_fdinfo()` as part of the driver specific file operations registered
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 ---------
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
90 Value shall be in specified time units which the respective GPU engine spent
99 - drm-engine-capacity-<keystr>: <uint>
102 drm-engine-<keystr> tag and shall contain a greater than zero number in case the
108 - drm-cycles-<keystr>: <uint>
111 drm-engine-<keystr> tag and shall contain the number of busy cycles for the given
120 - drm-total-cycles-<keystr>: <uint>
123 drm-cycles-<keystr> tag and shall contain the total number cycles for the given
126 This is a timestamp in GPU unspecified unit that matches the update rate
127 of drm-cycles-<keystr>. For drivers that implement this interface, the engine
128 utilization can be calculated entirely on the GPU clock domain, without
131 A driver may implement either this key or drm-maxfreq-<keystr>, but not both.
133 - drm-maxfreq-<keystr>: <uint> [Hz|MHz|KHz]
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
142 A driver may implement either this key or drm-total-cycles-<keystr>, but not
148 Each possible memory type which can be used to store buffer objects by the GPU
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]
209 -------------------------------
211 * :ref:`i915-usage-stats`
212 * :ref:`panfrost-usage-stats`
213 * :ref:`panthor-usage-stats`
214 * :ref:`xe-usage-stats`