On Thu, Aug 11, 2022 at 02:40:57PM -0700, Elliot Berman wrote: > +Gunyah provides these following features. > + > +- Scheduling: > + A scheduler for virtual CPUs (vCPUs) on physical CPUs and enables time-sharing > + of the CPUs. Gunyah supports two models of scheduling: > + 1. "Behind the back" scheduling in which Gunyah hypervisor schedules vCPUS on its own > + 2. "Proxy" scheduling in which a delegated VM can donate part of one of its vCPU slice > + to another VM's vCPU via a hypercall. > +- Memory Management: > + APIs handling memory, abstracted as objects, limiting direct use of physical > + addresses. Memory ownership and usage tracking of all memory under its control. > + Memory partitioning between VMs is a fundamental security feature. > +- Interrupt Virtualization: > + Uses CPU hardware interrupt virtualization capabilities. Interrupts are handled > + in the hypervisor and routed to the assigned VM. > +- Inter-VM Communication: > + There are several different mechanisms provided for communicating between VMs. > +- Virtual platform: > + Architectural devices such as interrupt controllers and CPU timers are directly provided > + by the hypervisor as well as core virtual platform devices and system APIs such as ARM PSCI. > +- Device Virtualization: > + Para-virtualization of devices is supported using inter-VM communication. htmldocs build produces a new warning: Documentation/virt/gunyah/index.rst:25: WARNING: Unexpected indentation. I have applied the fixup for lists above: ---- >8 ---- diff --git a/Documentation/virt/gunyah/index.rst b/Documentation/virt/gunyah/index.rst index 780ff958a83b8c..c55e02f17ca318 100644 --- a/Documentation/virt/gunyah/index.rst +++ b/Documentation/virt/gunyah/index.rst @@ -20,24 +20,36 @@ https://github.com/quic/gunyah-hypervisor. Gunyah provides these following features. - Scheduling: + A scheduler for virtual CPUs (vCPUs) on physical CPUs and enables time-sharing of the CPUs. Gunyah supports two models of scheduling: + 1. "Behind the back" scheduling in which Gunyah hypervisor schedules vCPUS on its own 2. "Proxy" scheduling in which a delegated VM can donate part of one of its vCPU slice to another VM's vCPU via a hypercall. + - Memory Management: + APIs handling memory, abstracted as objects, limiting direct use of physical addresses. Memory ownership and usage tracking of all memory under its control. Memory partitioning between VMs is a fundamental security feature. + - Interrupt Virtualization: + Uses CPU hardware interrupt virtualization capabilities. Interrupts are handled in the hypervisor and routed to the assigned VM. + - Inter-VM Communication: + There are several different mechanisms provided for communicating between VMs. + - Virtual platform: + Architectural devices such as interrupt controllers and CPU timers are directly provided by the hypervisor as well as core virtual platform devices and system APIs such as ARM PSCI. + - Device Virtualization: + Para-virtualization of devices is supported using inter-VM communication. Architectures supported Thanks. -- An old man doll... just what I always wanted! - Clara
Attachment:
signature.asc
Description: PGP signature
