From: Jason Gunthorpe <jgg@nvidia.com>
To: David Hildenbrand <david@redhat.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
John Hubbard <jhubbard@nvidia.com>,
nouveau@lists.freedesktop.org,
Alistair Popple <apopple@nvidia.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Karol Herbst <kherbst@redhat.com>, Lyude Paul <lyude@redhat.com>,
Danilo Krummrich <dakr@kernel.org>
Subject: Re: [Question] Are "device exclusive non-swap entries" / "SVM atomics in Nouveau" still getting used in practice?
Date: Fri, 24 Jan 2025 10:11:21 -0400 [thread overview]
Message-ID: <20250124141121.GY5556@nvidia.com> (raw)
In-Reply-To: <8c6f3838-f194-4a42-845d-10011192a234@redhat.com>
On Fri, Jan 24, 2025 at 11:44:28AM +0100, David Hildenbrand wrote:
> There are other concerns I have (what if the page is pinned and access
> outside of the user space page tables?). Maybe there was not need to handle
> these cases so far.
I think alot of this depends on userspace following some restrictions
so that the pages are always convertible. Presumably if the userspace
breaks things then their atomic using GPU kernels will fault.
So, from a kernel perspective, I'd suggest that creating a reasonable
set of conditions that userspace can follow to have it work reliably
is a reasonable goal.
Jason
next prev parent reply other threads:[~2025-01-24 14:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 10:20 [Question] Are "device exclusive non-swap entries" / "SVM atomics in Nouveau" still getting used in practice? David Hildenbrand
2025-01-23 15:08 ` Simona Vetter
2025-01-24 10:44 ` David Hildenbrand
2025-01-24 14:11 ` Jason Gunthorpe [this message]
2025-01-24 14:39 ` David Hildenbrand
2025-01-24 15:28 ` Simona Vetter
2025-01-24 17:54 ` David Hildenbrand
2025-01-28 0:09 ` Alistair Popple
2025-01-28 20:14 ` Simona Vetter
2025-01-28 20:24 ` David Hildenbrand
2025-01-29 10:48 ` Simona Vetter
2025-01-29 11:28 ` Simona Vetter
2025-01-29 11:31 ` David Hildenbrand
2025-01-29 14:05 ` Simona Vetter
2025-01-29 16:13 ` David Hildenbrand
2025-01-30 8:55 ` Simona Vetter
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=20250124141121.GY5556@nvidia.com \
--to=jgg@nvidia.com \
--cc=apopple@nvidia.com \
--cc=dakr@kernel.org \
--cc=david@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jhubbard@nvidia.com \
--cc=kherbst@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.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