Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Marc Zyngier <maz@kernel.org>
To:     Will Deacon <will@kernel.org>, David Brazdil <dbrazdil@google.com>,
        Catalin Marinas <catalin.marinas@arm.com>
Cc:     kernel-team@google.com, clang-built-linux@googlegroups.com,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        android-kvm@google.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] KVM: arm64: Ensure that all nVHE hyp code is in .hyp.text
Date:   Thu, 30 Jul 2020 14:52:09 +0100
Message-Id: <159611709973.1644456.15046238262603869142.b4-ty@kernel.org>
In-Reply-To: <20200730132519.48787-1-dbrazdil@google.com>
References: <20200730132519.48787-1-dbrazdil@google.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, 30 Jul 2020 14:25:19 +0100, David Brazdil wrote:
> Some compilers may put a subset of generated functions into '.text.*'
> ELF sections and the linker may leverage this division to optimize ELF
> layout. Unfortunately, the recently introduced HYPCOPY command assumes
> that all executable code (with the exception of specialized sections
> such as '.hyp.idmap.text') is in the '.text' section. If this
> assumption is broken, code in '.text.*' will be merged into kernel
> proper '.text' instead of the '.hyp.text' that is mapped in EL2.
> 
> [...]

Applied to kvm-arm64/el2-obj-v4.1, thanks!

[1/1] KVM: arm64: Ensure that all nVHE hyp code is in .hyp.text
      commit: bdbc0c7a070c0cbe3009cd271c6ec8d87d69cc7a

Cheers,

	M.
-- 
Without deviation from the norm, progress is not possible.