From: Will Deacon <will@kernel.org>
To: Dev Jain <dev.jain@arm.com>
Cc: catalin.marinas@arm.com, anshuman.khandual@arm.com,
quic_zhenhuah@quicinc.com, ryan.roberts@arm.com,
kevin.brodsky@arm.com, yangyicong@hisilicon.com,
joey.gouly@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, david@redhat.com,
mark.rutland@arm.com, urezki@gmail.com, jthoughton@google.com
Subject: Re: [RESEND PATCH v5] arm64: Enable vmalloc-huge with ptdump
Date: Fri, 19 Sep 2025 08:27:45 +0100 [thread overview]
Message-ID: <aM0F8U-cW6sh62H-@willie-the-truck> (raw)
In-Reply-To: <aMrXBArFNLTdwWs3@willie-the-truck>
Dev,
On Wed, Sep 17, 2025 at 04:43:00PM +0100, Will Deacon wrote:
> On Tue, Sep 16, 2025 at 11:30:26AM +0100, Will Deacon wrote:
> > I'm currently trying to put together a litmus test with James (cc'd) so
> > maybe we can help you out with that part.
>
> Here's what we came up with. There's not a good way to express the IPI
> from kick_all_cpus_sync() but it turns out that the ISB from the TLB
> invalidation is sufficient anyway. Does it make sense to you?
Any comments on the litmus test and/or my question about serialisation
of the static key? I'll be moving the arm64 tree to "fixes only" soon
as far as 6.18 is concerned.
Will
next prev parent reply other threads:[~2025-09-19 7:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 16:18 [RESEND PATCH v5] arm64: Enable vmalloc-huge with ptdump Dev Jain
2025-07-24 5:50 ` Anshuman Khandual
2025-07-24 7:20 ` Dev Jain
2025-07-30 17:00 ` Catalin Marinas
2025-07-30 18:29 ` Ryan Roberts
2025-07-31 4:30 ` Dev Jain
2025-07-31 11:38 ` Catalin Marinas
2025-07-31 7:12 ` Dev Jain
2025-07-31 17:06 ` Catalin Marinas
2025-08-01 12:15 ` Dev Jain
2025-08-01 15:48 ` Catalin Marinas
2025-09-16 10:30 ` Will Deacon
2025-09-17 15:43 ` Will Deacon
2025-09-19 7:27 ` Will Deacon [this message]
2025-09-19 7:46 ` Dev Jain
2025-09-19 10:28 ` Dev Jain
2025-09-19 10:59 ` Will Deacon
2025-09-19 12:14 ` Dev Jain
2025-09-19 12:26 ` Will Deacon
2025-09-19 7:53 ` Dev Jain
2025-09-19 8:11 ` Ryan Roberts
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=aM0F8U-cW6sh62H-@willie-the-truck \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=joey.gouly@arm.com \
--cc=jthoughton@google.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=quic_zhenhuah@quicinc.com \
--cc=ryan.roberts@arm.com \
--cc=urezki@gmail.com \
--cc=yangyicong@hisilicon.com \
/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