[PATCH 0/3] RFC: Scratch page checking

[kevin.rogovin@intel.com]

From: Kevin Rogovin <kevin.rogovin@intel.com>

This patch series proposes a new kernel interface for user
space to read and write the values of the scratch page for
a PPGTT. The user space is expected to guarantee (via its
own locking mechanism) that nothing shall read or write to
the scratch page for the duration of the ioctl's to read
or write the scratch page values. The purpose for user space
to read and write the scratch page values is to help see if
an out-of-bound write was done to the scratch page by the
GPU; from the point of view of GL, this can be used to help
detect if an application performs an out-of-bounds write to
an SSBO.

Patch 1 defines the kernel interface
Patches 2-3 implement the debug option in i965 to check for
inadvertent scratch page writes by the GPU.

Kevin Rogovin (3):
  drm-uapi: define interface to kernel for scratch page read
  i965: define stuff for scratch page checking in intel_screen
  i965: check scratch page in a locked fashion on each ioctl

 include/drm-uapi/i915_drm.h                   | 31 +++++++++++++++++++++++++++
 src/intel/common/gen_debug.c                  |  1 +
 src/intel/common/gen_debug.h                  |  1 +
 src/mesa/drivers/dri/i965/intel_batchbuffer.c | 27 ++++++++++++++++++++++-
 src/mesa/drivers/dri/i965/intel_screen.c      | 26 ++++++++++++++++++++++
 src/mesa/drivers/dri/i965/intel_screen.h      | 12 +++++++++++
 6 files changed, 97 insertions(+), 1 deletion(-)

-- 
2.15.0

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx