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>,
Matthew Auld <matthew.auld@intel.com>
Subject: [i-g-t V2 3/4] include/intel_drm_local.h: Add DRM_XE_MMAP_OFFSET_FLAG_PCI_BARRIER
Date: Mon, 18 Nov 2024 12:32:10 +0530 [thread overview]
Message-ID: <20241118070211.1474372-4-tejas.upadhyay@intel.com> (raw)
In-Reply-To: <20241118070211.1474372-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.
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
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-18 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 7:02 [i-g-t V2 0/4] Add pci_membarrier test in xe_mmap Tejas Upadhyay
2024-11-18 7:02 ` [i-g-t V2 1/4] lib/i915_drm_local: Remove macros added via merged kernel Tejas Upadhyay
2024-11-18 7:02 ` [i-g-t V2 2/4] include/drm-uapi-experimental: Move i915_drm_local.h to drm-uapi-experimental Tejas Upadhyay
2024-11-18 10:42 ` Matthew Auld
2024-11-18 11:24 ` Upadhyay, Tejas
2024-11-18 7:02 ` Tejas Upadhyay [this message]
2024-11-18 7:02 ` [i-g-t V2 4/4] tests/xe/mmap: add tests for pci mem barrier Tejas Upadhyay
2024-11-18 7:05 ` ✗ CI.Patch_applied: failure for Add pci_membarrier test in xe_mmap (rev3) 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=20241118070211.1474372-4-tejas.upadhyay@intel.com \
--to=tejas.upadhyay@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.