From: Stefano Stabellini <sstabellini@kernel.org>
To: devicetree@vger.kernel.org
Cc: mark.rutland@arm.com, Stefano Stabellini <stefanos@xilinx.com>,
sstabellini@kernel.org, xen-devel@lists.xen.org,
julien.grall@arm.com, robh+dt@kernel.org
Subject: [PATCH v2] devicetree, xen: add xen, shared-memory binding
Date: Thu, 18 Oct 2018 15:10:30 -0700 [thread overview]
Message-ID: <1539900630-26566-1-git-send-email-sstabellini@kernel.org> (raw)
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
next reply other threads:[~2018-10-18 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 22:10 Stefano Stabellini [this message]
2018-10-22 10:27 ` [PATCH v2] devicetree, xen: add xen, shared-memory binding Julien Grall
2018-10-23 0:30 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1539900630-26566-1-git-send-email-sstabellini@kernel.org \
--to=sstabellini@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=julien.grall@arm.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=stefanos@xilinx.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).