Re: [PATCH v1 4/4] mm/memory: document restore_exclusive_pte()

2025-01-31 Thread Simona Vetter
On Fri, Jan 31, 2025 at 11:14:06AM +1100, Alistair Popple wrote: > On Thu, Jan 30, 2025 at 04:29:33PM +0100, David Hildenbrand wrote: > > On 30.01.25 14:31, Simona Vetter wrote: > > > On Thu, Jan 30, 2025 at 10:37:06AM +0100, David Hildenbrand wrote: > > > > On 30.01.25 01:27, Alistair Popple wrote

Re: [PATCH v1 4/4] mm/memory: document restore_exclusive_pte()

2025-01-31 Thread David Hildenbrand
On 31.01.25 01:20, Alistair Popple wrote: On Thu, Jan 30, 2025 at 11:43:25AM +0100, Simona Vetter wrote: On Thu, Jan 30, 2025 at 11:27:37AM +1100, Alistair Popple wrote: On Wed, Jan 29, 2025 at 12:58:02PM +0100, David Hildenbrand wrote: Let's document how this function is to be used, and why t

Re: [PATCH v1 4/4] mm/memory: document restore_exclusive_pte()

2025-01-30 Thread Alistair Popple
On Thu, Jan 30, 2025 at 11:43:25AM +0100, Simona Vetter wrote: > On Thu, Jan 30, 2025 at 11:27:37AM +1100, Alistair Popple wrote: > > On Wed, Jan 29, 2025 at 12:58:02PM +0100, David Hildenbrand wrote: > > > Let's document how this function is to be used, and why the requirement > > > for the folio

Re: [PATCH v1 4/4] mm/memory: document restore_exclusive_pte()

2025-01-30 Thread Alistair Popple
On Thu, Jan 30, 2025 at 04:29:33PM +0100, David Hildenbrand wrote: > On 30.01.25 14:31, Simona Vetter wrote: > > On Thu, Jan 30, 2025 at 10:37:06AM +0100, David Hildenbrand wrote: > > > On 30.01.25 01:27, Alistair Popple wrote: > > > > On Wed, Jan 29, 2025 at 12:58:02PM +0100, David Hildenbrand wro

Re: [PATCH v1 4/4] mm/memory: document restore_exclusive_pte()

2025-01-30 Thread David Hildenbrand
On 30.01.25 14:31, Simona Vetter wrote: On Thu, Jan 30, 2025 at 10:37:06AM +0100, David Hildenbrand wrote: On 30.01.25 01:27, Alistair Popple wrote: On Wed, Jan 29, 2025 at 12:58:02PM +0100, David Hildenbrand wrote: Let's document how this function is to be used, and why the requirement for th

Re: [PATCH v1 4/4] mm/memory: document restore_exclusive_pte()

2025-01-30 Thread Simona Vetter
On Thu, Jan 30, 2025 at 10:37:06AM +0100, David Hildenbrand wrote: > On 30.01.25 01:27, Alistair Popple wrote: > > On Wed, Jan 29, 2025 at 12:58:02PM +0100, David Hildenbrand wrote: > > > Let's document how this function is to be used, and why the requirement > > > for the folio lock might maybe be

Re: [PATCH v1 4/4] mm/memory: document restore_exclusive_pte()

2025-01-30 Thread Simona Vetter
On Thu, Jan 30, 2025 at 11:27:37AM +1100, Alistair Popple wrote: > On Wed, Jan 29, 2025 at 12:58:02PM +0100, David Hildenbrand wrote: > > Let's document how this function is to be used, and why the requirement > > for the folio lock might maybe be dropped in the future. > > Sorry, only just catchi

Re: [PATCH v1 4/4] mm/memory: document restore_exclusive_pte()

2025-01-30 Thread David Hildenbrand
On 30.01.25 01:27, Alistair Popple wrote: On Wed, Jan 29, 2025 at 12:58:02PM +0100, David Hildenbrand wrote: Let's document how this function is to be used, and why the requirement for the folio lock might maybe be dropped in the future. Sorry, only just catching up on your other thread. The f

Re: [PATCH v1 4/4] mm/memory: document restore_exclusive_pte()

2025-01-29 Thread Alistair Popple
On Wed, Jan 29, 2025 at 12:58:02PM +0100, David Hildenbrand wrote: > Let's document how this function is to be used, and why the requirement > for the folio lock might maybe be dropped in the future. Sorry, only just catching up on your other thread. The folio lock was to ensure the GPU got a chan

[PATCH v1 4/4] mm/memory: document restore_exclusive_pte()

2025-01-29 Thread David Hildenbrand
Let's document how this function is to be used, and why the requirement for the folio lock might maybe be dropped in the future. Signed-off-by: David Hildenbrand --- mm/memory.c | 25 + 1 file changed, 25 insertions(+) diff --git a/mm/memory.c b/mm/memory.c index 4695699