From: Tejas Upadhyay <tejas.upadhyay@intel.com>
To: igt-dev@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Tejas Upadhyay <tejas.upadhyay@intel.com>
Subject: [PATCH 3/4] include/intel_drm_local.h: Add DRM_XE_MMAP_OFFSET_FLAG_PCI_BARRIER
Date: Wed, 13 Nov 2024 19:40:11 +0530 [thread overview]
Message-ID: <20241113141012.1362064-4-tejas.upadhyay@intel.com> (raw)
In-Reply-To: <20241113141012.1362064-1-tejas.upadhyay@intel.com>
For now dump into intel_drm_local.h. Once the uapi on the kernel side is
merged, and is part of drm-next, we can sync the kernel headers and
remove this.
Signed-off-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
---
include/drm-uapi-experimental/intel_drm_local.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/drm-uapi-experimental/intel_drm_local.h b/include/drm-uapi-experimental/intel_drm_local.h
index 1773c649b..4afe588ec 100644
--- a/include/drm-uapi-experimental/intel_drm_local.h
+++ b/include/drm-uapi-experimental/intel_drm_local.h
@@ -20,6 +20,8 @@ extern "C" {
* clean these up when kernel uapi headers are sync'd.
*/
+#define DRM_XE_MMAP_OFFSET_FLAG_PCI_BARRIER (1 << 0)
+
#if defined(__cplusplus)
}
#endif
--
2.34.1
next prev parent reply other threads:[~2024-11-13 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 14:10 [PATCH 0/4] Add pci_membarrier test in xe_mmap Tejas Upadhyay
2024-11-13 14:10 ` [PATCH 1/4] lib/i915_drm_local: Remove macros added via merged kernel Tejas Upadhyay
2024-11-13 14:10 ` [PATCH 2/4] include/drm-uapi-experimental: Move i915_drm_local.h to drm-uapi-experimental Tejas Upadhyay
2024-11-13 14:10 ` Tejas Upadhyay [this message]
2024-11-13 14:10 ` [PATCH 4/4] tests/xe/mmap: add tests for pci mem barrier Tejas Upadhyay
2024-11-13 16:24 ` ✗ CI.Patch_applied: failure for Add pci_membarrier test in xe_mmap Patchwork
2024-11-14 4:58 ` [PATCH 0/4] " Upadhyay, Tejas
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=20241113141012.1362064-4-tejas.upadhyay@intel.com \
--to=tejas.upadhyay@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-xe@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