[PATCH v5 01/13] docs: gunyah: Introduce Gunyah Hypervisor

[Bagas Sanjaya]

On 10/11/22 07:08, Elliot Berman wrote:
> +The diagram below shows how message queue works. A typical configuration involves
> +2 message queues. Message queue 1 allows VM_A to send messages to VM_B. Message
> +queue 2 allows VM_B to send messages to VM_A.
> +
> +1. VM_A sends a message of up to 1024 bytes in length. It raises a hypercall
> +   with the message to inform the hypervisor to add the message to
> +   message queue 1's queue.
> +
> +2. Gunyah raises the corresponding interrupt for VM_B when any of these happens:
> +   a. gh_msgq_send has PUSH flag. Queue is immediately flushed. This is the typical case.
> +   b. Explicility with gh_msgq_push command from VM_A.
> +   c. Message queue has reached a threshold depth.
> +
> +3. VM_B calls gh_msgq_recv and Gunyah copies message to requested buffer.
> +

Seems like you forget to apply my suggestion fixes at [1].

[1]: https://lore.kernel.org/all/YzUUaIx+azyzFDNX@debian.me/

Thanks.

-- 
An old man doll... just what I always wanted! - Clara