From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Oliver Upton <oupton@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v2] KVM: arm64: Don't populate TPIDR_EL2 in finalise_el2()
Date: Mon, 18 May 2026 16:39:30 +0100 [thread overview]
Message-ID: <86y0hgwwul.wl-maz@kernel.org> (raw)
In-Reply-To: <20260518153127.6078-1-will@kernel.org>
On Mon, 18 May 2026 16:31:26 +0100,
Will Deacon <will@kernel.org> wrote:
>
> Currently, it is not necessary for __finalise_el2() to configure
> TPIDR_EL2:
>
> * The hyp stub code does not consume the value of TPIDR_EL2.
>
> * On the boot cpu, TPIDR_EL1 is used for the percpu offset until the
> ARM64_HAS_VIRT_HOST_EXTN cpucap is detected and boot alternatives
> are patched. Before boot alternatives are patched,
> cpu_copy_el2regs() will copy TPIDR_EL1 into TPIDR_EL2. It is not
> necessary for __finalise_el2() to initialise TPIDR_EL2 before this.
>
> * Secondary CPUs are brought up after boot alternatives have been
> patched, and __secondary_switched() will initialize TPIDR_EL2 in
> 'init_cpu_task', after finalise_el2() calls __finalise_el2()
>
> * KVM hyp code which may consume TPIDR_EL2 is brought up after all
> secondaries have been booted, once TPIDR_El2 has been configured on
> all CPUs.
>
> Remove the redundant initialisation from __finalise_el2().
>
> Cc: Oliver Upton <oupton@kernel.org>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Reviewed-by: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Will Deacon <will@kernel.org>
Reviewed-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-05-18 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 15:31 [PATCH v2] KVM: arm64: Don't populate TPIDR_EL2 in finalise_el2() Will Deacon
2026-05-18 15:39 ` Marc Zyngier [this message]
2026-05-18 15:41 ` Marc Zyngier
2026-05-18 15:55 ` Will Deacon
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=86y0hgwwul.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=oupton@kernel.org \
--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