From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta1.migadu.com (out-183.mta1.migadu.com [95.215.58.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A165C3F9284 for ; Mon, 17 Aug 2026 12:22:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.183 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786969326; cv=none; b=N6a5saxaOjP+MVbTpgR2CjKRb43zLpElPjjrBNB1LCrnZOa7SXoqLAUEceo3C9LHMW3Gc6VrY6mtXCWsplSFlyE2KQvVIcAXKiH0OmbG0+fD5m8jOms/qILvQH51vdQGLL6zxkXRVu5HbySsoOZNsXgNAHeXQGth+iY62HBgwr4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786969326; c=relaxed/simple; bh=XUz20HjX88HKc3zhTmA9XIj0WBNTBdnuMyd7s0rygf4=; h=Mime-Version:Content-Type:Date:Message-Id:Cc:Subject:From:To: References:In-Reply-To; b=hq1SpX58kp/i/tls7FLL31Q+JQbGaeAzJhyo7/P/DGaNa1lIcD/KNox709l1SHhM1LV1bD+3hYZBtAfzvl4JKZZLVXWNGLwWBLrKBoJha7+mc6BVPuEahjRj/bElShc5/sQY5PRRKgrYH9H2IjT3nJWB2lzSZePRKnWqOr/QK2c= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=XkldS3CH; arc=none smtp.client-ip=95.215.58.183 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="XkldS3CH" X-Envelope-To: linux-kernel@vger.kernel.org DKIM-Signature: a=rsa-sha256; bh=XUz20HjX88HKc3zhTmA9XIj0WBNTBdnuMyd7s0rygf4=; c=simple/simple; d=linux.dev; h=from:to:subject:date:message-id:mime-version:content-type; s=key1; t=1786969322; v=1; x=1787574122; b=XkldS3CHg9hCBivEOhkQQzkmUhdPITkRmMuNYQi3cCkftCjtJWWLDRiDP/+pw18b1esq4lNP slbcZxty0whFStgDGAoQnHGUK2wfA2IpllM//lyHcu35MfQ6dkOPY6w42V/iiNp8rSh+jXtT66Q Gkbjx9DvRnQfiagSi2bv5dsQ= X-Envelope-To: linux-kernel@vger.kernel.org Received: from localhost (185.201.63.253) by smtp.migadu.com with ESMTPS id ac101bf52cfc1249; Mon, 17 Aug 2026 12:22:02 +0000 X-Migadu-Flow: FLOW_OUT Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 17 Aug 2026 14:21:41 +0200 Message-Id: Cc: =?utf-8?q?Adrian_Barna=C5=9B?= , "Albert Ou" , "Alexander Gordeev" , "Alexandre Ghiti" , "Andy Lutomirski" , "Borislav Petkov" , "Brendan Jackman" , "Catalin Marinas" , "Christian Borntraeger" , "Dave Hansen" , "David Hildenbrand" , "Gerald Schaefer" , "Heiko Carstens" , "Huacai Chen" , "Ingo Molnar" , "Len Brown" , "Palmer Dabbelt" , "Paul Walmsley" , "Pavel Machek" , "Peter Zijlstra" , "H. Peter Anvin" , "Rafael J. Wysocki" , "Ryan Roberts" , "Sven Schnelle" , "Thomas Gleixner" , "Uladzislau Rezki" , "Vasily Gorbik" , "WANG Xuerui" , "Will Deacon" , , , , , , , , Subject: Re: [PATCH 4/6] mm/vmalloc: make set_area_direct_map HUGE_VMAP friendly From: "Brendan Jackman" To: "Mike Rapoport (Microsoft)" , "Andrew Morton" X-Mailer: aerc 0.21.0 References: <20260816-execmem-set-vm-perms-v0-2-v1-0-90944a3ad43f@kernel.org> <20260816-execmem-set-vm-perms-v0-2-v1-4-90944a3ad43f@kernel.org> In-Reply-To: <20260816-execmem-set-vm-perms-v0-2-v1-4-90944a3ad43f@kernel.org> On Sun Aug 16, 2026 at 12:59 PM CEST, Mike Rapoport (Microsoft) wrote: > set_area_direct_map() always updates direct map alias permissions in > single page increments. > > For HUGE_VMAP areas it's suboptimal. Not only the loop in > set_area_direct_map() needlessly has more iterations (e.g times 512 on > x86), but it also causes fragmentation of the direct map that could be > avoided for the HUGE_VMAP areas populated with large pages. > > All pages in an area are always of the same order: either same-order > large pages when VM_ALLOW_HUGE_VMAP is set and all huge pages were > successfully allocated, or order-0 page when VM_ALLOW_HUGE_VMAP is > cleared or when huge pages allocation fails and fallback path is taken. > > Instead of updating the direct map permissions for every order-0 page in > an area, use the area's page_order as the loop increment and update the > large pages in one call to set_direct_map_{invalid,default}_noflush(). > > Signed-off-by: Mike Rapoport (Microsoft) > --- > mm/vmalloc.c | 13 ++++++++----- > 1 file changed, 8 insertions(+), 5 deletions(-) > > diff --git a/mm/vmalloc.c b/mm/vmalloc.c > index fc7993db4152..11170d1ee5be 100644 > --- a/mm/vmalloc.c > +++ b/mm/vmalloc.c > @@ -3361,12 +3361,15 @@ static inline void set_area_direct_map(const stru= ct vm_struct *area, > int (*set_direct_map)(struct page *page, > unsigned int nr)) > { > - unsigned long i; > + unsigned int nr =3D (1U << vm_area_page_order(area)); > + > + for (unsigned long i =3D 0; i < area->nr_pages; i +=3D nr) { > + if (page_address(area->pages[i])) { > + int err =3D set_direct_map(area->pages[i], nr); > =20 > - /* HUGE_VMALLOC passes small pages to set_direct_map */ > - for (i =3D 0; i < area->nr_pages; i++) > - if (page_address(area->pages[i])) > - set_direct_map(area->pages[i], 1); > + WARN_ON_ONCE(err); Nit: Maybe worth a comment on why this is expected to always succeed? I.e. I think we are assuming the only failure mode is allocation but=20 because we know vm_area_page_order() there shouldn't be any allocation?