[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <171283217883.1337455.2882364241442501889.b4-ty@kernel.org>
Date: Fri, 12 Apr 2024 17:06:39 +0100
From: Will Deacon <will@...nel.org>
To: linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Gavin Shan <gshan@...hat.com>
Cc: catalin.marinas@....com,
kernel-team@...roid.com,
Will Deacon <will@...nel.org>,
akpm@...ux-foundation.org,
maz@...nel.org,
oliver.upton@...ux.dev,
ryan.roberts@....com,
apopple@...dia.com,
rananta@...gle.com,
mark.rutland@....com,
v-songbaohua@...o.com,
yangyicong@...ilicon.com,
shahuang@...hat.com,
yihyu@...hat.com,
shan.gavin@...il.com
Subject: Re: [PATCH v3 0/3] arm64: tlb: Fix TLBI RANGE operand
On Fri, 05 Apr 2024 13:58:49 +1000, Gavin Shan wrote:
> A kernel crash on the destination VM after the live migration was
> reported by Yihuang Yu. The issue is only reproducible on NVidia's
> grace-hopper where TLBI RANGE feature is available. The kernel crash
> is caused by incomplete TLB flush and missed dirty page. For the
> root cause and analysis, please refer to PATCH[v3 1/3]'s commit log.
>
> Thanks to Marc Zyngier who proposed all the code changes.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/3] arm64: tlb: Fix TLBI RANGE operand
(no commit info)
[2/3] arm64: tlb: Improve __TLBI_VADDR_RANGE()
https://git.kernel.org/arm64/c/e07255d69702
[3/3] arm64: tlb: Allow range operation for MAX_TLBI_RANGE_PAGES
https://git.kernel.org/arm64/c/73301e464a72
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists