From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Alexander Gordeev" <agordeev@linux.ibm.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Andrey Ryabinin" <ryabinin.a.a@gmail.com>
Cc: "Hugh Dickins" <hughd@google.com>,
"Guenter Roeck" <linux@roeck-us.net>,
"Juergen Gross" <jgross@suse.com>,
"Jeremy Fitzhardinge" <jeremy@goop.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<kasan-dev@googlegroups.com>, <sparclinux@vger.kernel.org>,
<xen-devel@lists.xenproject.org>, <linuxppc-dev@lists.ozlabs.org>,
<linux-s390@vger.kernel.org>
Subject: Re: [PATCH v1 2/4] mm: Cleanup apply_to_pte_range() routine
Date: Fri, 11 Apr 2025 16:46:58 +1000 [thread overview]
Message-ID: <D93LW58FLXOS.2U8X0CO2H9H5S@gmail.com> (raw)
In-Reply-To: <93102722541b1daf541fce9fb316a1a2614d8c86.1744037648.git.agordeev@linux.ibm.com>
On Tue Apr 8, 2025 at 1:11 AM AEST, Alexander Gordeev wrote:
> Reverse 'create' vs 'mm == &init_mm' conditions and move
> page table mask modification out of the atomic context.
>
> Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
> ---
> mm/memory.c | 28 +++++++++++++++++-----------
> 1 file changed, 17 insertions(+), 11 deletions(-)
>
> diff --git a/mm/memory.c b/mm/memory.c
> index 2d8c265fc7d6..f0201c8ec1ce 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -2915,24 +2915,28 @@ static int apply_to_pte_range(struct mm_struct *mm, pmd_t *pmd,
> pte_fn_t fn, void *data, bool create,
> pgtbl_mod_mask *mask)
> {
> + int err = create ? -ENOMEM : -EINVAL;
Could you make this a new variable instead of reusing
existing err? 'const int pte_err' or something?
> pte_t *pte, *mapped_pte;
> - int err = 0;
> spinlock_t *ptl;
>
> - if (create) {
> - mapped_pte = pte = (mm == &init_mm) ?
> - pte_alloc_kernel_track(pmd, addr, mask) :
> - pte_alloc_map_lock(mm, pmd, addr, &ptl);
> + if (mm == &init_mm) {
> + if (create)
> + pte = pte_alloc_kernel_track(pmd, addr, mask);
> + else
> + pte = pte_offset_kernel(pmd, addr);
> if (!pte)
> - return -ENOMEM;
> + return err;
> } else {
> - mapped_pte = pte = (mm == &init_mm) ?
> - pte_offset_kernel(pmd, addr) :
> - pte_offset_map_lock(mm, pmd, addr, &ptl);
> + if (create)
> + pte = pte_alloc_map_lock(mm, pmd, addr, &ptl);
> + else
> + pte = pte_offset_map_lock(mm, pmd, addr, &ptl);
> if (!pte)
> - return -EINVAL;
> + return err;
> + mapped_pte = pte;
> }
>
> + err = 0;
> arch_enter_lazy_mmu_mode();
>
> if (fn) {
> @@ -2944,12 +2948,14 @@ static int apply_to_pte_range(struct mm_struct *mm, pmd_t *pmd,
> }
> } while (addr += PAGE_SIZE, addr != end);
> }
> - *mask |= PGTBL_PTE_MODIFIED;
>
> arch_leave_lazy_mmu_mode();
>
> if (mm != &init_mm)
> pte_unmap_unlock(mapped_pte, ptl);
> +
> + *mask |= PGTBL_PTE_MODIFIED;
This is done just because we might as well? Less work in critical
section?
Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
> +
> return err;
> }
>
next prev parent reply other threads:[~2025-04-11 6:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 15:11 [PATCH v1 0/4] mm: Fix apply_to_pte_range() vs lazy MMU mode Alexander Gordeev
2025-04-07 15:11 ` [PATCH v1 1/4] kasan: Avoid sleepable page allocation from atomic context Alexander Gordeev
2025-04-11 6:40 ` Nicholas Piggin
2025-04-11 6:54 ` Nicholas Piggin
2025-04-07 15:11 ` [PATCH v1 2/4] mm: Cleanup apply_to_pte_range() routine Alexander Gordeev
2025-04-11 6:46 ` Nicholas Piggin [this message]
2025-04-14 14:17 ` Alexander Gordeev
2025-04-07 15:11 ` [PATCH v1 3/4] mm: Protect kernel pgtables in apply_to_pte_range() Alexander Gordeev
2025-04-11 6:53 ` Nicholas Piggin
2025-04-07 15:11 ` [PATCH v1 4/4] mm: Allow detection of wrong arch_enter_lazy_mmu_mode() context Alexander Gordeev
2025-04-11 7:16 ` Nicholas Piggin
2025-04-07 18:35 ` [PATCH v1 0/4] mm: Fix apply_to_pte_range() vs lazy MMU mode Andrew Morton
2025-04-11 7:12 ` Nicholas Piggin
2025-04-11 12:04 ` Alexander Gordeev
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=D93LW58FLXOS.2U8X0CO2H9H5S@gmail.com \
--to=npiggin@gmail.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=jeremy@goop.org \
--cc=jgross@suse.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ryabinin.a.a@gmail.com \
--cc=sparclinux@vger.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;
as well as URLs for NNTP newsgroup(s).