All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	julien.grall@arm.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] devicetree, xen: add xen, shared-memory binding
Date: Wed, 17 Oct 2018 10:35:27 -0500	[thread overview]
Message-ID: <20181017153527.GA9130@bogus> (raw)
In-Reply-To: <alpine.DEB.2.10.1810081600350.28877@sstabellini-ThinkPad-X260>

On Mon, Oct 08, 2018 at 04:03:54PM -0700, Stefano Stabellini wrote:
> 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>

checkpatch.pl complains that the author and S-o-b don't match.

> Cc: julien.grall@arm.com
> 
> 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..a927a94
> --- /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"

Any need for versioning?

> +
> +- reg:
> +	the base guest physical address and size of the shared memory region
> +
> +- id:

xen,id

> +	a string that identifies the shared memory region as specified in
> +	the VM config file

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-10-17 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 23:03 [PATCH] devicetree,xen: add xen,shared-memory binding Stefano Stabellini
2018-10-17 15:35 ` Rob Herring [this message]
2018-10-18 21:30   ` [PATCH] devicetree, xen: add xen, shared-memory binding Stefano Stabellini

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=20181017153527.GA9130@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=julien.grall@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=sstabellini@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.