Re: [PATCH v3 02/12] docs: gunyah: Introduce Gunyah Hypervisor

From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Elliot Berman <quic_eberman@quicinc.com>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Murali Nalajala <quic_mnalajal@quicinc.com>,
	Trilok Soni <quic_tsoni@quicinc.com>,
	Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>,
	Carl van Schaik <quic_cvanscha@quicinc.com>,
	Andy Gross <agross@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	Mark Rutland <mark.rutland@arm.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 02/12] docs: gunyah: Introduce Gunyah Hypervisor
Date: Fri, 12 Aug 2022 15:25:17 +0700	[thread overview]
Message-ID: <YvYObTVhZsr0B2vS@debian.me> (raw)
In-Reply-To: <20220811214107.1074343-3-quic_eberman@quicinc.com>

[-- Attachment #1: Type: text/plain, Size: 3292 bytes --]

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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
