From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DD2DB38422D for ; Thu, 25 Jun 2026 11:54:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782388471; cv=none; b=MhjcYKyT3jMVVuxHuRfXfbL8aJNqnu3AJ8zM0Nj0e2C9XDxMUSpyDqZSehy4AgP27UFq+MMRoe74M0+X3Mj8J135IEs84oapegBXtl1qnTRfItqcAYk2CXpXm+SMtG5qnaAkZLK4ZPQldEIyib0zVYI3Z3pWyR6Db0Hs7SmR4+Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782388471; c=relaxed/simple; bh=/GXFi/MVRAwUZHw1Zk5DPCqLioIWwoiNAiqmK1nO1Ew=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=BGoUsTEutg08Y0NUdYKkyKKtDW5J82B7os7DO5BfsEwzDHbxiJb/yqPGRwkNq8ZeKKgGJFWPSA2HTrIVAWNtxrpJXQxRLu98xrp3U725xIWl3yVXjNYSrjaflpW/l0/n2DiFo1ovASh6qz2oBc7stTn3HoDIQd7JRgdv69nqd60= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=beu4O6BZ; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="beu4O6BZ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 264EE1F000E9; Thu, 25 Jun 2026 11:54:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1782388470; bh=/GXFi/MVRAwUZHw1Zk5DPCqLioIWwoiNAiqmK1nO1Ew=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=beu4O6BZP1eXIi45Dd5+lSUZZefTpFb3TjvzlFxLH0t/BOcXi8L6Dale141fqCl6Z /Xte0MUmMr3yT9Pcbt1Lg8nplPdvKdmOnIVohDbRXzgub0s/+nTkR/vXxf57AZz0CF SBFlmlwifSmHo/3s7jGSTq143SfCAFMwOl8TxWJ61LJRBo6NS6O+GjGXDZFEdykJda ZAhI6fYFT/UqiaP96opC92vgpKZ/jIEtfoHBzsGwNgcrPxbp9F0u58F4tUoecbcYza skRccOgyZHJp/MMsUbljWviO84DFhaq696UGJc6N0ZebJUxf28JNGPE6nucgOmoHxO kXQfySON4fttw== Date: Thu, 25 Jun 2026 12:54:20 +0100 From: Lorenzo Stoakes To: "David Hildenbrand (Arm)" Cc: Yitao Jiang , Alex Deucher , Christian =?utf-8?B?S8O2bmln?= , David Airlie , Simona Vetter , Felix Kuehling , Andrew Morton , Zi Yan , Baolin Wang , "Liam R . Howlett" , Nico Pache , Ryan Roberts , Dev Jain , Barry Song , Lance Yang , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , Jann Horn , amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 0/3] mm/mmu_notifier, drm/amdgpu: block THP for GPU user mappings Message-ID: References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: NAK to this or any version of this. This series is insane and the idea is insane. On Thu, Jun 25, 2026 at 01:47:25PM +0200, David Hildenbrand (Arm) wrote: > On 6/25/26 12:59, Yitao Jiang wrote: > > Hi, > > > > This series fixes a THP policy problem I found while debugging > > frequent ROCm GPU failures on an AMD Radeon 780M system during ML > > training. > > > > Some AMDGPU/KFD user mappings are registered through interval > > notifiers and cannot safely tolerate the backing VMA changing from base > > pages to a transparent huge page after registration. Userspace can > > still apply MADV_HUGEPAGE or MADV_COLLAPSE, and khugepaged can also > > collapse the range, after the GPU mapping has been registered. > > Huh, why? As a memory notifier user, you must be prepared from memory to get > unmapped+remapped at random points in time. > > What is the precise problem here? How are you handling THPs at registration time? > > Letting arbitrary drivers make THP policies sounds like the very wrong approach. We absolutely will not _ever_ allow drivers to do this while I still breath :) > > -- > Cheers, > > David Thanks, Lorenzo