Add snapshot of device tree bindings from keystone common kernel, branch "android-mainline-keystone-qcom-release" at c4c12103f9c0 ("Snap for 9228065 from e32903b9a63bb558df8b803b076619c53c16baad to android-mainline-keystone-qcom-release"). Change-Id: I7682079615cbd9f29340a5c1f2a1d84ec441a1f1 Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
25 lines
850 B
Plaintext
25 lines
850 B
Plaintext
* Xen hypervisor reserved-memory binding
|
|
|
|
Expose one or more memory regions as reserved-memory to the guest
|
|
virtual machine. Typically, a region is configured at VM creation time
|
|
to be a shared memory area across multiple virtual machines for
|
|
communication among them.
|
|
|
|
For each of these pre-shared memory regions, a range is exposed under
|
|
the /reserved-memory node as a child node. Each range sub-node is named
|
|
xen-shmem@<address> and has the following properties:
|
|
|
|
- compatible:
|
|
compatible = "xen,shared-memory-v1"
|
|
|
|
- reg:
|
|
the base guest physical address and size of the shared memory region
|
|
|
|
- xen,offset: (borrower VMs only)
|
|
64 bit integer offset within the owner virtual machine's shared
|
|
memory region used for the mapping in the borrower VM.
|
|
|
|
- xen,id:
|
|
a string that identifies the shared memory region as specified in
|
|
the VM config file
|