Re: [PATCH v1 00/24] Opt-in always-on nVHE hypervisor

From: Christoph Hellwig
Date: Tue Nov 10 2020 - 05:15:51 EST

Next message: Howard Chung: "[PATCH v8 1/6] Bluetooth: Replace BT_DBG with bt_dev_dbg in HCI request"
Previous message: Xiaolei Wang: "[PATCH v2] Bluetooth: hci_ll: add a small delay for wl1271 enable bt_en"
In reply to: Marc Zyngier: "Re: [PATCH v1 07/24] kvm: arm64: Create nVHE copy of cpu_logical_map"
Next in thread: Marc Zyngier: "Re: [PATCH v1 00/24] Opt-in always-on nVHE hypervisor"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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?

Next message: Howard Chung: "[PATCH v8 1/6] Bluetooth: Replace BT_DBG with bt_dev_dbg in HCI request"
Previous message: Xiaolei Wang: "[PATCH v2] Bluetooth: hci_ll: add a small delay for wl1271 enable bt_en"
In reply to: Marc Zyngier: "Re: [PATCH v1 07/24] kvm: arm64: Create nVHE copy of cpu_logical_map"
Next in thread: Marc Zyngier: "Re: [PATCH v1 00/24] Opt-in always-on nVHE hypervisor"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]