From: Boris Brezillon <boris.brezillon@collabora.com>
To: Danilo Krummrich <dakr@redhat.com>
Cc: airlied@gmail.com, daniel@ffwll.ch, matthew.brost@intel.com,
thomas.hellstrom@linux.intel.com, sarah.walker@imgtec.com,
donald.robson@imgtec.com, christian.koenig@amd.com,
faith@gfxstrand.net, dri-devel@lists.freedesktop.org,
nouveau@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH drm-misc-next v9 03/12] drm/gpuvm: export drm_gpuvm_range_valid()
Date: Fri, 10 Nov 2023 12:20:15 +0100 [thread overview]
Message-ID: <20231110122015.69636459@collabora.com> (raw)
In-Reply-To: <20231108001259.15123-4-dakr@redhat.com>
On Wed, 8 Nov 2023 01:12:33 +0100
Danilo Krummrich <dakr@redhat.com> wrote:
> Drivers may use this function to validate userspace requests in advance,
> hence export it.
>
> Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Signed-off-by: Danilo Krummrich <dakr@redhat.com>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
> ---
> drivers/gpu/drm/drm_gpuvm.c | 14 +++++++++++++-
> include/drm/drm_gpuvm.h | 1 +
> 2 files changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c
> index 445767f8fbc4..2669f9bbc377 100644
> --- a/drivers/gpu/drm/drm_gpuvm.c
> +++ b/drivers/gpu/drm/drm_gpuvm.c
> @@ -649,7 +649,18 @@ drm_gpuvm_in_kernel_node(struct drm_gpuvm *gpuvm, u64 addr, u64 range)
> return krange && addr < kend && kstart < end;
> }
>
> -static bool
> +/**
> + * drm_gpuvm_range_valid() - checks whether the given range is valid for the
> + * given &drm_gpuvm
> + * @gpuvm: the GPUVM to check the range for
> + * @addr: the base address
> + * @range: the range starting from the base address
> + *
> + * Checks whether the range is within the GPUVM's managed boundaries.
> + *
> + * Returns: true for a valid range, false otherwise
> + */
> +bool
> drm_gpuvm_range_valid(struct drm_gpuvm *gpuvm,
> u64 addr, u64 range)
> {
> @@ -657,6 +668,7 @@ drm_gpuvm_range_valid(struct drm_gpuvm *gpuvm,
> drm_gpuvm_in_mm_range(gpuvm, addr, range) &&
> !drm_gpuvm_in_kernel_node(gpuvm, addr, range);
> }
> +EXPORT_SYMBOL_GPL(drm_gpuvm_range_valid);
>
> /**
> * drm_gpuvm_init() - initialize a &drm_gpuvm
> diff --git a/include/drm/drm_gpuvm.h b/include/drm/drm_gpuvm.h
> index 687fd5893624..13eac6f70061 100644
> --- a/include/drm/drm_gpuvm.h
> +++ b/include/drm/drm_gpuvm.h
> @@ -253,6 +253,7 @@ void drm_gpuvm_init(struct drm_gpuvm *gpuvm, const char *name,
> const struct drm_gpuvm_ops *ops);
> void drm_gpuvm_destroy(struct drm_gpuvm *gpuvm);
>
> +bool drm_gpuvm_range_valid(struct drm_gpuvm *gpuvm, u64 addr, u64 range);
> bool drm_gpuvm_interval_empty(struct drm_gpuvm *gpuvm, u64 addr, u64 range);
>
> static inline struct drm_gpuva *
next prev parent reply other threads:[~2023-11-10 18:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 0:12 [PATCH drm-misc-next v9 00/12] [RFC] DRM GPUVM features Danilo Krummrich
2023-11-08 0:12 ` [PATCH drm-misc-next v9 01/12] drm/gpuvm: convert WARN() to drm_WARN() variants Danilo Krummrich
2023-11-08 0:12 ` [PATCH drm-misc-next v9 02/12] drm/gpuvm: don't always WARN in drm_gpuvm_check_overflow() Danilo Krummrich
2023-11-10 11:19 ` Boris Brezillon
2023-11-08 0:12 ` [PATCH drm-misc-next v9 03/12] drm/gpuvm: export drm_gpuvm_range_valid() Danilo Krummrich
2023-11-10 11:20 ` Boris Brezillon [this message]
2023-11-08 0:12 ` [PATCH drm-misc-next v9 04/12] drm/nouveau: make use of drm_gpuvm_range_valid() Danilo Krummrich
2023-11-08 0:12 ` [PATCH drm-misc-next v9 05/12] drm/gpuvm: add common dma-resv per struct drm_gpuvm Danilo Krummrich
2023-11-08 0:12 ` [PATCH drm-misc-next v9 06/12] drm/nouveau: make use of the GPUVM's shared dma-resv Danilo Krummrich
2023-11-08 0:12 ` [PATCH drm-misc-next v9 07/12] drm/gpuvm: add drm_gpuvm_flags to drm_gpuvm Danilo Krummrich
2023-11-08 0:12 ` [PATCH drm-misc-next v9 08/12] drm/nouveau: separately allocate struct nouveau_uvmm Danilo Krummrich
2023-11-08 0:12 ` [PATCH drm-misc-next v9 09/12] drm/gpuvm: reference count drm_gpuvm structures Danilo Krummrich
2023-11-10 10:39 ` Thomas Hellström
2023-11-10 11:21 ` Boris Brezillon
2023-11-08 0:12 ` [PATCH drm-misc-next v9 10/12] drm/gpuvm: add an abstraction for a VM / BO combination Danilo Krummrich
2023-11-08 0:12 ` [PATCH drm-misc-next v9 11/12] drm/gpuvm: track/lock/validate external/evicted objects Danilo Krummrich
2023-11-08 0:12 ` [PATCH drm-misc-next v9 12/12] drm/nouveau: use GPUVM common infrastructure Danilo Krummrich
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=20231110122015.69636459@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=donald.robson@imgtec.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=faith@gfxstrand.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=nouveau@lists.freedesktop.org \
--cc=sarah.walker@imgtec.com \
--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