From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.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>
Subject: Re: [PATCH 3/5] mm: Refactor lazy_mmu_mode_pause() and lazy_mmu_mode_resume()
Date: Mon, 1 Jun 2026 17:09:47 +0200 [thread overview]
Message-ID: <e0a80cc9-03b3-40b4-a6e8-ac0fa00b7aad@kernel.org> (raw)
In-Reply-To: <20260526150514.129330-4-jgross@suse.com>
On 5/26/26 17:05, Juergen Gross wrote:
> In order to allow pausing and resuming MMU lazy mode for other tasks
> than current, refactor lazy_mmu_mode_pause() and
> lazy_mmu_mode_resume().
>
> This will be needed when dropping the Xen PV private lazy MMU
> bookkeeping.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
next prev parent reply other threads:[~2026-06-01 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 15:05 [PATCH 0/5] x86/xen: Get rid of Xen private lazy MMU mode tracking Juergen Gross
2026-05-26 15:05 ` [PATCH 1/5] x86/xen: Drop lazy mode from trace entries Juergen Gross
2026-05-26 15:05 ` [PATCH 2/5] x86/xen: Change interface of xen_mc_issue() Juergen Gross
2026-05-26 15:05 ` [PATCH 3/5] mm: Refactor lazy_mmu_mode_pause() and lazy_mmu_mode_resume() Juergen Gross
2026-06-01 15:09 ` David Hildenbrand (Arm) [this message]
2026-05-26 15:05 ` [PATCH 4/5] x86/xen: Get rid of last XEN_LAZY_MMU uses Juergen Gross
2026-05-26 15:05 ` [PATCH 5/5] x86/xen: Replace generic lazy tracking with cpu specific one Juergen Gross
2026-06-01 15:08 ` [PATCH 0/5] x86/xen: Get rid of Xen private lazy MMU mode tracking David Hildenbrand (Arm)
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=e0a80cc9-03b3-40b4-a6e8-ac0fa00b7aad@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jgross@suse.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=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.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
all inboxes | Powered by JetHome®