From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: <intel-xe@lists.freedesktop.org>, <thomas.hellstrom@linux.intel.com>
Subject: [PATCH 02/16] drm/gpuvm: don't always WARN in drm_gpuvm_check_overflow()
Date: Fri, 8 Dec 2023 01:46:29 -0500 [thread overview]
Message-ID: <20231208064643.877688-3-rodrigo.vivi@intel.com> (raw)
In-Reply-To: <20231208064643.877688-1-rodrigo.vivi@intel.com>
From: Danilo Krummrich <dakr@redhat.com>
Don't always WARN in drm_gpuvm_check_overflow() and separate it into a
drm_gpuvm_check_overflow() and a dedicated
drm_gpuvm_warn_check_overflow() variant.
This avoids printing warnings due to invalid userspace requests.
(cherry picked from commit d1adea27d0c8a08031b075f1bf4c5ce6f135ad7c)
Acked-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
Signed-off-by: Danilo Krummrich <dakr@redhat.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20231108001259.15123-3-dakr@redhat.com
---
drivers/gpu/drm/drm_gpuvm.c | 20 +++++++++++++-------
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c
index b378554b81ac..1cbeb4169f9c 100644
--- a/drivers/gpu/drm/drm_gpuvm.c
+++ b/drivers/gpu/drm/drm_gpuvm.c
@@ -614,12 +614,18 @@ static int __drm_gpuva_insert(struct drm_gpuvm *gpuvm,
static void __drm_gpuva_remove(struct drm_gpuva *va);
static bool
-drm_gpuvm_check_overflow(struct drm_gpuvm *gpuvm, u64 addr, u64 range)
+drm_gpuvm_check_overflow(u64 addr, u64 range)
{
u64 end;
- return drm_WARN(gpuvm->drm, check_add_overflow(addr, range, &end),
- "GPUVA address limited to %zu bytes.\n", sizeof(end));
+ return check_add_overflow(addr, range, &end);
+}
+
+static bool
+drm_gpuvm_warn_check_overflow(struct drm_gpuvm *gpuvm, u64 addr, u64 range)
+{
+ return drm_WARN(gpuvm->drm, drm_gpuvm_check_overflow(addr, range),
+ "GPUVA address limited to %zu bytes.\n", sizeof(addr));
}
static bool
@@ -647,7 +653,7 @@ static bool
drm_gpuvm_range_valid(struct drm_gpuvm *gpuvm,
u64 addr, u64 range)
{
- return !drm_gpuvm_check_overflow(gpuvm, addr, range) &&
+ return !drm_gpuvm_check_overflow(addr, range) &&
drm_gpuvm_in_mm_range(gpuvm, addr, range) &&
!drm_gpuvm_in_kernel_node(gpuvm, addr, range);
}
@@ -682,7 +688,7 @@ drm_gpuvm_init(struct drm_gpuvm *gpuvm, const char *name,
gpuvm->ops = ops;
gpuvm->drm = drm;
- drm_gpuvm_check_overflow(gpuvm, start_offset, range);
+ drm_gpuvm_warn_check_overflow(gpuvm, start_offset, range);
gpuvm->mm_start = start_offset;
gpuvm->mm_range = range;
@@ -691,8 +697,8 @@ drm_gpuvm_init(struct drm_gpuvm *gpuvm, const char *name,
gpuvm->kernel_alloc_node.va.addr = reserve_offset;
gpuvm->kernel_alloc_node.va.range = reserve_range;
- if (likely(!drm_gpuvm_check_overflow(gpuvm, reserve_offset,
- reserve_range)))
+ if (likely(!drm_gpuvm_warn_check_overflow(gpuvm, reserve_offset,
+ reserve_range)))
__drm_gpuva_insert(gpuvm, &gpuvm->kernel_alloc_node);
}
}
--
2.43.0
next prev parent reply other threads:[~2023-12-08 6:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 6:46 [PATCH 00/16] Adjust to GPUVM / fixup version Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 01/16] drm/gpuvm: convert WARN() to drm_WARN() variants Rodrigo Vivi
2023-12-08 6:46 ` Rodrigo Vivi [this message]
2023-12-08 6:46 ` [PATCH 03/16] drm/gpuvm: export drm_gpuvm_range_valid() Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 04/16] drm/nouveau: make use of drm_gpuvm_range_valid() Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 05/16] drm/gpuvm: add common dma-resv per struct drm_gpuvm Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 06/16] drm/nouveau: make use of the GPUVM's shared dma-resv Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 07/16] drm/gpuvm: add drm_gpuvm_flags to drm_gpuvm Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 08/16] drm/nouveau: separately allocate struct nouveau_uvmm Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 09/16] drm/gpuvm: reference count drm_gpuvm structures Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 10/16] drm/gpuvm: add an abstraction for a VM / BO combination Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 11/16] drm/gpuvm: track/lock/validate external/evicted objects Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 12/16] fixup! drm/xe/vm: Simplify and document xe_vm_lock() Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 13/16] fixup! drm/xe: Convert pagefaulting code to use drm_exec Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 14/16] fixup! drm/xe: Rework xe_exec and the VM rebind worker to use the drm_exec helper Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 15/16] fixup! drm/xe: Convert remaining instances of ttm_eu_reserve_buffers to drm_exec Rodrigo Vivi
2023-12-08 6:46 ` [PATCH 16/16] fixup! drm/xe: Port Xe to GPUVA Rodrigo Vivi
2023-12-08 10:34 ` ✓ CI.Patch_applied: success for Adjust to GPUVM / fixup version Patchwork
2023-12-08 10:35 ` ✗ CI.checkpatch: warning " Patchwork
2023-12-08 10:36 ` ✓ CI.KUnit: success " Patchwork
2023-12-08 10:44 ` ✓ CI.Build: " Patchwork
2023-12-08 10:44 ` ✓ CI.Hooks: " Patchwork
2023-12-08 10:46 ` ✗ CI.checksparse: warning " Patchwork
2023-12-08 11:21 ` ✓ CI.BAT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-12-07 14:11 [PATCH 00/16] drm/xe: Adjust to DRM GPUVM changes Thomas Hellström
2023-12-07 14:11 ` [PATCH 02/16] drm/gpuvm: don't always WARN in drm_gpuvm_check_overflow() Thomas Hellström
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=20231208064643.877688-3-rodrigo.vivi@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.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