Re: [PATCH v1 4/4] Revert "x86/xen: allow nesting of same lazy mode"

2025-03-03 Thread David Hildenbrand
On 03.03.25 13:33, Ryan Roberts wrote: On 03/03/2025 11:52, David Hildenbrand wrote: On 02.03.25 15:55, Ryan Roberts wrote: Commit 49147beb0ccb ("x86/xen: allow nesting of same lazy mode") was added as a solution for a core-mm code change where arch_[enter|leave]_lazy_mmu_mode() started to be c

Re: [PATCH v1 4/4] Revert "x86/xen: allow nesting of same lazy mode"

2025-03-03 Thread Ryan Roberts
On 03/03/2025 11:52, David Hildenbrand wrote: > On 02.03.25 15:55, Ryan Roberts wrote: >> Commit 49147beb0ccb ("x86/xen: allow nesting of same lazy mode") was >> added as a solution for a core-mm code change where >> arch_[enter|leave]_lazy_mmu_mode() started to be called in a nested >> manner; see

Re: [PATCH v1 4/4] Revert "x86/xen: allow nesting of same lazy mode"

2025-03-03 Thread David Hildenbrand
On 02.03.25 15:55, Ryan Roberts wrote: Commit 49147beb0ccb ("x86/xen: allow nesting of same lazy mode") was added as a solution for a core-mm code change where arch_[enter|leave]_lazy_mmu_mode() started to be called in a nested manner; see commit bcc6cc832573 ("mm: add default definition of set_p

[PATCH v1 4/4] Revert "x86/xen: allow nesting of same lazy mode"

2025-03-02 Thread Ryan Roberts
Commit 49147beb0ccb ("x86/xen: allow nesting of same lazy mode") was added as a solution for a core-mm code change where arch_[enter|leave]_lazy_mmu_mode() started to be called in a nested manner; see commit bcc6cc832573 ("mm: add default definition of set_ptes()"). However, now that we have fixed