Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Marc Zyngier <maz@kernel.org>
To:     mark.rutland@arm.com, broonie@kernel.org,
        Kalesh Singh <kaleshsingh@google.com>, tabba@google.com,
        madvenka@linux.microsoft.com
Cc:     linux-arm-kernel@lists.infradead.org,
        Suzuki K Poulose <suzuki.poulose@arm.com>,
        James Morse <james.morse@arm.com>, will@kernel.org,
        Alexandru Elisei <alexandru.elisei@arm.com>,
        kernel-team@android.com, kvmarm@lists.cs.columbia.edu,
        qperret@google.com, linux-kernel@vger.kernel.org,
        Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH] KVM: arm64: Fix hypervisor address symbolization
Date:   Sun, 17 Jul 2022 11:46:39 +0100
Message-Id: <165805475449.3537183.8979480362090216052.b4-ty@kernel.org>
In-Reply-To: <20220715235824.2549012-1-kaleshsingh@google.com>
References: <20220715235824.2549012-1-kaleshsingh@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 15 Jul 2022 16:58:24 -0700, Kalesh Singh wrote:
> With CONFIG_RANDOMIZE_BASE=y vmlinux addresses will resolve correctly
> from kallsyms. Fix this by adding the KASLR offset before printing the
> symbols.
> 
> Based on arm64 for-next/stacktrace.

Applied to next, thanks!

[1/1] KVM: arm64: Fix hypervisor address symbolization
      commit: ed6313a93fd11d2015ad17046f3c418bf6a8dab1

Cheers,

	M.
-- 
Marc Zyngier <maz@kernel.org>