From: Matthew Brost <matthew.brost@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH 1/4] xe: Update to latest uAPI
Date: Wed, 15 Mar 2023 19:32:47 -0700 [thread overview]
Message-ID: <20230316023250.4115730-2-matthew.brost@intel.com> (raw)
In-Reply-To: <20230316023250.4115730-1-matthew.brost@intel.com>
Needed to test NULL VM binds.
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
---
include/drm-uapi/xe_drm.h | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/include/drm-uapi/xe_drm.h b/include/drm-uapi/xe_drm.h
index 593b01ba..4bde1087 100644
--- a/include/drm-uapi/xe_drm.h
+++ b/include/drm-uapi/xe_drm.h
@@ -446,6 +446,14 @@ struct drm_xe_vm_bind_op {
* than differing the MAP to the page fault handler.
*/
#define XE_VM_BIND_FLAG_IMMEDIATE (0x1 << 18)
+ /*
+ * When the NULL flag is set, the page tables are setup with a special
+ * bit which indicates writes are dropped and all reads return zero. The
+ * NULL flags is only valid for XE_VM_BIND_OP_MAP operations, the BO
+ * handle MBZ, and the BO offset MBZ. This flag is intended to implement
+ * VK sparse bindings.
+ */
+#define XE_VM_BIND_FLAG_NULL (0x1 << 19)
/** @reserved: Reserved */
__u64 reserved[2];
--
2.34.1
next prev parent reply other threads:[~2023-03-16 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 2:32 [igt-dev] [PATCH 0/4] Test GPUVA and NULL VM binds Matthew Brost
2023-03-16 2:32 ` Matthew Brost [this message]
2023-03-16 2:32 ` [igt-dev] [PATCH 2/4] xe_exec_basic: Add NULL VM bind section Matthew Brost
2023-03-16 2:32 ` [igt-dev] [PATCH 3/4] xe_vm: MMAP style VM binds section Matthew Brost
2023-03-16 2:32 ` [igt-dev] [PATCH 4/4] xe_vm: Add mmap / munmap sections that split large pages Matthew Brost
2023-03-16 3:07 ` [igt-dev] ✗ GitLab.Pipeline: warning for Test GPUVA and NULL VM binds (rev2) Patchwork
2023-03-16 3:27 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-03-16 8:55 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20230316023250.4115730-2-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=igt-dev@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