From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, npiggin@gmail.com,
christophe.leroy@csgroup.eu,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: willy@infradead.org
Subject: Re: [PATCH v2] powerpc/mm: Avoid calling arch_enter/leave_lazy_mmu() in set_ptes
Date: Fri, 27 Oct 2023 20:46:51 +1100 [thread overview]
Message-ID: <169840001174.2695453.15255074360035893405.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20231024143604.16749-1-aneesh.kumar@linux.ibm.com>
On Tue, 24 Oct 2023 20:06:04 +0530, Aneesh Kumar K.V wrote:
> With commit 9fee28baa601 ("powerpc: implement the new page table range
> API") we added set_ptes to powerpc architecture. The implementation
> included calling arch_enter/leave_lazy_mmu() calls.
>
> The patch removes the usage of arch_enter/leave_lazy_mmu() because
> set_pte is not supposed to be used when updating a pte entry. Powerpc
> architecture uses this rule to skip the expensive tlb invalidate which
> is not needed when you are setting up the pte for the first time. See
> commit 56eecdb912b5 ("mm: Use ptep/pmdp_set_numa() for updating
> _PAGE_NUMA bit") for more details
>
> [...]
Applied to powerpc/fixes.
[1/1] powerpc/mm: Avoid calling arch_enter/leave_lazy_mmu() in set_ptes
https://git.kernel.org/powerpc/c/47b8def9358c5eb888e78b24b7e5b7f2e2e97b8e
cheers
next prev parent reply other threads:[~2023-10-27 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 14:36 [PATCH v2] powerpc/mm: Avoid calling arch_enter/leave_lazy_mmu() in set_ptes Aneesh Kumar K.V
2023-10-27 9:46 ` Michael Ellerman [this message]
2023-10-27 10:50 ` Matthew Wilcox
2023-11-02 11:39 ` Michael Ellerman
2023-11-11 10:33 ` Christophe Leroy
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=169840001174.2695453.15255074360035893405.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.