Re: [PATCH v2 00/11] Drivers for gunyah hypervisor

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 8/4/2022 1:26 AM, Bagas Sanjaya wrote:
On Mon, Aug 01, 2022 at 02:12:29PM -0700, Elliot Berman wrote:
Gunyah is a Type-1 hypervisor independent of any
high-level OS kernel, and runs in a higher CPU privilege level. It does
not depend on any lower-privileged OS kernel/code for its core
functionality. This increases its security and can support a much smaller
trusted computing base than a Type-2 hypervisor.

Gunyah is an open source hypervisor. The source repo is available at
https://github.com/quic/gunyah-hypervisor.

The diagram below shows the architecture.

::

         Primary VM           Secondary VMs
      +-----+ +-----+  | +-----+ +-----+ +-----+
      |     | |     |  | |     | |     | |     |
  EL0 | APP | | APP |  | | APP | | APP | | APP |
      |     | |     |  | |     | |     | |     |
      +-----+ +-----+  | +-----+ +-----+ +-----+
  ---------------------|-------------------------
      +--------------+ | +----------------------+
      |              | | |                      |
  EL1 | Linux Kernel | | |Linux kernel/Other OS |   ...
      |              | | |                      |
      +--------------+ | +----------------------+
  --------hvc/smc------|------hvc/smc------------
      +----------------------------------------+
      |                                        |
  EL2 |            Gunyah Hypervisor           |
      |                                        |
      +----------------------------------------+

Gunyah provides these following features.

- Threads and Scheduling: The scheduler schedules virtual CPUs (VCPUs) on
physical CPUs and enables time-sharing of the CPUs.
- Memory Management: Gunyah tracks memory ownership and use of all memory
under its control. Memory partitioning between VMs is a fundamental
security feature.
- Interrupt Virtualization: All 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.
- Device Virtualization: Para-virtualization of devices is supported using
inter-VM communication. Low level system features and devices such as
interrupt controllers are supported with emulation where required.


Hi,

I can't apply this series on top of mainline or linux-next. On what tree
(and what commit) this series is based on? I'd like to do htmldocs test.


The series should apply cleanly on commit 4a57a8400075 ("vf/remap: return the amount of bytes actually deduplicated") from Linus's tree.

Thanks.




[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux