From: Matthew Auld <matthew.auld@intel.com>
To: Tejas Upadhyay <tejas.upadhyay@intel.com>,
igt-dev@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [i-g-t 3/4] include/intel_drm_local.h: Add DRM_XE_MMAP_OFFSET_FLAG_PCI_BARRIER
Date: Fri, 15 Nov 2024 10:27:04 +0000 [thread overview]
Message-ID: <59554420-7a6e-4475-b72e-9c41088a322a@intel.com> (raw)
In-Reply-To: <20241114050129.1381711-4-tejas.upadhyay@intel.com>
On 14/11/2024 05:01, Tejas Upadhyay wrote:
> 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>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Although not sure if we should still have separate i915 and xe headers,
just how it is in the official kernel headers. Maybe that is a bikeshed
though.
> ---
> 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
next prev parent reply other threads:[~2024-11-15 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 5:01 [i-g-t 0/4] Add pci_membarrier test in xe_mmap Tejas Upadhyay
2024-11-14 5:01 ` [i-g-t 1/4] lib/i915_drm_local: Remove macros added via merged kernel Tejas Upadhyay
2024-11-15 10:14 ` Matthew Auld
2024-11-14 5:01 ` [i-g-t 2/4] include/drm-uapi-experimental: Move i915_drm_local.h to drm-uapi-experimental Tejas Upadhyay
2024-11-15 10:22 ` Matthew Auld
2024-11-14 5:01 ` [i-g-t 3/4] include/intel_drm_local.h: Add DRM_XE_MMAP_OFFSET_FLAG_PCI_BARRIER Tejas Upadhyay
2024-11-15 10:27 ` Matthew Auld [this message]
2024-11-14 5:01 ` [i-g-t 4/4] tests/xe/mmap: add tests for pci mem barrier Tejas Upadhyay
2024-11-15 10:50 ` Matthew Auld
2024-11-14 5:24 ` ✗ CI.Patch_applied: failure for Add pci_membarrier test in xe_mmap (rev2) 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=59554420-7a6e-4475-b72e-9c41088a322a@intel.com \
--to=matthew.auld@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=tejas.upadhyay@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox