* [PATCH v2] devicetree, xen: add xen, shared-memory binding
@ 2018-10-18 22:10 Stefano Stabellini
2018-10-22 10:27 ` Julien Grall
0 siblings, 1 reply; 3+ messages in thread
From: Stefano Stabellini @ 2018-10-18 22:10 UTC (permalink / raw)
To: devicetree
Cc: mark.rutland, Stefano Stabellini, sstabellini, xen-devel,
julien.grall, robh+dt
From: Stefano Stabellini <stefanos@xilinx.com>
Introduce a device tree binding for Xen reserved-memory regions. They
are used to share memory across VMs from the VM config files. (See
static_shm config option.)
Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>
---
Changes in v2:
- fix Author line
- add versioning
- xen,id instead of id
---
.../bindings/reserved-memory/xen,shared-memory.txt | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
diff --git a/Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt b/Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
new file mode 100644
index 0000000..9078fb7
--- /dev/null
+++ b/Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
@@ -0,0 +1,20 @@
+* 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", "xen,shared-memory"
+
+- reg:
+ the base guest physical address and size of the shared memory region
+
+- xen,id:
+ a string that identifies the shared memory region as specified in
+ the VM config file
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH v2] devicetree, xen: add xen, shared-memory binding
2018-10-18 22:10 [PATCH v2] devicetree, xen: add xen, shared-memory binding Stefano Stabellini
@ 2018-10-22 10:27 ` Julien Grall
2018-10-23 0:30 ` Rob Herring
0 siblings, 1 reply; 3+ messages in thread
From: Julien Grall @ 2018-10-22 10:27 UTC (permalink / raw)
To: Stefano Stabellini, devicetree
Cc: mark.rutland, Stefano Stabellini, robh+dt, xen-devel
Hi Stefano,
On 18/10/2018 23:10, Stefano Stabellini wrote:
> From: Stefano Stabellini <stefanos@xilinx.com>
>
> Introduce a device tree binding for Xen reserved-memory regions. They
> are used to share memory across VMs from the VM config files. (See
> static_shm config option.)
>
> Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>
> ---
> Changes in v2:
> - fix Author line
> - add versioning
> - xen,id instead of id
> ---
> .../bindings/reserved-memory/xen,shared-memory.txt | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
>
> diff --git a/Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt b/Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
> new file mode 100644
> index 0000000..9078fb7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
> @@ -0,0 +1,20 @@
> +* 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", "xen,shared-memory"
Do we need to specify the two compatibles?
> +
> +- reg:
> + the base guest physical address and size of the shared memory region
> +
> +- xen,id:
> + a string that identifies the shared memory region as specified in
> + the VM config file
>
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v2] devicetree, xen: add xen, shared-memory binding
2018-10-22 10:27 ` Julien Grall
@ 2018-10-23 0:30 ` Rob Herring
0 siblings, 0 replies; 3+ messages in thread
From: Rob Herring @ 2018-10-23 0:30 UTC (permalink / raw)
To: Julien Grall
Cc: mark.rutland, devicetree, Stefano Stabellini, Stefano Stabellini,
xen-devel
On Mon, Oct 22, 2018 at 11:27:23AM +0100, Julien Grall wrote:
> Hi Stefano,
>
> On 18/10/2018 23:10, Stefano Stabellini wrote:
> > From: Stefano Stabellini <stefanos@xilinx.com>
> >
> > Introduce a device tree binding for Xen reserved-memory regions. They
> > are used to share memory across VMs from the VM config files. (See
> > static_shm config option.)
> >
> > Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>
> > ---
> > Changes in v2:
> > - fix Author line
> > - add versioning
> > - xen,id instead of id
> > ---
> > .../bindings/reserved-memory/xen,shared-memory.txt | 20 ++++++++++++++++++++
> > 1 file changed, 20 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
> >
> > diff --git a/Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt b/Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
> > new file mode 100644
> > index 0000000..9078fb7
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
> > @@ -0,0 +1,20 @@
> > +* 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", "xen,shared-memory"
>
> Do we need to specify the two compatibles?
I'd just drop the fallback as version seems to be just in case.
Rob
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-10-23 0:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-10-18 22:10 [PATCH v2] devicetree, xen: add xen, shared-memory binding Stefano Stabellini
2018-10-22 10:27 ` Julien Grall
2018-10-23 0:30 ` Rob Herring
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).