[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <165805475449.3537183.8979480362090216052.b4-ty@kernel.org>
Date: Sun, 17 Jul 2022 11:46:39 +0100
From: Marc Zyngier <maz@...nel.org>
To: mark.rutland@....com, broonie@...nel.org,
Kalesh Singh <kaleshsingh@...gle.com>, tabba@...gle.com,
madvenka@...ux.microsoft.com
Cc: linux-arm-kernel@...ts.infradead.org,
Suzuki K Poulose <suzuki.poulose@....com>,
James Morse <james.morse@....com>, will@...nel.org,
Alexandru Elisei <alexandru.elisei@....com>,
kernel-team@...roid.com, kvmarm@...ts.cs.columbia.edu,
qperret@...gle.com, linux-kernel@...r.kernel.org,
Catalin Marinas <catalin.marinas@....com>
Subject: Re: [PATCH] KVM: arm64: Fix hypervisor address symbolization
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@...nel.org>
Powered by blists - more mailing lists