summaryrefslogtreecommitdiff
path: root/include/linux/debugobjects.h
diff options
context:
space:
mode:
authorMatt Roper <matthew.d.roper@intel.com>2026-06-26 14:53:28 -0700
committerMatt Roper <matthew.d.roper@intel.com>2026-06-30 08:11:46 -0700
commit483c9f54515922398bd0dbca72c6194cd333685a (patch)
tree2d8f178440c5ec907418514be38f7f75a19f528f /include/linux/debugobjects.h
parente459a3bdeb117be496d7f229e2ea1f6c9fe4080b (diff)
drm/xe/tests/rtp: Add kunit test for whitelist upper bounds
Xe must only add registers to the GT whitelist if they are listed in the "Software Allowlist" section of the bspec. These registers have been carefully reviewed by the architecture/security teams to ensure that they are safe to whitelist from a security perspective. The list of allowed registers changes from platform to platform, and it is not safe to assume that a register is safe to whitelist on a new platform/IP just because it was whitelisted on older ones. This means that whitelist entries in the driver that used undefined upper bounds (XE_RTP_END_VERSION_UNDEFINED) for their version ranges should always be considered illegal since they could potentially open unexpected security holes on future platforms. Add a kunit test to scan the whitelist RTP table and ensure that all entries have well-defined upper bounds on IP version ranges. Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com> Link: https://patch.msgid.link/20260626-kunit_whitelist_bounds-v3-1-aedf0b3adab9@intel.com Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Diffstat (limited to 'include/linux/debugobjects.h')
0 files changed, 0 insertions, 0 deletions