linux-kernel - Re: [PATCH V2 0/2] arm64/mm: Add remaining TLBI_XXX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <116d9f13-b82a-4361-9a62-c0207da25576@arm.com>
Date: Thu, 13 Nov 2025 14:45:12 +0530
From: Anshuman Khandual <anshuman.khandual@....com>
To: linux-arm-kernel@...ts.infradead.org
Cc: ben.horgan@....com, Catalin Marinas <catalin.marinas@....com>,
 Will Deacon <will@...nel.org>, Marc Zyngier <maz@...nel.org>,
 Oliver Upton <oliver.upton@...ux.dev>, linux-kernel@...r.kernel.org,
 kvmarm@...ts.linux.dev
Subject: Re: [PATCH V2 0/2] arm64/mm: Add remaining TLBI_XXX_MASK macros

On 24/10/25 9:32 AM, Anshuman Khandual wrote:
> Add remaining TLBI_XXX_MASK macros. But before that drop one redundant
> 'level' trimming operation in __tlbi_level().
> 
> Changes in V2:
> 
> - Added KVM changes required to accommodate TLBI_TTL_MASK split
> - Updated the commit message
> 
> Changes in V1:
> 
> https://lore.kernel.org/all/20251021052022.2898275-1-anshuman.khandual@arm.com/
> 
> Cc: Catalin Marinas <catalin.marinas@....com>
> Cc: Will Deacon <will@...nel.org>
> Cc: Marc Zyngier <maz@...nel.org> 
> Cc: Oliver Upton <oliver.upton@...ux.dev>
> Cc: linux-arm-kernel@...ts.infradead.org
> Cc: linux-kernel@...r.kernel.org
> Cc: kvmarm@...ts.linux.dev
> 
> Anshuman Khandual (2):
>   arm64/mm: Drop redundant 'level' range trimming in __tlbi_level()
>   arm64/mm: Add remaining TLBI_XXX_MASK macros
> 
>  arch/arm64/include/asm/tlbflush.h | 26 ++++++++++++++++++--------
>  arch/arm64/kvm/nested.c           |  8 +++++---
>  2 files changed, 23 insertions(+), 11 deletions(-)
> 

Gentle ping. Any updates or concerns regarding these changes ?