From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Imre Kaloz <kaloz@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Andreas Larsson <andreas@gaisler.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
"Mike Rapoport (IBM)" <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] sparc64: D-cache alias flushing fixes
Date: Sun, 27 Sep 2026 23:22:36 +0200 [thread overview]
Message-ID: <3d0f0b6aa7ccaad25d04c5cdf0475d2d030c78e9.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20260927105539.8742-1-kaloz@kernel.org>
Hi Imre,
On Sun, 2026-09-27 at 12:55 +0200, Imre Kaloz wrote:
> Two fixes to D-cache alias flushing on sparc64 CPUs with a virtually
> indexed L1 D-cache.
>
> Patch 1 makes move_pte() and tlb_batch_add() flush only the page a PTE
> maps, instead of every page of its folio once per PTE, so the number
> of cross-calls for an mremap() of a large folio no longer grows with
> the square of its size.
>
> Patch 2 implements flush_cache_vmap() and flush_cache_vunmap(), which
> have been no-ops on sparc64. Stale lines left by a vmalloc mapping
> corrupt BPF programs and module data on UltraSPARC III. It uses
> flush_dcache_page_all() as patch 1 restores it.
>
> Both patches are tagged for stable. Tested on a Sun Ultra 45.
>
> Imre Kaloz (2):
> sparc64: flush only the aliased page, not its whole folio
> sparc64: flush vmalloc ranges from the D-cache on map and unmap
>
> arch/sparc/include/asm/cacheflush_64.h | 9 ++--
> arch/sparc/include/asm/pgtable_64.h | 7 ++-
> arch/sparc/kernel/smp_64.c | 42 ++++++++++++-----
> arch/sparc/mm/init_64.c | 64 ++++++++++++++++++++++++++
> arch/sparc/mm/tlb.c | 2 +-
> arch/sparc/mm/ultra.S | 25 ++++++++++
> 6 files changed, 131 insertions(+), 18 deletions(-)
>
>
> base-commit: fe2ec83746e501645709761605c2464a44fd2929
Would you mind reporting the bugs that these patches fix in the sparclinux
issue tracker on GitHub [1]? The reason I'm asking is that there has been
recently a strong uptick of patches for SPARC and I want to make sure we're
not missing any when Andreas gets back to reviewing patches.
Adrian
> [1] https://github.com/sparclinux/issues/issues
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2026-09-27 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 10:55 Imre Kaloz
2026-09-27 10:55 ` [PATCH 1/2] sparc64: flush only the aliased page, not its whole folio Imre Kaloz
2026-09-28 9:19 ` Stian Halseth
2026-09-27 10:55 ` [PATCH 2/2] sparc64: flush vmalloc ranges from the D-cache on map and unmap Imre Kaloz
2026-09-28 10:33 ` Stian Halseth
2026-09-28 13:18 ` Imre Kaloz
2026-09-28 14:04 ` Stian Halseth
2026-09-27 21:22 ` John Paul Adrian Glaubitz [this message]
2026-09-28 8:49 ` [PATCH 0/2] sparc64: D-cache alias flushing fixes Imre Kaloz
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=3d0f0b6aa7ccaad25d04c5cdf0475d2d030c78e9.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=kaloz@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=sparclinux@vger.kernel.org \
--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 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®