Re: [PATCH v3 00/23] Opt-in always-on nVHE hypervisor

2020-11-26 Thread Matthew Wilcox
On Thu, Nov 26, 2020 at 04:19:55PM +, Marc Zyngier wrote: > On 2020-11-26 15:57, Matthew Wilcox wrote: > > On Thu, Nov 26, 2020 at 03:53:58PM +, David Brazdil wrote: > > > The hypervisor starts trapping host SMCs and intercepting host's PSCI > > > CPU_ON/SUSPEND calls. It replaces the host'

Re: [PATCH v3 00/23] Opt-in always-on nVHE hypervisor

2020-11-26 Thread Marc Zyngier
On 2020-11-26 15:57, Matthew Wilcox wrote: On Thu, Nov 26, 2020 at 03:53:58PM +, David Brazdil wrote: The hypervisor starts trapping host SMCs and intercepting host's PSCI CPU_ON/SUSPEND calls. It replaces the host's entry point with its own, initializes the EL2 state of the new CPU and inst

Re: [PATCH v3 00/23] Opt-in always-on nVHE hypervisor

2020-11-26 Thread Matthew Wilcox
On Thu, Nov 26, 2020 at 03:53:58PM +, David Brazdil wrote: > The hypervisor starts trapping host SMCs and intercepting host's PSCI > CPU_ON/SUSPEND calls. It replaces the host's entry point with its own, > initializes the EL2 state of the new CPU and installs the nVHE hyp vector > before ERETin

[PATCH v3 00/23] Opt-in always-on nVHE hypervisor

2020-11-26 Thread David Brazdil
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. All functionality described below is opt-in, guarded by an early param 'kvm-arm.pro