[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <df5bf1943851715130517c43fde8e5a9@kernel.org>
Date: Thu, 07 May 2020 16:15:55 +0100
From: Marc Zyngier <maz@...nel.org>
To: David Brazdil <dbrazdil@...gle.com>
Cc: Suzuki K Poulose <suzuki.poulose@....com>,
Catalin Marinas <catalin.marinas@....com>,
linux-kernel@...r.kernel.org, James Morse <james.morse@....com>,
linux-arm-kernel@...ts.infradead.org,
Will Deacon <will@...nel.org>, kvmarm@...ts.cs.columbia.edu,
Julien Thierry <julien.thierry.kdev@...il.com>
Subject: Re: [PATCH 05/15] arm64: kvm: Build hyp-entry.S separately for
VHE/nVHE
On 2020-05-07 16:07, Marc Zyngier wrote:
> On Thu, 30 Apr 2020 15:48:21 +0100,
> David Brazdil <dbrazdil@...gle.com> wrote:
[...]
>> hyp-entry.S contains implementation of KVM hyp vectors. This code is
>> mostly
>> shared between VHE/nVHE, therefore compile it under both VHE and nVHE
>> build
>> rules, with small differences hidden behind '#ifdef __HYPERVISOR__'.
>> These are:
>> * only nVHE should handle host HVCs, VHE will now panic,
>
> That's not true. VHE does handle HVCs from the guest. If you make VHE
> panic on guest exit, I'll come after you! ;-)
Duh, I can't read. "host HVCs". You can relax. ;-)
M.
--
Jazz is not dead. It just smells funny...
Powered by blists - more mailing lists