[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aH_o-85T-EexGWrg@pc636>
Date: Tue, 22 Jul 2025 21:39:39 +0200
From: Uladzislau Rezki <urezki@...il.com>
To: Jia He <justin.he@....com>
Cc: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Uladzislau Rezki <urezki@...il.com>,
Anshuman Khandual <anshuman.khandual@....com>,
Ryan Roberts <ryan.roberts@....com>, Peter Xu <peterx@...hat.com>,
Joey Gouly <joey.gouly@....com>,
Yicong Yang <yangyicong@...ilicon.com>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH] mm: vmalloc: use VMALLOC_EARLY_START boundary for early
vmap area
On Tue, Jul 22, 2025 at 04:08:50AM +0000, Jia He wrote:
> When VMALLOC_START is redefined to a new boundary, most subsystems
> continue to function correctly. However, vm_area_register_early()
> assumes the use of the global _vmlist_ structure before vmalloc_init()
> is invoked. This assumption can lead to issues during early boot.
>
But we just should not redefine the macro. If there are such places
those are should be fixed, IMO.
--
Uladzislau Rezki
Powered by blists - more mailing lists