From: "Jürgen Groß" <jgross@suse.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org
Cc: kevin.brodsky@arm.com, mmarek@invisiblethingslab.com,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] x86/xen: Fix lazy mmu handling across context switch
Date: Fri, 8 May 2026 10:33:53 +0200 [thread overview]
Message-ID: <5cb54bd1-5981-4a46-9083-f7b527ca342f@suse.com> (raw)
In-Reply-To: <20260508080514.454607-1-jgross@suse.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 3688 bytes --]
Please disregard this patch. It isn't fixing the real problem.
On 08.05.26 10:05, Juergen Gross wrote:
> The recent rework of mmu lazy mode has resulted in problems when
> running as a Xen PV guest. Enabling lazy mmu mode for the new context
> during context switch is done from the arch_end_context_switch() hook,
> but when calling this hook current hasn't been changed yet, so the
> lazy mmu mode state of the wrong task is modified.
>
> Additionally it is much cleaner to use lazy_mmu_mode_pause() and
> lazy_mmu_mode_resume() in the Xen context switch hooks, as it avoids
> conditionals in those hooks.
>
> In order not having to add another hook to be called after switching
> current, modify lazy_mmu_mode_resume() to use a new sub-function which
> takes a task pointer as parameter. This new sub-function can then be
> used in the xen_end_context_switch() hook.
>
> Fixes: 291b3abed657 ("x86/xen: use lazy_mmu_state when context-switching")
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> arch/x86/xen/enlighten_pv.c | 7 ++-----
> include/linux/pgtable.h | 33 ++++++++++++++++++++++++---------
> 2 files changed, 26 insertions(+), 14 deletions(-)
>
> diff --git a/arch/x86/xen/enlighten_pv.c b/arch/x86/xen/enlighten_pv.c
> index ed2d7a3756ce..67bb6bf6d240 100644
> --- a/arch/x86/xen/enlighten_pv.c
> +++ b/arch/x86/xen/enlighten_pv.c
> @@ -424,9 +424,7 @@ static void xen_start_context_switch(struct task_struct *prev)
> {
> BUG_ON(preemptible());
>
> - if (this_cpu_read(xen_lazy_mode) == XEN_LAZY_MMU) {
> - arch_leave_lazy_mmu_mode();
> - }
> + lazy_mmu_mode_pause();
> enter_lazy(XEN_LAZY_CPU);
> }
>
> @@ -436,8 +434,7 @@ static void xen_end_context_switch(struct task_struct *next)
>
> xen_mc_flush();
> leave_lazy(XEN_LAZY_CPU);
> - if (__task_lazy_mmu_mode_active(next))
> - arch_enter_lazy_mmu_mode();
> + lazy_mmu_mode_resume_task(next);
> }
>
> static unsigned long xen_store_tr(void)
> diff --git a/include/linux/pgtable.h b/include/linux/pgtable.h
> index cdd68ed3ae1a..83a099bf2038 100644
> --- a/include/linux/pgtable.h
> +++ b/include/linux/pgtable.h
> @@ -326,6 +326,28 @@ static inline void lazy_mmu_mode_pause(void)
> arch_leave_lazy_mmu_mode();
> }
>
> +/**
> + * lazy_mmu_mode_resume_task() - Resume the lazy MMU mode for a specific task.
> + *
> + * Like lazy_mmu_mode_resume() below, but with a task specified.
> + * Must be called only by lazy_mmu_mode_resume() or during context switch.
> + * Must never be called in interrupt context.
> + *
> + * Must match a call to lazy_mmu_mode_pause().
> + *
> + * Has no effect if called:
> + * - While paused (inside another pause()/resume() pair)
> + */
> +static inline void lazy_mmu_mode_resume_task(struct task_struct *task)
> +{
> + struct lazy_mmu_state *state = &task->lazy_mmu_state;
> +
> + VM_WARN_ON_ONCE(state->pause_count == 0);
> +
> + if (--state->pause_count == 0 && state->enable_count > 0)
> + arch_enter_lazy_mmu_mode();
> +}
> +
> /**
> * lazy_mmu_mode_resume() - Resume the lazy MMU mode.
> *
> @@ -341,15 +363,8 @@ static inline void lazy_mmu_mode_pause(void)
> */
> static inline void lazy_mmu_mode_resume(void)
> {
> - struct lazy_mmu_state *state = ¤t->lazy_mmu_state;
> -
> - if (in_interrupt())
> - return;
> -
> - VM_WARN_ON_ONCE(state->pause_count == 0);
> -
> - if (--state->pause_count == 0 && state->enable_count > 0)
> - arch_enter_lazy_mmu_mode();
> + if (!in_interrupt())
> + lazy_mmu_mode_resume_task(current);
> }
> #else
> static inline void lazy_mmu_mode_enable(void) {}
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2026-05-08 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 8:05 [PATCH] x86/xen: Fix lazy mmu handling across context switch Juergen Gross
2026-05-08 8:33 ` Jürgen Groß [this message]
2026-05-08 9:08 ` Kevin Brodsky
2026-05-08 9:30 ` Kevin Brodsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5cb54bd1-5981-4a46-9083-f7b527ca342f@suse.com \
--to=jgross@suse.com \
--cc=akpm@linux-foundation.org \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=hpa@zytor.com \
--cc=kevin.brodsky@arm.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=mmarek@invisiblethingslab.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tglx@kernel.org \
--cc=vbabka@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox