On Tue, Sep 20, 2022 at 02:20:48PM +0100, Alexandru Elisei wrote: > Hi, > > On Tue, Sep 20, 2022 at 10:45:53AM +0200, Andrew Jones wrote: > > On Tue, Aug 09, 2022 at 10:15:44AM +0100, Alexandru Elisei wrote: > > > With powerpc moving the page allocator, there are no architectures left > > > which use the physical allocator after the boot setup: arm, arm64, > > > s390x and powerpc drain the physical allocator to initialize the page > > > allocator; and x86 calls setup_vm() to drain the allocator for each of > > > the tests that allocate memory. > > > > Please put the motivation for this change in the commit message. I looked > > ahead at the next patch to find it, but I'm not sure I agree with it. We > > should be able to keep the locking even when used early, since we probably > > need our locking to be something we can use early elsewhere anyway. > > You are correct, the commit message doesn't explain why locking is removed, > which makes the commit confusing. I will try to do a better job for the > next iteration (if we decide to keep this patch). > > I removed locking because the physical allocator by the end of the series > will end up being used only by arm64 to create the idmap, which is done on If only arm, and no unit tests, needs the phys allocator, then it can be integrated with whatever arm is using it for and removed from the general lib. > the boot CPU and with the MMU off. After that, the translation table > allocator functions will use the page allocator, which can be used > concurrently. > > Looking at the spinlock implementation, spin_lock() doesn't protect from > the concurrent accesses when the MMU is disabled (lock->v is > unconditionally set to 1). Which means that spin_lock() does not work (in > the sense that it doesn't protect against concurrent accesses) on the boot > path, which doesn't need a spinlock anyway, because no secondaries are > online secondaries. It also means that spinlocks don't work when > AUXINFO_MMU_OFF is set. So for the purpose of simplicity I preferred to > drop it entirely. If other architectures or unit tests have / could have uses for the phys allocator then we should either document that it doesn't have locks or keep the locks, and arm will just know that they don't work, but also that they don't need to for its purposes. Finally, if we drop the locks and arm doesn't have any other places where we use locks without the MMU enabled, then we can change the lock implementation to not have the no-mmu fallback - maybe by switching to the generic implementation as the other architectures have done. Thanks, drew
