[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201110101542.GA17572@infradead.org>
Date: Tue, 10 Nov 2020 10:15:42 +0000
From: Christoph Hellwig <hch@...radead.org>
To: David Brazdil <dbrazdil@...gle.com>
Cc: kvmarm@...ts.cs.columbia.edu, Mark Rutland <mark.rutland@....com>,
kernel-team@...roid.com,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Andrew Walbran <qwandor@...gle.com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Marc Zyngier <maz@...nel.org>,
Quentin Perret <qperret@...gle.com>,
linux-kernel@...r.kernel.org, James Morse <james.morse@....com>,
linux-arm-kernel@...ts.infradead.org,
Catalin Marinas <catalin.marinas@....com>,
Tejun Heo <tj@...nel.org>, Dennis Zhou <dennis@...nel.org>,
Christoph Lameter <cl@...ux.com>,
Will Deacon <will@...nel.org>,
Julien Thierry <julien.thierry.kdev@...il.com>,
Andrew Scull <ascull@...gle.com>
Subject: Re: [PATCH v1 00/24] Opt-in always-on nVHE hypervisor
On Mon, Nov 09, 2020 at 11:32:09AM +0000, David Brazdil wrote:
> As we progress towards being able to keep guest state private to the
> host running nVHE hypervisor, this series allows the hypervisor to
> install itself on newly booted CPUs before the host is allowed to run
> on them.
Why? I thought we were trying to kill nVHE off now that newer CPUs
provide the saner virtualization extensions?
Powered by blists - more mailing lists