[PATCH 0/4] Start fixing OA whitelist mistakes

[Matt Roper <matthew.d.roper@intel.com>]

There are a number of mistakes in the OA register whitelists:
 - Unlimited upper bounds (never allowed for whitelists entries!)
 - Whitelisting registers that userspace already has access to
 - Whitelisting registers that userspace is not intended to ever need
   access to

Correct the first two bullets above.  The third bullet will need more
investigation to determine whether any userspace has developed an
unnecessary and unwanted dependency on these registers (in which case we
can't easily take them away without breaking userspace).

Going forward we should also probably unmacro-ize these OA entries
because they make it harder to see exactly which register(s) are being
whitelisted and harder to audit against the formally allowed lists.


Matt Roper (4):
  drm/xe/oa: Stop whitelisting MMIO_TRG registers on non-DG2
  drm/xe/oa: Stop whitelisting OAG_OASTATUS
  drm/xe/oa: Stop whitelisting OAM registers on non Xe2/Xe3
  drm/xe/oa: Stop whitelisting OAG registers after Xe3

 drivers/gpu/drm/xe/xe_reg_whitelist.c | 41 +++++++++++++++------------
 1 file changed, 23 insertions(+), 18 deletions(-)

-- 
2.52.0