From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org
Cc: thomas.hellstrom@linux.intel.com, sumit.semwal@linaro.org,
christian.koenig@amd.com, daniel@ffwll.ch
Subject: [PATCH v3 0/2] Replace dma-fence chain with dma-fence array for media GT TLB invalidation
Date: Thu, 22 Aug 2024 21:54:41 -0700 [thread overview]
Message-ID: <20240823045443.2132118-1-matthew.brost@intel.com> (raw)
Third try, requires spliting out dma fence array alloc and arm into new
functions to avoid memory allocations under notifier lock.
Matt
Matthew Brost (2):
dma-buf: Split out dma fence array create into alloc and arm functions
drm/xe: Use dma-fence array for media GT TLB invalidations in PT code
drivers/dma-buf/dma-fence-array.c | 81 ++++++++++++++++++++++---------
drivers/gpu/drm/xe/xe_pt.c | 34 +++++++++----
include/linux/dma-fence-array.h | 7 +++
3 files changed, 90 insertions(+), 32 deletions(-)
--
2.34.1
next reply other threads:[~2024-08-23 4:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 4:54 Matthew Brost [this message]
2024-08-23 4:54 ` [PATCH v3 1/2] dma-buf: Split out dma fence array create into alloc and arm functions Matthew Brost
2024-08-23 6:37 ` Christian König
2024-08-23 15:46 ` Matthew Brost
2024-08-27 17:15 ` Daniel Vetter
2024-08-23 4:54 ` [PATCH v3 2/2] drm/xe: Use dma-fence array for media GT TLB invalidations in PT code Matthew Brost
2024-08-23 6:40 ` Christian König
2024-08-23 15:38 ` Matthew Brost
2024-08-26 7:43 ` Christian König
2024-08-26 8:45 ` Matthew Brost
2024-08-23 5:04 ` ✓ CI.Patch_applied: success for Replace dma-fence chain with dma-fence array for media GT TLB invalidation Patchwork
2024-08-23 5:04 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-23 5:05 ` ✓ CI.KUnit: success " Patchwork
2024-08-23 5:17 ` ✓ CI.Build: " Patchwork
2024-08-23 5:19 ` ✓ CI.Hooks: " Patchwork
2024-08-23 5:21 ` ✗ CI.checksparse: warning " Patchwork
2024-08-23 5:45 ` ✓ CI.BAT: success " Patchwork
2024-08-23 13:32 ` ✗ 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=20240823045443.2132118-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=thomas.hellstrom@linux.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