From: Matthew Auld <matthew.auld@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 2/5] drm/i915/uapi: convert drm_i915_gem_madvise to kernel-doc
Date: Tue, 13 Jul 2021 11:45:51 +0100 [thread overview]
Message-ID: <20210713104554.2381406-2-matthew.auld@intel.com> (raw)
In-Reply-To: <20210713104554.2381406-1-matthew.auld@intel.com>
Add some kernel doc for this. We can then just reference this later when
documenting madv in the kernel.
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Daniel Vetter <daniel@ffwll.ch>
---
include/uapi/drm/i915_drm.h | 50 +++++++++++++++++++++++++++++++------
1 file changed, 42 insertions(+), 8 deletions(-)
diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h
index e334a8b14ef2..a839085b6577 100644
--- a/include/uapi/drm/i915_drm.h
+++ b/include/uapi/drm/i915_drm.h
@@ -1492,20 +1492,54 @@ struct drm_i915_get_pipe_from_crtc_id {
__u32 pipe;
};
-#define I915_MADV_WILLNEED 0
-#define I915_MADV_DONTNEED 1
-#define __I915_MADV_PURGED 2 /* internal state */
-
+/**
+ * struct drm_i915_gem_madvise - Update the madvise hint for the object.
+ *
+ * The kernel uses this to know when it can safely discard the backing pages for
+ * an object, when under memory pressure.
+ */
struct drm_i915_gem_madvise {
- /** Handle of the buffer to change the backing store advice */
+ /**
+ * @handle: Handle of the buffer to change the backing store advice for.
+ */
__u32 handle;
- /* Advice: either the buffer will be needed again in the near future,
- * or wont be and could be discarded under memory pressure.
+ /**
+ * @madv: The madvise hint to set for the object.
+ *
+ * Supported values:
+ *
+ * I915_MADV_WILLNEED:
+ *
+ * The buffer will be needed again in the near future. By default all
+ * objects are set as I915_MADV_WILLNEED. Once the pages become
+ * dirty, the kernel is no longer allowed to simply discard the pages,
+ * and instead can only resort to swapping the pages out, if under
+ * memory pressure, where the page contents must persist when swapping
+ * the pages back in.
+ *
+ * I915_MADV_DONTNEED:
+ *
+ * The buffer wont be needed. The pages and their contents can be
+ * discarded under memory pressure.
+ *
+ * Note that if the pages were discarded then the kernel updates the
+ * internal madvise value of the object to __I915_MADV_PURGED, which
+ * effectively kills the object, since all further requests to allocate
+ * pages for the object will be rejected. At this point a new object is
+ * needed. This will be reflected in @retained.
*/
+#define I915_MADV_WILLNEED 0
+#define I915_MADV_DONTNEED 1
+#define __I915_MADV_PURGED 2 /* internal state */
__u32 madv;
- /** Whether the backing store still exists. */
+ /**
+ * @retained: Whether the backing store still exists.
+ *
+ * Set to false if the kernel purged the object and marked the object as
+ * __I915_MADV_PURGED.
+ */
__u32 retained;
};
--
2.26.3
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-07-13 10:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 10:45 [Intel-gfx] [PATCH 1/5] drm/i915: document caching related bits Matthew Auld
2021-07-13 10:45 ` Matthew Auld [this message]
2021-07-13 10:45 ` [Intel-gfx] [PATCH 3/5] drm/i915: convert drm_i915_gem_object to kernel-doc Matthew Auld
2021-07-13 10:45 ` [Intel-gfx] [PATCH 4/5] drm/i915: pull in some more kernel-doc Matthew Auld
2021-07-13 10:45 ` [Intel-gfx] [PATCH 5/5] drm/i915/ehl: unconditionally flush the pages on acquire Matthew Auld
2021-07-14 11:19 ` Daniel Vetter
2021-07-13 11:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915: document caching related bits Patchwork
2021-07-13 11:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-13 11:41 ` [Intel-gfx] [PATCH 1/5] " Mika Kuoppala
2021-07-13 12:59 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/5] " Patchwork
2021-07-13 15:55 ` [Intel-gfx] [PATCH 1/5] " Ville Syrjälä
2021-07-13 16:13 ` Matthew Auld
2021-07-13 16:50 ` Daniel Vetter
2021-07-13 17:47 ` Ville Syrjälä
2021-07-13 18:24 ` Matthew Auld
2021-07-13 18:46 ` Ville Syrjälä
2021-07-14 11:16 ` Daniel Vetter
2021-07-14 11:42 ` Ville Syrjälä
2021-07-14 12:08 ` Ville Syrjälä
2021-07-14 12:57 ` Daniel Vetter
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=20210713104554.2381406-2-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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