From: Frank Binns <Frank.Binns@imgtec.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>,
Donald Robson <Donald.Robson@imgtec.com>,
Matt Coster <Matt.Coster@imgtec.com>,
"mripard@kernel.org" <mripard@kernel.org>,
"airlied@gmail.com" <airlied@gmail.com>,
"dakr@redhat.com" <dakr@redhat.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH drm-misc-next 0/5] PowerVR VM fixes
Date: Mon, 27 Nov 2023 10:53:54 +0000 [thread overview]
Message-ID: <d8c45d6c1b4ecbb182c4a16cb06def520450efa4.camel@imgtec.com> (raw)
In-Reply-To: <20231124233650.152653-1-dakr@redhat.com>
Hi,
Thank you for the patches.
On Sat, 2023-11-25 at 00:36 +0100, Danilo Krummrich wrote:
> 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
>
>
> Danilo Krummrich (5):
> drm/imagination: vm: prevent duplicate drm_gpuvm_bo instances
> drm/imagination: vm: check for drm_gpuvm_range_valid()
> drm/imagination: vm: fix drm_gpuvm reference count
> 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 | 36 ++++++++++++++++++++--
> drivers/gpu/drm/imagination/pvr_vm.c | 46 +++++++++++++++-------------
> drivers/gpu/drm/imagination/pvr_vm.h | 3 +-
> include/drm/drm_gpuvm.h | 23 ++------------
> 4 files changed, 63 insertions(+), 45 deletions(-)
>
>
> base-commit: 46990918f35c1bf6e367cf8e0423e7344fec9fcb
For the series:
Tested-by: Frank Binns <frank.binns@imgtec.com>
I'll leave it to Donald to do the review.
Thanks
Frank
prev parent reply other threads:[~2023-11-27 11:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 23:36 Danilo Krummrich
2023-11-24 23:36 ` [PATCH drm-misc-next 1/5] drm/imagination: vm: prevent duplicate drm_gpuvm_bo instances Danilo Krummrich
2023-11-28 10:34 ` [EXTERNAL] " Donald Robson
2023-11-28 13:00 ` (subset) " Maxime Ripard
2023-11-24 23:36 ` [PATCH drm-misc-next 2/5] drm/imagination: vm: check for drm_gpuvm_range_valid() Danilo Krummrich
2023-11-28 10:34 ` [EXTERNAL] " Donald Robson
2023-11-28 13:00 ` (subset) " Maxime Ripard
2023-11-24 23:36 ` [PATCH drm-misc-next 3/5] drm/imagination: vm: fix drm_gpuvm reference count Danilo Krummrich
2023-11-28 10:36 ` Donald Robson
2023-11-28 13:01 ` (subset) " Maxime Ripard
2023-11-24 23:36 ` [PATCH drm-misc-next 4/5] drm/gpuvm: fall back to drm_exec_lock_obj() Danilo Krummrich
2023-11-24 23:40 ` Danilo Krummrich
2023-11-27 13:52 ` Christian König
2023-11-27 17:50 ` Danilo Krummrich
2023-11-24 23:36 ` [PATCH drm-misc-next 5/5] drm/imagination: vm: make use of GPUVM's drm_exec helper Danilo Krummrich
2023-11-28 10:47 ` [EXTERNAL] " Donald Robson
2023-11-28 19:02 ` Danilo Krummrich
2023-11-27 10:53 ` Frank Binns [this message]
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=d8c45d6c1b4ecbb182c4a16cb06def520450efa4.camel@imgtec.com \
--to=frank.binns@imgtec.com \
--cc=Donald.Robson@imgtec.com \
--cc=Matt.Coster@imgtec.com \
--cc=airlied@gmail.com \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.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
all inboxes | Powered by JetHome®