[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4f5df85d-b238-4e12-8654-cab771454c49@arm.com>
Date: Fri, 19 Sep 2025 13:16:18 +0530
From: Dev Jain <dev.jain@....com>
To: Will Deacon <will@...nel.org>
Cc: catalin.marinas@....com, anshuman.khandual@....com,
quic_zhenhuah@...cinc.com, ryan.roberts@....com, kevin.brodsky@....com,
yangyicong@...ilicon.com, joey.gouly@....com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
david@...hat.com, mark.rutland@....com, urezki@...il.com,
jthoughton@...gle.com
Subject: Re: [RESEND PATCH v5] arm64: Enable vmalloc-huge with ptdump
On 19/09/25 12:57 pm, Will Deacon wrote:
> 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.
Sorry, I had read your replies but thought I will take time to respond since
it seemed this patch wouldn't land in 6.18, and I need to recall the discussion :)
I'll reply to the other mail.
>
> Will
Powered by blists - more mailing lists