mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Imre Kaloz <kaloz@kernel.org>
To: Stian Halseth <stian@itx.no>
Cc: "David S. Miller" <davem@davemloft.net>,
	Andreas Larsson <andreas@gaisler.com>,
	"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,
	nsafran1217 <54966414+nsafran1217@users.noreply.github.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 2/2] sparc64: flush vmalloc ranges from the D-cache on map and unmap
Date: Mon, 28 Sep 2026 15:18:28 +0200	[thread overview]
Message-ID: <20260928131828.1504-1-kaloz@kernel.org> (raw)
In-Reply-To: <1330dc280f59571c1f624ccada069b73cd8624a3.camel@itx.no>

Hi Stian,

> Since the vmemmap has no aliases to flush, I suggest we skip
> anything outside vmalloc and module space, like this:

Thanks for chasing this down. Confirmed the path: dcache_size is
still 0 there, so the old code took the "exceeds cache size" branch
into flush_dcache_all() every time, and the mondo block PA is 0
until init_IRQ() runs, so the cross-call landed on physical address
0 instead of a real mondo queue. Skipping non-vmalloc/module
addresses is the right fix.

v2 with your check and your Tested-by follows.


Best,
Imre

  reply	other threads:[~2026-09-28 13:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27 10:55 [PATCH 0/2] sparc64: D-cache alias flushing fixes 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 [this message]
2026-09-28 14:04       ` Stian Halseth
2026-09-27 21:22 ` [PATCH 0/2] sparc64: D-cache alias flushing fixes John Paul Adrian Glaubitz
2026-09-28  8:49   ` 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=20260928131828.1504-1-kaloz@kernel.org \
    --to=kaloz@kernel.org \
    --cc=54966414+nsafran1217@users.noreply.github.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreas@gaisler.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rppt@kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stian@itx.no \
    --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®