linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Juergen Gross <jgross@suse.com>,
	Erhard Furtner <erhard_f@mailbox.org>,
	"Matthew Wilcox \(Oracle\)" <willy@infradead.org>,
	linux-sparc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	David Woodhouse <dwmw2@infradead.org>
Subject: [PATCH 2/2] sparc: Allow nesting of lazy MMU mode
Date: Thu, 12 Oct 2023 20:54:15 +0100	[thread overview]
Message-ID: <20231012195415.282357-3-willy@infradead.org> (raw)
In-Reply-To: <20231012195415.282357-1-willy@infradead.org>

As noted in commit 49147beb0ccb ("x86/xen: allow nesting of same lazy
mode"), we can now nest calls to arch_enter_lazy_mmu_mode().  Use ->active
as a counter instead of a flag and only drain the batch when the counter
hits 0.

Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Fixes: bcc6cc832573 ("mm: add default definition of set_ptes()")
---
 arch/sparc/mm/tlb.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/arch/sparc/mm/tlb.c b/arch/sparc/mm/tlb.c
index b44d79d778c7..a82c7c32e47d 100644
--- a/arch/sparc/mm/tlb.c
+++ b/arch/sparc/mm/tlb.c
@@ -54,16 +54,15 @@ void arch_enter_lazy_mmu_mode(void)
 {
 	struct tlb_batch *tb = this_cpu_ptr(&tlb_batch);
 
-	tb->active = 1;
+	tb->active++;
 }
 
 void arch_leave_lazy_mmu_mode(void)
 {
 	struct tlb_batch *tb = this_cpu_ptr(&tlb_batch);
 
-	if (tb->tlb_nr)
+	if ((--tb->active == 0) && tb->tlb_nr)
 		flush_tlb_pending();
-	tb->active = 0;
 }
 
 static void tlb_batch_add_one(struct mm_struct *mm, unsigned long vaddr,
-- 
2.40.1


  parent reply	other threads:[~2023-10-12 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 19:54 [PATCH 0/2] Allow nesting of lazy MMU mode Matthew Wilcox (Oracle)
2023-10-12 19:54 ` [PATCH 1/2] powerpc: " Matthew Wilcox (Oracle)
2023-10-12 19:54 ` Matthew Wilcox (Oracle) [this message]
2023-10-13 13:42 ` [PATCH 0/2] " Erhard Furtner
2023-10-17  6:04   ` Aneesh Kumar K.V
2023-10-17 23:14     ` Erhard Furtner

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=20231012195415.282357-3-willy@infradead.org \
    --to=willy@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=erhard_f@mailbox.org \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sparc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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).