[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 04 Apr 2024 18:33:16 +0100
From: Marc Zyngier <maz@...nel.org>
To: Gavin Shan <gshan@...hat.com>
Cc: linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
catalin.marinas@....com,
will@...nel.org,
akpm@...ux-foundation.org,
oliver.upton@...ux.dev,
mark.rutland@....com,
ryan.roberts@....com,
apopple@...dia.com,
rananta@...gle.com,
yangyicong@...ilicon.com,
v-songbaohua@...o.com,
yezhenyu2@...wei.com,
yihyu@...hat.com,
shan.gavin@...il.com
Subject: Re: [PATCH v2] arm64: tlb: Fix TLBI RANGE operand
On Thu, 04 Apr 2024 11:26:20 +0100,
Gavin Shan <gshan@...hat.com> wrote:
>
> In summary, we need 3 patches but the one fixing __TLBI_RANGE_NUM needs to be
> PATCH[1/3] so that it can be easily picked by stable kernel. PATCH[2/3] would
> be to improve __TLBI_VADDR_RANGE with masks. PATCH[3/3] will allow __flush_tlb_range_nosync()
> to do range-based TLB flush for MAX_TLBI_RANGE_PAGES.
That's about it indeed.
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists