Re: [PATCH v1 0/4] mm: Fix apply_to_pte_range() vs lazy MMU mode

2025-04-11 Thread Alexander Gordeev
On Fri, Apr 11, 2025 at 05:12:28PM +1000, Nicholas Piggin wrote: ... > Huh. powerpc actually has some crazy code in __switch_to() that is > supposed to handle preemption while in lazy mmu mode. So we probably > don't even need to disable preemption, just use the raw per-cpu > accessors (or keep dis

Re: [PATCH v1 0/4] mm: Fix apply_to_pte_range() vs lazy MMU mode

2025-04-11 Thread Nicholas Piggin
On Tue Apr 8, 2025 at 1:11 AM AEST, Alexander Gordeev wrote: > Hi All, > > This series is an attempt to fix the violation of lazy MMU mode context > requirement as described for arch_enter_lazy_mmu_mode(): > > This mode can only be entered and left under the protection of > the page table l

Re: [PATCH v1 0/4] mm: Fix apply_to_pte_range() vs lazy MMU mode

2025-04-07 Thread Andrew Morton
On Mon, 7 Apr 2025 17:11:26 +0200 Alexander Gordeev wrote: > This series is an attempt to fix the violation of lazy MMU mode context > requirement as described for arch_enter_lazy_mmu_mode(): > > This mode can only be entered and left under the protection of > the page table locks for

[PATCH v1 0/4] mm: Fix apply_to_pte_range() vs lazy MMU mode

2025-04-07 Thread Alexander Gordeev
Hi All, This series is an attempt to fix the violation of lazy MMU mode context requirement as described for arch_enter_lazy_mmu_mode(): This mode can only be entered and left under the protection of the page table locks for all page tables which may be modified. On s390 if I make arch_e