From: Tejas Upadhyay <tejas.upadhyay@intel.com>
To: igt-dev@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Auld@freedesktop.org, Matthew <matthew.auld@intel.com>,
Tejas Upadhyay <tejas.upadhyay@intel.com>
Subject: [PATCH V7 0/4] Add pci_membarrier test in xe_mmap
Date: Mon, 6 Jan 2025 20:44:37 +0530 [thread overview]
Message-ID: <20250106151441.2598949-1-tejas.upadhyay@intel.com> (raw)
Series adds,
1. Remove all local defines which are landed from upstream kernel
include. Keeping include in igt_gt.h as its common header for all
such defines.
2. New flag in mmap_offset ioctl to provide query
support for special offset.
3. Adds pci_membarrier subtests xe_mmap test
Note: Similar drm-uapi change made here is under review
in KMD as well
V7:
- Modify parallel test to update random number every test
- Update cross client value check
V6:
- Modify parallel test to check only diff cross client value
V5:
- Add pci-membarrier-parallel subtest
V4:
- Check if pci memory barrier is supported
Tejas Upadhyay (4):
lib/i915_drm_local: Remove macros added via merged kernel
include/drm-uapi-experimental: Move i915_drm_local.h to
drm-uapi-experimental
include/intel_drm_local.h: Add DRM_XE_MMAP_OFFSET_FLAG_PCI_BARRIER
tests/xe/mmap: add tests for pci mem barrier
.../drm-uapi-experimental/intel_drm_local.h | 29 +++
lib/i915/gem_scheduler.c | 1 -
lib/i915/i915_drm_local.h | 6 -
lib/i915/intel_memory_region.h | 1 -
lib/igt_gt.h | 2 +-
tests/intel/xe_mmap.c | 171 ++++++++++++++++++
tools/i915-perf/i915_perf_recorder.c | 2 -
7 files changed, 201 insertions(+), 11 deletions(-)
create mode 100644 include/drm-uapi-experimental/intel_drm_local.h
--
2.34.1
next reply other threads:[~2025-01-06 15:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 15:14 Tejas Upadhyay [this message]
2025-01-06 15:14 ` [PATCH V7 1/4] lib/i915_drm_local: Remove macros added via merged kernel Tejas Upadhyay
2025-01-06 15:14 ` [PATCH V7 2/4] include/drm-uapi-experimental: Move i915_drm_local.h to drm-uapi-experimental Tejas Upadhyay
2025-01-06 15:14 ` [PATCH V7 3/4] include/intel_drm_local.h: Add DRM_XE_MMAP_OFFSET_FLAG_PCI_BARRIER Tejas Upadhyay
2025-01-06 15:14 ` [PATCH V7 4/4] tests/xe/mmap: add tests for pci mem barrier Tejas Upadhyay
2025-01-07 13:35 ` Matthew Auld
2025-01-07 13:40 ` Upadhyay, Tejas
2025-01-06 15:48 ` ✗ GitLab.Pipeline: warning for Add pci_membarrier test in xe_mmap (rev8) Patchwork
2025-01-06 16:16 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-06 16:23 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-06 17:21 ` ✓ i915.CI.Full: " Patchwork
2025-01-07 7:57 ` ✗ Xe.CI.Full: failure " 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=20250106151441.2598949-1-tejas.upadhyay@intel.com \
--to=tejas.upadhyay@intel.com \
--cc=Auld@freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox