From: Rob Herring <robh@kernel.org>
To: Oleksandr Tyshchenko <olekstysh@gmail.com>
Cc: Juergen Gross <jgross@suse.com>,
devicetree@vger.kernel.org,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>, Arnd Bergmann <arnd@arndb.de>,
"Michael S. Tsirkin" <mst@redhat.com>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
xen-devel@lists.xenproject.org, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4 5/8] dt-bindings: Add xen,grant-dma IOMMU description for xen-grant DMA ops
Date: Sun, 5 Jun 2022 17:45:33 -0500 [thread overview]
Message-ID: <20220605224533.GA3667788-robh@kernel.org> (raw)
In-Reply-To: <1654197833-25362-6-git-send-email-olekstysh@gmail.com>
On Thu, 02 Jun 2022 22:23:50 +0300, Oleksandr Tyshchenko wrote:
> From: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
>
> The main purpose of this binding is to communicate Xen specific
> information using generic IOMMU device tree bindings (which is
> a good fit here) rather than introducing a custom property.
>
> Introduce Xen specific IOMMU for the virtualized device (e.g. virtio)
> to be used by Xen grant DMA-mapping layer in the subsequent commit.
>
> The reference to Xen specific IOMMU node using "iommus" property
> indicates that Xen grant mappings need to be enabled for the device,
> and it specifies the ID of the domain where the corresponding backend
> resides. The domid (domain ID) is used as an argument to the Xen grant
> mapping APIs.
>
> This is needed for the option to restrict memory access using Xen grant
> mappings to work which primary goal is to enable using virtio devices
> in Xen guests.
>
> Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
> ---
> Changes RFC -> V1:
> - update commit subject/description and text in description
> - move to devicetree/bindings/arm/
>
> Changes V1 -> V2:
> - update text in description
> - change the maintainer of the binding
> - fix validation issue
> - reference xen,dev-domid.yaml schema from virtio/mmio.yaml
>
> Change V2 -> V3:
> - Stefano already gave his Reviewed-by, I dropped it due to the changes (significant)
> - use generic IOMMU device tree bindings instead of custom property
> "xen,dev-domid"
> - change commit subject and description, was
> "dt-bindings: Add xen,dev-domid property description for xen-grant DMA ops"
>
> Changes V3 -> V4:
> - add Stefano's R-b
> - remove underscore in iommu node name
> - remove consumer example virtio@3000
> - update text for two descriptions
> ---
> .../devicetree/bindings/iommu/xen,grant-dma.yaml | 39 ++++++++++++++++++++++
> 1 file changed, 39 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iommu/xen,grant-dma.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Oleksandr Tyshchenko <olekstysh@gmail.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Joerg Roedel <joro@8bytes.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Julien Grall <julien@xen.org>,
xen-devel@lists.xenproject.org, devicetree@vger.kernel.org,
Will Deacon <will@kernel.org>, Juergen Gross <jgross@suse.com>,
Arnd Bergmann <arnd@arndb.de>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org,
Christoph Hellwig <hch@infradead.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH V4 5/8] dt-bindings: Add xen,grant-dma IOMMU description for xen-grant DMA ops
Date: Sun, 5 Jun 2022 17:45:33 -0500 [thread overview]
Message-ID: <20220605224533.GA3667788-robh@kernel.org> (raw)
In-Reply-To: <1654197833-25362-6-git-send-email-olekstysh@gmail.com>
On Thu, 02 Jun 2022 22:23:50 +0300, Oleksandr Tyshchenko wrote:
> From: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
>
> The main purpose of this binding is to communicate Xen specific
> information using generic IOMMU device tree bindings (which is
> a good fit here) rather than introducing a custom property.
>
> Introduce Xen specific IOMMU for the virtualized device (e.g. virtio)
> to be used by Xen grant DMA-mapping layer in the subsequent commit.
>
> The reference to Xen specific IOMMU node using "iommus" property
> indicates that Xen grant mappings need to be enabled for the device,
> and it specifies the ID of the domain where the corresponding backend
> resides. The domid (domain ID) is used as an argument to the Xen grant
> mapping APIs.
>
> This is needed for the option to restrict memory access using Xen grant
> mappings to work which primary goal is to enable using virtio devices
> in Xen guests.
>
> Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
> ---
> Changes RFC -> V1:
> - update commit subject/description and text in description
> - move to devicetree/bindings/arm/
>
> Changes V1 -> V2:
> - update text in description
> - change the maintainer of the binding
> - fix validation issue
> - reference xen,dev-domid.yaml schema from virtio/mmio.yaml
>
> Change V2 -> V3:
> - Stefano already gave his Reviewed-by, I dropped it due to the changes (significant)
> - use generic IOMMU device tree bindings instead of custom property
> "xen,dev-domid"
> - change commit subject and description, was
> "dt-bindings: Add xen,dev-domid property description for xen-grant DMA ops"
>
> Changes V3 -> V4:
> - add Stefano's R-b
> - remove underscore in iommu node name
> - remove consumer example virtio@3000
> - update text for two descriptions
> ---
> .../devicetree/bindings/iommu/xen,grant-dma.yaml | 39 ++++++++++++++++++++++
> 1 file changed, 39 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iommu/xen,grant-dma.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Oleksandr Tyshchenko <olekstysh@gmail.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Joerg Roedel <joro@8bytes.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Julien Grall <julien@xen.org>,
xen-devel@lists.xenproject.org, devicetree@vger.kernel.org,
Will Deacon <will@kernel.org>, Juergen Gross <jgross@suse.com>,
Arnd Bergmann <arnd@arndb.de>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org,
Christoph Hellwig <hch@infradead.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH V4 5/8] dt-bindings: Add xen,grant-dma IOMMU description for xen-grant DMA ops
Date: Sun, 5 Jun 2022 17:45:33 -0500 [thread overview]
Message-ID: <20220605224533.GA3667788-robh@kernel.org> (raw)
In-Reply-To: <1654197833-25362-6-git-send-email-olekstysh@gmail.com>
On Thu, 02 Jun 2022 22:23:50 +0300, Oleksandr Tyshchenko wrote:
> From: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
>
> The main purpose of this binding is to communicate Xen specific
> information using generic IOMMU device tree bindings (which is
> a good fit here) rather than introducing a custom property.
>
> Introduce Xen specific IOMMU for the virtualized device (e.g. virtio)
> to be used by Xen grant DMA-mapping layer in the subsequent commit.
>
> The reference to Xen specific IOMMU node using "iommus" property
> indicates that Xen grant mappings need to be enabled for the device,
> and it specifies the ID of the domain where the corresponding backend
> resides. The domid (domain ID) is used as an argument to the Xen grant
> mapping APIs.
>
> This is needed for the option to restrict memory access using Xen grant
> mappings to work which primary goal is to enable using virtio devices
> in Xen guests.
>
> Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
> ---
> Changes RFC -> V1:
> - update commit subject/description and text in description
> - move to devicetree/bindings/arm/
>
> Changes V1 -> V2:
> - update text in description
> - change the maintainer of the binding
> - fix validation issue
> - reference xen,dev-domid.yaml schema from virtio/mmio.yaml
>
> Change V2 -> V3:
> - Stefano already gave his Reviewed-by, I dropped it due to the changes (significant)
> - use generic IOMMU device tree bindings instead of custom property
> "xen,dev-domid"
> - change commit subject and description, was
> "dt-bindings: Add xen,dev-domid property description for xen-grant DMA ops"
>
> Changes V3 -> V4:
> - add Stefano's R-b
> - remove underscore in iommu node name
> - remove consumer example virtio@3000
> - update text for two descriptions
> ---
> .../devicetree/bindings/iommu/xen,grant-dma.yaml | 39 ++++++++++++++++++++++
> 1 file changed, 39 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iommu/xen,grant-dma.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-05 22:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 19:23 [PATCH V4 0/8] virtio: Solution to restrict memory access under Xen using xen-grant DMA-mapping layer Oleksandr Tyshchenko
2022-06-02 19:23 ` Oleksandr Tyshchenko
2022-06-02 19:23 ` [PATCH V4 1/8] arm/xen: Introduce xen_setup_dma_ops() Oleksandr Tyshchenko
2022-06-02 19:23 ` Oleksandr Tyshchenko
2022-06-02 19:23 ` [PATCH V4 2/8] xen/grants: support allocating consecutive grants Oleksandr Tyshchenko
2022-06-02 19:23 ` Oleksandr Tyshchenko
2022-06-02 19:23 ` [PATCH V4 3/8] xen/grant-dma-ops: Add option to restrict memory access under Xen Oleksandr Tyshchenko
2022-06-02 19:23 ` Oleksandr Tyshchenko
2022-06-02 19:23 ` [PATCH V4 4/8] xen/virtio: Enable restricted memory access using Xen grant mappings Oleksandr Tyshchenko
2022-06-02 19:23 ` Oleksandr Tyshchenko
2022-06-02 19:23 ` [PATCH V4 5/8] dt-bindings: Add xen, grant-dma IOMMU description for xen-grant DMA ops Oleksandr Tyshchenko
2022-06-02 19:23 ` [PATCH V4 5/8] dt-bindings: Add xen,grant-dma " Oleksandr Tyshchenko
2022-06-02 19:23 ` Oleksandr Tyshchenko
2022-06-05 22:45 ` Rob Herring [this message]
2022-06-05 22:45 ` Rob Herring
2022-06-05 22:45 ` Rob Herring
2022-06-02 19:23 ` [PATCH V4 6/8] xen/grant-dma-iommu: Introduce stub IOMMU driver Oleksandr Tyshchenko
2022-06-02 19:23 ` Oleksandr Tyshchenko
2022-06-02 19:23 ` [PATCH V4 7/8] xen/grant-dma-ops: Retrieve the ID of backend's domain for DT devices Oleksandr Tyshchenko
2022-06-02 19:23 ` Oleksandr Tyshchenko
2022-06-02 19:23 ` [PATCH V4 8/8] arm/xen: Assign xen-grant DMA ops for xen-grant DMA devices Oleksandr Tyshchenko
2022-06-02 19:23 ` Oleksandr Tyshchenko
2022-06-08 5:36 ` [PATCH V4 0/8] virtio: Solution to restrict memory access under Xen using xen-grant DMA-mapping layer Juergen Gross via Virtualization
2022-06-08 5:36 ` Juergen Gross
2022-06-08 5:36 ` Juergen Gross
2022-06-15 6:23 ` Viresh Kumar
2022-06-15 6:23 ` Viresh Kumar
2022-06-15 6:23 ` Viresh Kumar
2022-06-15 12:41 ` Oleksandr
2022-06-15 12:41 ` Oleksandr
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=20220605224533.GA3667788-robh@kernel.org \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=olekstysh@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sstabellini@kernel.org \
--cc=will@kernel.org \
--cc=xen-devel@lists.xenproject.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.