From: Danilo Krummrich <dakr@redhat.com>
To: mripard@kernel.org, airlied@gmail.com, daniel@ffwll.ch,
frank.binns@imgtec.com, donald.robson@imgtec.com,
matt.coster@imgtec.com, sarah.walker@imgtec.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Danilo Krummrich <dakr@redhat.com>
Subject: [PATCH drm-misc-next v2 0/2] PowerVR VM fixes
Date: Wed, 29 Nov 2023 23:07:59 +0100 [thread overview]
Message-ID: <20231129220835.297885-1-dakr@redhat.com> (raw)
Hi,
Some major GPUVM changes landed just before v8 of the PowerVR series. Since v8
went in rather quickly (review process was finished otherwise) I haven't had the
chance to review the subsequent code changes.
Hence, this series with a few fixes in this context. Plus a minor GPUVM patch to
make the drm_gpuvm_prepare_* helpers useful for PowerVR.
- Danilo
Changes in V2
=============
- GPUVM: update function DOC comment to indicate the passing zero fences to
drm_gpuvm_prepare_* functions results into drm_exec_lock_obj() calls rather
than drm_exec_prepare_obj() calls.
- pvr/vm: use drm_gpuvm_exec wrappers
- drop 3 patches which were applied already
Danilo Krummrich (2):
drm/gpuvm: fall back to drm_exec_lock_obj()
drm/imagination: vm: make use of GPUVM's drm_exec helper
drivers/gpu/drm/drm_gpuvm.c | 43 +++++++++++--
drivers/gpu/drm/imagination/pvr_vm.c | 91 +++++++++++-----------------
include/drm/drm_gpuvm.h | 23 +------
3 files changed, 77 insertions(+), 80 deletions(-)
base-commit: 83dc1029dcf50b5b849b26679a1b3f860b85d79c
--
2.43.0
next reply other threads:[~2023-11-29 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 22:07 Danilo Krummrich [this message]
2023-11-29 22:08 ` [PATCH drm-misc-next v2 1/2] drm/gpuvm: fall back to drm_exec_lock_obj() Danilo Krummrich
2023-11-29 22:08 ` [PATCH drm-misc-next v2 2/2] drm/imagination: vm: make use of GPUVM's drm_exec helper Danilo Krummrich
2023-12-05 14:54 ` [EXTERNAL] [PATCH drm-misc-next v2 0/2] PowerVR VM fixes Donald Robson
2023-12-05 15:35 ` Maxime Ripard
2023-12-05 15:40 ` Danilo Krummrich
2023-12-06 8:28 ` Maxime Ripard
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=20231129220835.297885-1-dakr@redhat.com \
--to=dakr@redhat.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=donald.robson@imgtec.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank.binns@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.coster@imgtec.com \
--cc=mripard@kernel.org \
--cc=sarah.walker@imgtec.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
all inboxes | Powered by JetHome®