[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250124181524.3584236-1-david@redhat.com>
Date: Fri, 24 Jan 2025 19:15:22 +0100
From: David Hildenbrand <david@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: dri-devel@...ts.freedesktop.org,
nouveau@...ts.freedesktop.org,
David Hildenbrand <david@...hat.com>,
Karol Herbst <kherbst@...hat.com>,
Lyude Paul <lyude@...hat.com>,
Danilo Krummrich <dakr@...nel.org>,
David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>,
Alistair Popple <apopple@...dia.com>
Subject: [PATCH v1 0/2] nouveau/svm: fix + cleanup for nouveau_atomic_range_fault()
One fix and a minor cleanup.
Only compile-tested due to lack of HW, so I'd be happy if someone with
access to HW could test. But not sure how easy this is to trigger. Likely
some concurrent MADV_DONTNEED on the PTE we just converted might be able
to trigger it.
Cc: Karol Herbst <kherbst@...hat.com>
Cc: Lyude Paul <lyude@...hat.com>
Cc: Danilo Krummrich <dakr@...nel.org>
Cc: David Airlie <airlied@...il.com>
Cc: Simona Vetter <simona@...ll.ch>
Cc: Alistair Popple <apopple@...dia.com>
David Hildenbrand (2):
nouveau/svm: fix missing folio unlock + put after
make_device_exclusive_range()
nouveau/svm: don't initialize ret in nouveau_atomic_range_fault()
drivers/gpu/drm/nouveau/nouveau_svm.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
--
2.47.1
Powered by blists - more mailing lists