Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Marc Zyngier <maz@kernel.org>,
	Oliver Upton <oliver.upton@linux.dev>,
	Mark Brown <broonie@kernel.org>,
	Ryan Roberts <ryan.roberts@arm.com>,
	kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 2/2] arm64/sysreg: Replace TCR_EL1 field macros
Date: Fri, 19 Sep 2025 14:52:40 +0530	[thread overview]
Message-ID: <554e507a-1a68-4ae9-9345-5aea0a81ba2b@arm.com> (raw)
In-Reply-To: <aMv2J1hRQm_f4WAP@willie-the-truck>

On 18/09/25 5:38 PM, Will Deacon wrote:
> On Sun, Sep 07, 2025 at 06:00:00PM +0530, Anshuman Khandual wrote:
>> This just replaces all used TCR_EL1 field macros with tools sysreg variant
>> based fields and subsequently drops them from the header (pgtable-hwdef.h)
>> and moves all required macros into KVM header (asm/kvm_arm.h) for continued
>> usage in KVM.
>>
>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>> Cc: Will Deacon <will@kernel.org>
>> Cc: Marc Zyngier <maz@kernel.org>
>> Cc: Mark Brown <broonie@kernel.org>
>> Cc: kvmarm@lists.linux.dev
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: linux-kernel@vger.kernel.org
>> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
>> ---
>> Changes in V4:
>>
>> - Dropped all unused TCR_XXX macros while moving into KVM header
>>
>>  arch/arm64/include/asm/assembler.h     |  6 +-
>>  arch/arm64/include/asm/cputype.h       |  2 +-
>>  arch/arm64/include/asm/kvm_arm.h       | 43 +++++++++++
>>  arch/arm64/include/asm/mmu_context.h   |  4 +-
>>  arch/arm64/include/asm/pgtable-hwdef.h | 98 +-------------------------
>>  arch/arm64/include/asm/pgtable-prot.h  |  2 +-
>>  arch/arm64/kernel/cpufeature.c         |  4 +-
>>  arch/arm64/kernel/pi/map_kernel.c      |  8 +--
>>  arch/arm64/kernel/vmcore_info.c        |  2 +-
>>  arch/arm64/mm/proc.S                   | 36 ++++++----
>>  tools/arch/arm64/include/asm/cputype.h |  2 +-
> 
> Please don't mix tools/ patches with arch patches. You probably want to keep
> the KVM one separate as well.

Sure, will split these changes in the following order.

- arm64 tool sysreg update for TCR_EL1
- Tools header update for TCR_NFD0/1
- Kernel update
- KVM specific update i.e header macro movement


  reply	other threads:[~2025-09-19  9:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07 12:29 [PATCH V4 0/2] arm64/sysreg: Clean up TCR_EL1 field macros Anshuman Khandual
2025-09-07 12:29 ` [PATCH V4 1/2] arm64/sysreg: Update TCR_EL1 register Anshuman Khandual
2025-09-08 13:58   ` Mark Brown
2025-09-09  3:50     ` Anshuman Khandual
2025-09-09 11:22       ` Mark Brown
2025-09-07 12:30 ` [PATCH V4 2/2] arm64/sysreg: Replace TCR_EL1 field macros Anshuman Khandual
2025-09-18 12:08   ` Will Deacon
2025-09-19  9:22     ` Anshuman Khandual [this message]
2025-09-15  2:24 ` [PATCH V4 0/2] arm64/sysreg: Clean up " Anshuman Khandual

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=554e507a-1a68-4ae9-9345-5aea0a81ba2b@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=broonie@kernel.org \
    --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=ryan.roberts@arm.com \
    --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