Re: [PATCH v1 01/13] xen/arm: introduce static shared memory
On Fri, 11 Mar 2022, Penny Zheng wrote:
> From: Penny Zheng
>
> This patch serie introduces a new feature: setting up static
> shared memory on a dom0less system, through device tree configuration.
>
> This commit parses shared memory node at boot-time, and reserve it in
> bootinfo.reserved_mem to avoid other use.
>
> Signed-off-by: Penny Zheng
> ---
> docs/misc/arm/device-tree/booting.txt | 118 ++
> xen/arch/arm/bootfdt.c| 52
> 2 files changed, 170 insertions(+)
>
> diff --git a/docs/misc/arm/device-tree/booting.txt
> b/docs/misc/arm/device-tree/booting.txt
> index a94125394e..f702ade817 100644
> --- a/docs/misc/arm/device-tree/booting.txt
> +++ b/docs/misc/arm/device-tree/booting.txt
> @@ -355,3 +355,121 @@ device-tree:
>
> This will reserve a 512MB region starting at the host physical address
> 0x3000 to be exclusively used by DomU1.
> +
> +Static Shared Memory
> +=
We ran out of = :-)
> +The static shared memory device tree nodes allow users to statically set up
> +shared memory on dom0less system, enabling domains to do shm-based
> +communication.
> +
> +- compatible
> +
> +"xen,domain-shared-memory-v1"
> +
> +- xen,shm-id
> +
> +An u8 value represents the unique identifier of the shared memory region.
> +The maximum identifier shall be "xen,shm-id = <0xff>".
> +
> +- xen,shared-mem
> +
> +An array takes a physical address, which is the base address of the
> +shared memory region in host physical address space, a size, and a guest
> +physical address, as the target address of the mapping.
This is good. We also need to say how to know how many cells each of the
three elements take: how many cells is the host physical address, how
many cells is the size, how many cells is the guest physical address.
This node is a subnode of a xen,domain compatible node (or chosen) which
comes with an #address-cells and a #size-cells. This is similarly to
multiboot,kernel nodes, so we could do the same. Here we could say that
the number of cells for the host address (and size) is the same as the
guest pseudo-physical address and they are inherited from the parent
node.
> +- role (Optional)
> +
> +A string property specifying the ownership of a shared memory region,
> +the value must be one of the following: "owner", or "borrower"
> +A shared memory region could be explicitly backed by one domain, which is
> +called "owner domain", and all the other domains who are also sharing
> +this region are called "borrower domain".
> +If not specified, the default value is "borrower" and owner is
> +"dom_shared", a system domain.
> +
> +As an example:
> +
> +chosen {
> +#address-cells = <0x1>;
> +#size-cells = <0x1>;
> +xen,xen-bootargs = "console=dtuart dtuart=serial0 bootscrub=0";
> +
> +..
> +
> +/* this is for Dom0 */
> +dom0-shared-mem@1000 {
> +compatible = "xen,domain-shared-memory-v1";
> +role = "owner";
> +xen,shm-id = <0x0>;
> +xen,shared-mem = <0x1000 0x1000 0x1000>;
> +}
> +
> +domU1 {
> +compatible = "xen,domain";
> +#address-cells = <0x1>;
> +#size-cells = <0x1>;
> +memory = <0 131072>;
> +cpus = <2>;
> +vpl011;
> +
> +/*
> + * shared memory region identified as 0x0(xen,shm-id = <0x0>)
> + * is shared between Dom0 and DomU1.
> + */
> +domU1-shared-mem@1000 {
> +compatible = "xen,domain-shared-memory-v1";
> +role = "borrower";
> +xen,shm-id = <0x0>;
> +xen,shared-mem = <0x1000 0x1000 0x5000>;
> +}
> +
> +/*
> + * shared memory region identified as 0x1(xen,shm-id = <0x1>)
> + * is shared between DomU1 and DomU2.
> + */
> +domU1-shared-mem@5000 {
> +compatible = "xen,domain-shared-memory-v1";
> +xen,shm-id = <0x1>;
> +xen,shared-mem = <0x5000 0x2000 0x6000>;
> +}
> +
> +..
> +
> +};
> +
> +domU2 {
> +compatible = "xen,domain";
> +#address-cells = <0x1>;
> +#size-cells = <0x1>;
> +memory = <0 65536>;
> +cpus = <1>;
> +
> +/*
> + * shared memory region identified as 0x1(xen,shm-id = <0x1>)
> + * is shared between domU1 and domU2.
> + */
> +domU2-shared-mem@5000 {
> +compatible = "xen,domain-shared-memory-v1";
> +xen,shm-id = <0x1>;
> +xen,shared-mem = <0x5000 0x2000 0x7000>;
> +}
> +
> +..
> +};
> +};
> +
> +This is an example with two static shared memory regions.
> +
> +For the static shared memory region identified as 0x0, host physical
> +address starting at 0x1000 of 256MB will be reserved to be shared between
> +Dom0 and DomU1.It will get mapped at 0x1000 in
[PATCH v1 01/13] xen/arm: introduce static shared memory
From: Penny Zheng
This patch serie introduces a new feature: setting up static
shared memory on a dom0less system, through device tree configuration.
This commit parses shared memory node at boot-time, and reserve it in
bootinfo.reserved_mem to avoid other use.
Signed-off-by: Penny Zheng
---
docs/misc/arm/device-tree/booting.txt | 118 ++
xen/arch/arm/bootfdt.c| 52
2 files changed, 170 insertions(+)
diff --git a/docs/misc/arm/device-tree/booting.txt
b/docs/misc/arm/device-tree/booting.txt
index a94125394e..f702ade817 100644
--- a/docs/misc/arm/device-tree/booting.txt
+++ b/docs/misc/arm/device-tree/booting.txt
@@ -355,3 +355,121 @@ device-tree:
This will reserve a 512MB region starting at the host physical address
0x3000 to be exclusively used by DomU1.
+
+Static Shared Memory
+=
+
+The static shared memory device tree nodes allow users to statically set up
+shared memory on dom0less system, enabling domains to do shm-based
+communication.
+
+- compatible
+
+"xen,domain-shared-memory-v1"
+
+- xen,shm-id
+
+An u8 value represents the unique identifier of the shared memory region.
+The maximum identifier shall be "xen,shm-id = <0xff>".
+
+- xen,shared-mem
+
+An array takes a physical address, which is the base address of the
+shared memory region in host physical address space, a size, and a guest
+physical address, as the target address of the mapping.
+
+- role (Optional)
+
+A string property specifying the ownership of a shared memory region,
+the value must be one of the following: "owner", or "borrower"
+A shared memory region could be explicitly backed by one domain, which is
+called "owner domain", and all the other domains who are also sharing
+this region are called "borrower domain".
+If not specified, the default value is "borrower" and owner is
+"dom_shared", a system domain.
+
+As an example:
+
+chosen {
+#address-cells = <0x1>;
+#size-cells = <0x1>;
+xen,xen-bootargs = "console=dtuart dtuart=serial0 bootscrub=0";
+
+..
+
+/* this is for Dom0 */
+dom0-shared-mem@1000 {
+compatible = "xen,domain-shared-memory-v1";
+role = "owner";
+xen,shm-id = <0x0>;
+xen,shared-mem = <0x1000 0x1000 0x1000>;
+}
+
+domU1 {
+compatible = "xen,domain";
+#address-cells = <0x1>;
+#size-cells = <0x1>;
+memory = <0 131072>;
+cpus = <2>;
+vpl011;
+
+/*
+ * shared memory region identified as 0x0(xen,shm-id = <0x0>)
+ * is shared between Dom0 and DomU1.
+ */
+domU1-shared-mem@1000 {
+compatible = "xen,domain-shared-memory-v1";
+role = "borrower";
+xen,shm-id = <0x0>;
+xen,shared-mem = <0x1000 0x1000 0x5000>;
+}
+
+/*
+ * shared memory region identified as 0x1(xen,shm-id = <0x1>)
+ * is shared between DomU1 and DomU2.
+ */
+domU1-shared-mem@5000 {
+compatible = "xen,domain-shared-memory-v1";
+xen,shm-id = <0x1>;
+xen,shared-mem = <0x5000 0x2000 0x6000>;
+}
+
+..
+
+};
+
+domU2 {
+compatible = "xen,domain";
+#address-cells = <0x1>;
+#size-cells = <0x1>;
+memory = <0 65536>;
+cpus = <1>;
+
+/*
+ * shared memory region identified as 0x1(xen,shm-id = <0x1>)
+ * is shared between domU1 and domU2.
+ */
+domU2-shared-mem@5000 {
+compatible = "xen,domain-shared-memory-v1";
+xen,shm-id = <0x1>;
+xen,shared-mem = <0x5000 0x2000 0x7000>;
+}
+
+..
+};
+};
+
+This is an example with two static shared memory regions.
+
+For the static shared memory region identified as 0x0, host physical
+address starting at 0x1000 of 256MB will be reserved to be shared between
+Dom0 and DomU1.It will get mapped at 0x1000 in Dom0 guest physical address
+space, and at 0x5000 in DomU1 guest physical address space. Dom0 is
+explicitly defined as the owner domain, and DomU1 is the borrower domain.
+
+For the static shared memory region identified as 0x1, host physical
+address starting at 0x5000 of 512MB will be reserved to be shared between
+DomU1 and DomU2. It will get mapped at 0x6000 in DomU1 guest physical
+address space, and at 0x7000 in DomU2 guest physical address space. DomU1
+and DomU2 are both the borrower domain, the owner domain is the default owner
+domain dom_shared.
diff --git a/xen/arch/arm/bootfdt.c b/xen/arch/arm/bootfdt.c
index afaa0e249b..7de0f8cea9 100644
--- a/xen/arch/arm/bootfdt.c
+++ b/xen/arch/arm/bootfdt.c
@@ -363,6 +363,56 @@ static int __init process_domain_node(const void *fdt, int
node,
size_cells, &bootinfo.reserved_mem, t
