Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH 0/3] Test GPUVA and NULL VM binds
Date: Wed, 15 Mar 2023 13:59:38 -0700	[thread overview]
Message-ID: <20230315205941.4038718-1-matthew.brost@intel.com> (raw)

Tests: https://patchwork.freedesktop.org/series/115217/

Signed-off-by: Matthew Brost <matthew.brost@intel.com>

Matthew Brost (3):
  xe: Update to latest uAPI
  xe_exec_basic: Add NULL VM bind section
  xe_vm: MMAP style VM binds section

 include/drm-uapi/xe_drm.h |   8 +
 tests/xe/xe_exec_basic.c  |  29 +++-
 tests/xe/xe_vm.c          | 326 +++++++++++++++++++++++++++++++++-----
 3 files changed, 322 insertions(+), 41 deletions(-)

-- 
2.34.1

             reply	other threads:[~2023-03-15 20:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 20:59 Matthew Brost [this message]
2023-03-15 20:59 ` [igt-dev] [PATCH 1/3] xe: Update to latest uAPI Matthew Brost
2023-03-15 20:59 ` [igt-dev] [PATCH 2/3] xe_exec_basic: Add NULL VM bind section Matthew Brost
2023-03-15 20:59 ` [igt-dev] [PATCH 3/3] xe_vm: MMAP style VM binds section Matthew Brost
2023-03-15 21:33 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Test GPUVA and NULL VM binds 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=20230315205941.4038718-1-matthew.brost@intel.com \
    --to=matthew.brost@intel.com \
    --cc=igt-dev@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