Re: [PATCH 1/7] drm/gpusvm: fix hmm_pfn_to_map_order() usage

2025-03-21 Thread Matthew Auld
On 20/03/2025 20:40, Matthew Brost wrote: On Thu, Mar 20, 2025 at 05:29:58PM +, Matthew Auld wrote: Handle the case where the hmm range partially covers a huge page (like 2M), otherwise we can potentially end up doing something nasty like mapping memory which potentially is outside the range

Re: [PATCH 1/7] drm/gpusvm: fix hmm_pfn_to_map_order() usage

2025-03-20 Thread Matthew Brost
On Thu, Mar 20, 2025 at 05:29:58PM +, Matthew Auld wrote: > Handle the case where the hmm range partially covers a huge page (like > 2M), otherwise we can potentially end up doing something nasty like > mapping memory which potentially is outside the range, and maybe not > even mapped by the mm

Re: [PATCH 1/7] drm/gpusvm: fix hmm_pfn_to_map_order() usage

2025-03-20 Thread Thomas Hellström
On Thu, 2025-03-20 at 17:29 +, Matthew Auld wrote: > Handle the case where the hmm range partially covers a huge page > (like > 2M), otherwise we can potentially end up doing something nasty like > mapping memory which potentially is outside the range, and maybe not > even mapped by the mm. Fix