Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 i-g-t V2 0/2] Add xe_pci_membarrier test
Date: Wed, 23 Oct 2024 15:13:25 +0530	[thread overview]
Message-ID: <20241023094327.965050-1-tejas.upadhyay@intel.com> (raw)

Series adds,
1. New flag in mmap_offset ioctl to provide query 
support for special offset.
2. Adds xe_pci_membarrier test

Note: Similar drm-uapi change made here is under review 
in KMD as well

Tejas Upadhyay (2):
  drm-uapi/xe: Add new flag in mmap offset ioctl
  tests/intel: Add xe_pci_membarrier test

 include/drm-uapi/xe_drm.h       | 13 +++++-
 tests/intel/xe_pci_membarrier.c | 80 +++++++++++++++++++++++++++++++++
 tests/meson.build               |  1 +
 3 files changed, 93 insertions(+), 1 deletion(-)
 create mode 100644 tests/intel/xe_pci_membarrier.c

-- 
2.34.1


             reply	other threads:[~2024-10-23  9:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23  9:43 Tejas Upadhyay [this message]
2024-10-23  9:43 ` [PATCH i-g-t V2 1/2] drm-uapi/xe: Add new flag in mmap offset ioctl Tejas Upadhyay
2024-11-06 17:35   ` Matt Roper
2024-10-23  9:43 ` [PATCH i-g-t V2 2/2] tests/intel: Add xe_pci_membarrier test Tejas Upadhyay
2024-11-01 13:55   ` Matthew Auld
2024-11-06 12:00     ` Upadhyay, Tejas
2024-11-06 13:12       ` Upadhyay, Tejas
2024-11-11 11:48         ` Matthew Auld
2024-10-23 10:42 ` ✗ GitLab.Pipeline: warning for " Patchwork
2024-10-23 11:00 ` ✓ Fi.CI.BAT: success " Patchwork
2024-10-23 11:09 ` ✓ CI.xeBAT: " Patchwork
2024-10-23 12:58 ` ✗ CI.xeFULL: failure " Patchwork
2024-10-23 15:56 ` ✗ Fi.CI.IGT: " Patchwork
2024-11-06 13:17 ` ✗ Fi.CI.BUILD: failure for Add xe_pci_membarrier test (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=20241023094327.965050-1-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