From: Anshuman Khandual <anshuman.khandual@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: ben.horgan@arm.com, Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev
Subject: Re: [PATCH V2 0/2] arm64/mm: Add remaining TLBI_XXX_MASK macros
Date: Thu, 13 Nov 2025 14:45:12 +0530 [thread overview]
Message-ID: <116d9f13-b82a-4361-9a62-c0207da25576@arm.com> (raw)
In-Reply-To: <20251024040207.137480-1-anshuman.khandual@arm.com>
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@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Oliver Upton <oliver.upton@linux.dev>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Cc: kvmarm@lists.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 ?
prev parent reply other threads:[~2025-11-13 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 4:02 Anshuman Khandual
2025-10-24 4:02 ` [PATCH V2 1/2] arm64/mm: Drop redundant 'level' range trimming in __tlbi_level() Anshuman Khandual
2025-10-24 4:02 ` [PATCH V2 2/2] arm64/mm: Add remaining TLBI_XXX_MASK macros Anshuman Khandual
2025-10-24 8:56 ` Ben Horgan
2025-10-27 1:14 ` Anshuman Khandual
2025-10-24 11:00 ` Jonathan Cameron
2025-10-27 1:36 ` Anshuman Khandual
2025-10-28 12:43 ` Jonathan Cameron
2025-10-30 2:41 ` Anshuman Khandual
2025-11-13 9:15 ` Anshuman Khandual [this message]
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=116d9f13-b82a-4361-9a62-c0207da25576@arm.com \
--to=anshuman.khandual@arm.com \
--cc=ben.horgan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®