Hi,
This series introduces a way for applications to read local memory
information via files in the sysfs. So far the only way to do this was
via i915_query ioctl. This is slightly less handy than sysfs for
external users. Additionally, the ioctl has a capability check which
limits which users of a system might use it to get information.
The goals of this series are:
1) Introduce a simpler interface to access lmem information,
2) Lift the CAP_PERFMON check on that information, OR provide
the administrator with a way to optionally lift it.
The first patch introduces the general mechanism without protections.
This will effectively lift a capability check on obtaining the memory
information. The second patch introduces that check back inside the
_show() functions, but also adds a sysctl parameter allowing to override
the checks, if an administrator so decides.
I'm sending this as RFC because I have a feeling that there's no
consensus whether memory information exposed in the patch should be
protected or not. Showing it to any user is strictly speaking an info
leak, but the severity thereof might be considered not that high, so I'd
rather leave it up to discussion first.
If we decide for lifting the check, the first patch is sufficient. If we
decide against it, the second patch protects the information by default,
but with a way to expose it as a conscious decision of the admin. I find
it a decent compromise.
This change has been requested in these parallel issues for i915 and Xe:
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14153
https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/4861
Thanks
Krzysztof
Krzysztof Niemiec (2):
drm/i915: Expose local memory information via sysfs
drm/i915: Add protections to sysfs local memory information
drivers/gpu/drm/i915/i915_sysfs.c | 6 +
drivers/gpu/drm/i915/intel_memory_region.c | 136 +++++++++++++++++++++
drivers/gpu/drm/i915/intel_memory_region.h | 3 +
3 files changed, 145 insertions(+)
--
2.45.2
_
