[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161237062025.1419625.13086305573512898143.b4-ty@kernel.org>
Date: Wed, 3 Feb 2021 16:43:48 +0000
From: Marc Zyngier <maz@...nel.org>
To: arnd@...db.de, Quentin Perret <qperret@...gle.com>,
catalin.marinas@....com, will@...nel.org
Cc: ardb@...nel.org, linux-arm-kernel@...ts.infradead.org,
linux-arch@...r.kernel.org, kernel-team@...roid.com,
linux-kernel@...r.kernel.org, kvmarm@...ts.cs.columbia.edu
Subject: Re: [PATCH 0/2] KVM: arm64: Stub exports in nvhe code
On Wed, 3 Feb 2021 14:19:29 +0000, Quentin Perret wrote:
> In the context of the currently ongoing work to remove the host kernel
> from the TCB under KVM/arm64, I have been trying to wrap the host kernel
> with a stage 2 page-table -- see [1].
>
> Using this infrastructure, I attempted to unmap the .hyp. sections from
> the host stage 2 as it really shouldn't need to access them. But by
> doing so, I realized quickly the module loader was getting very confused
> by the usage of EXPORT_SYMBOL() macros in library functions that have
> been pulled into the EL2 object, and that we end up linking modules
> against the EL2 copy of e.g. memset. And so, this series essentially
> tries to fix this.
>
> [...]
Applied to kvm-arm64/misc-5.12, thanks!
[1/2] asm-generic: export: Stub EXPORT_SYMBOL with __DISABLE_EXPORTS
commit: 54effa653246c35997f5e990e0134be5be09f9d1
[2/2] KVM: arm64: Stub EXPORT_SYMBOL for nVHE EL2 code
commit: bbc075e01ceac50e0a8353b520544f3089e94e44
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists