Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kevin.rogovin@intel.com
To: intel-gfx@lists.freedesktop.org
Cc: Kevin Rogovin <kevin.rogovin@intel.com>
Subject: [PATCH 1/3] drm-uapi: define interface to kernel for scratch page read
Date: Tue,  5 Dec 2017 09:48:12 +0200	[thread overview]
Message-ID: <1512460094-4615-2-git-send-email-kevin.rogovin@intel.com> (raw)
In-Reply-To: <1512460094-4615-1-git-send-email-kevin.rogovin@intel.com>

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

---
 include/drm-uapi/i915_drm.h | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/include/drm-uapi/i915_drm.h b/include/drm-uapi/i915_drm.h
index 890df227ae..3a9c3a2d0c 100644
--- a/include/drm-uapi/i915_drm.h
+++ b/include/drm-uapi/i915_drm.h
@@ -262,6 +262,8 @@ typedef struct _drm_i915_sarea {
 #define DRM_I915_PERF_OPEN		0x36
 #define DRM_I915_PERF_ADD_CONFIG	0x37
 #define DRM_I915_PERF_REMOVE_CONFIG	0x38
+#define DRM_I915_READ_SCRATCH_PAGE      0x39
+#define DRM_I915_WRITE_SCRATCH_PAGE     0x40
 
 #define DRM_IOCTL_I915_INIT		DRM_IOW( DRM_COMMAND_BASE + DRM_I915_INIT, drm_i915_init_t)
 #define DRM_IOCTL_I915_FLUSH		DRM_IO ( DRM_COMMAND_BASE + DRM_I915_FLUSH)
@@ -319,6 +321,8 @@ typedef struct _drm_i915_sarea {
 #define DRM_IOCTL_I915_PERF_OPEN	DRM_IOW(DRM_COMMAND_BASE + DRM_I915_PERF_OPEN, struct drm_i915_perf_open_param)
 #define DRM_IOCTL_I915_PERF_ADD_CONFIG	DRM_IOW(DRM_COMMAND_BASE + DRM_I915_PERF_ADD_CONFIG, struct drm_i915_perf_oa_config)
 #define DRM_IOCTL_I915_PERF_REMOVE_CONFIG	DRM_IOW(DRM_COMMAND_BASE + DRM_I915_PERF_REMOVE_CONFIG, __u64)
+#define DRM_IOCTL_I915_READ_SCRATCH_PAGE        DRM_IOWR (DRM_COMMAND_BASE + DRM_I915_READ_SCRATCH_PAGE, struct drm_i915_scratch_page)
+#define DRM_IOCTL_I915_WRITE_SCRATCH_PAGE       DRM_IOWR (DRM_COMMAND_BASE + DRM_I915_WRITE_SCRATCH_PAGE, struct drm_i915_scratch_page)
 
 /* Allow drivers to submit batchbuffers directly to hardware, relying
  * on the security mechanisms provided by hardware.
@@ -1535,6 +1539,33 @@ struct drm_i915_perf_oa_config {
 	__u64 flex_regs_ptr;
 };
 
+/**
+ * Structure to read/write scratch page of PPGTT. Read and writing
+ * values are not reliable unless the calling application guarantees
+ * that no batchbuffer that could read or write the scratch is in
+ * flight using the PPGTT between the time the ioctl is issued and
+ * it returns.
+ */
+struct drm_i915_scratch_page {
+   /**
+    * size in bytes of the backing store pointed to by buffer_ptr;
+    * kernel will return the actual size of the scratch page in
+    * this field as well.
+    */
+   __u32 buffer_size;
+
+   /**
+    * Pointer data with which to upload to or download from the
+    * scratch page; if the buffer size behind buffer_ptr is
+    * smaller than the scratch page size, then only the first
+    * buffer_size bytes are read or written. If the scratch
+    * page size is greater than buffer_size, then the bytes
+    * past the scratch page size in buffer behind bufer_ptr
+    * are not read or writte.
+    */
+   __u64 buffer_ptr;
+};
+
 #if defined(__cplusplus)
 }
 #endif
-- 
2.15.0

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

  reply	other threads:[~2017-12-05  7:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05  7:48 [PATCH 0/3] RFC: Scratch page checking kevin.rogovin
2017-12-05  7:48 ` kevin.rogovin [this message]
2017-12-05  7:57   ` [PATCH 1/3] drm-uapi: define interface to kernel for scratch page read Rogovin, Kevin
2017-12-05  7:48 ` [PATCH 2/3] i965: define stuff for scratch page checking in intel_screen kevin.rogovin
2017-12-05  7:58   ` Rogovin, Kevin
2017-12-05  7:48 ` [PATCH 3/3] i965: check scratch page in a locked fashion on each ioctl kevin.rogovin
2017-12-05 10:07   ` Chris Wilson
2017-12-05 10:30     ` Rogovin, Kevin
2017-12-05 10:39       ` Chris Wilson
2017-12-05 10:41         ` Rogovin, Kevin
2017-12-05 13:59           ` Joonas Lahtinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1512460094-4615-2-git-send-email-kevin.rogovin@intel.com \
    --to=kevin.rogovin@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox