From: Oleksandr <olekstysh@gmail.com> To: Stefano Stabellini <sstabellini@kernel.org> Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>, Boris Ostrovsky <boris.ostrovsky@oracle.com>, Juergen Gross <jgross@suse.com>, Julien Grall <julien@xen.org>, "Michael S. Tsirkin" <mst@redhat.com>, Christoph Hellwig <hch@infradead.org> Subject: Re: [RFC PATCH 6/6] arm/xen: Assign xen-virtio DMA ops for virtio devices in Xen guests Date: Sun, 17 Apr 2022 22:20:04 +0300 [thread overview] Message-ID: <8df1dc60-614a-67fa-3a9d-e2db4a7e0132@gmail.com> (raw) In-Reply-To: <alpine.DEB.2.22.394.2204151305050.915916@ubuntu-linux-20-04-desktop> On 16.04.22 01:02, Stefano Stabellini wrote: Hello Stefano > On Thu, 14 Apr 2022, Oleksandr Tyshchenko wrote: >> From: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> >> >> Call xen_virtio_setup_dma_ops() only for Xen-aware virtio devices >> in Xen guests if restricted access to the guest memory is enabled. >> >> Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> >> --- >> include/xen/arm/xen-ops.h | 7 +++++++ >> 1 file changed, 7 insertions(+) >> >> diff --git a/include/xen/arm/xen-ops.h b/include/xen/arm/xen-ops.h >> index 621da05..28b2ad3 100644 >> --- a/include/xen/arm/xen-ops.h >> +++ b/include/xen/arm/xen-ops.h >> @@ -2,12 +2,19 @@ >> #ifndef _ASM_ARM_XEN_OPS_H >> #define _ASM_ARM_XEN_OPS_H >> >> +#include <linux/virtio_config.h> >> #include <xen/swiotlb-xen.h> >> +#include <xen/xen-ops.h> >> >> static inline void xen_setup_dma_ops(struct device *dev) >> { >> if (xen_swiotlb_detect()) >> dev->dma_ops = &xen_swiotlb_dma_ops; >> + >> +#ifdef CONFIG_XEN_VIRTIO >> + if (arch_has_restricted_virtio_memory_access() && xen_is_virtio_device(dev)) >> + xen_virtio_setup_dma_ops(dev); >> +#endif > This makes sense overall. thank you > Considering that the swiotlb-xen case and the > virtio case are mutually exclusive, I would write it like this: > > if (arch_has_restricted_virtio_memory_access() && xen_is_virtio_device(dev)) > xen_virtio_setup_dma_ops(dev); > else if (xen_swiotlb_detect()) > dev->dma_ops = &xen_swiotlb_dma_ops; Agree, will do > > There is no need for #ifdef (also see other comments). Agree, if !CONFIG_XEN_VIRTIO then xen_virtio_ are just stubs. #ifdef CONFIG_XEN_VIRTIO void xen_virtio_setup_dma_ops(struct device *dev); bool xen_is_virtio_device(struct device *dev); #else static inline void xen_virtio_setup_dma_ops(struct device *dev) { } static inline bool xen_is_virtio_device(struct device *dev) { return false; } #endif /* CONFIG_XEN_VIRTIO */ -- Regards, Oleksandr Tyshchenko
WARNING: multiple messages have this Message-ID (diff)
From: Oleksandr <olekstysh@gmail.com> To: Stefano Stabellini <sstabellini@kernel.org> Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>, Boris Ostrovsky <boris.ostrovsky@oracle.com>, Juergen Gross <jgross@suse.com>, Julien Grall <julien@xen.org>, "Michael S. Tsirkin" <mst@redhat.com>, Christoph Hellwig <hch@infradead.org> Subject: Re: [RFC PATCH 6/6] arm/xen: Assign xen-virtio DMA ops for virtio devices in Xen guests Date: Sun, 17 Apr 2022 22:20:04 +0300 [thread overview] Message-ID: <8df1dc60-614a-67fa-3a9d-e2db4a7e0132@gmail.com> (raw) In-Reply-To: <alpine.DEB.2.22.394.2204151305050.915916@ubuntu-linux-20-04-desktop> On 16.04.22 01:02, Stefano Stabellini wrote: Hello Stefano > On Thu, 14 Apr 2022, Oleksandr Tyshchenko wrote: >> From: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> >> >> Call xen_virtio_setup_dma_ops() only for Xen-aware virtio devices >> in Xen guests if restricted access to the guest memory is enabled. >> >> Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> >> --- >> include/xen/arm/xen-ops.h | 7 +++++++ >> 1 file changed, 7 insertions(+) >> >> diff --git a/include/xen/arm/xen-ops.h b/include/xen/arm/xen-ops.h >> index 621da05..28b2ad3 100644 >> --- a/include/xen/arm/xen-ops.h >> +++ b/include/xen/arm/xen-ops.h >> @@ -2,12 +2,19 @@ >> #ifndef _ASM_ARM_XEN_OPS_H >> #define _ASM_ARM_XEN_OPS_H >> >> +#include <linux/virtio_config.h> >> #include <xen/swiotlb-xen.h> >> +#include <xen/xen-ops.h> >> >> static inline void xen_setup_dma_ops(struct device *dev) >> { >> if (xen_swiotlb_detect()) >> dev->dma_ops = &xen_swiotlb_dma_ops; >> + >> +#ifdef CONFIG_XEN_VIRTIO >> + if (arch_has_restricted_virtio_memory_access() && xen_is_virtio_device(dev)) >> + xen_virtio_setup_dma_ops(dev); >> +#endif > This makes sense overall. thank you > Considering that the swiotlb-xen case and the > virtio case are mutually exclusive, I would write it like this: > > if (arch_has_restricted_virtio_memory_access() && xen_is_virtio_device(dev)) > xen_virtio_setup_dma_ops(dev); > else if (xen_swiotlb_detect()) > dev->dma_ops = &xen_swiotlb_dma_ops; Agree, will do > > There is no need for #ifdef (also see other comments). Agree, if !CONFIG_XEN_VIRTIO then xen_virtio_ are just stubs. #ifdef CONFIG_XEN_VIRTIO void xen_virtio_setup_dma_ops(struct device *dev); bool xen_is_virtio_device(struct device *dev); #else static inline void xen_virtio_setup_dma_ops(struct device *dev) { } static inline bool xen_is_virtio_device(struct device *dev) { return false; } #endif /* CONFIG_XEN_VIRTIO */ -- Regards, Oleksandr Tyshchenko _______________________________________________ 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-04-17 19:24 UTC|newest] Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-14 19:19 [RFC PATCH 0/6] virtio: Solution to restrict memory access under Xen using xen-virtio DMA ops layer Oleksandr Tyshchenko 2022-04-14 19:19 ` Oleksandr Tyshchenko 2022-04-14 19:19 ` [RFC PATCH 1/6] xen/grants: support allocating consecutive grants Oleksandr Tyshchenko 2022-04-14 19:19 ` Oleksandr Tyshchenko 2022-04-14 19:19 ` [RFC PATCH 2/6] virtio: add option to restrict memory access under Xen Oleksandr Tyshchenko 2022-04-14 19:19 ` Oleksandr Tyshchenko 2022-04-14 19:43 ` H. Peter Anvin 2022-04-15 15:20 ` Oleksandr 2022-04-15 15:20 ` Oleksandr 2022-04-15 22:01 ` Stefano Stabellini 2022-04-17 17:02 ` Oleksandr 2022-04-17 17:02 ` Oleksandr 2022-04-18 19:11 ` Stefano Stabellini 2022-04-18 19:11 ` Stefano Stabellini 2022-04-19 6:21 ` Juergen Gross 2022-04-19 6:21 ` Juergen Gross 2022-04-19 6:37 ` Oleksandr 2022-04-19 6:37 ` Oleksandr 2022-04-14 19:19 ` [RFC PATCH 3/6] dt-bindings: xen: Add xen,dev-domid property description for xen-virtio layer Oleksandr Tyshchenko 2022-04-14 19:19 ` [RFC PATCH 3/6] dt-bindings: xen: Add xen, dev-domid " Oleksandr Tyshchenko 2022-04-15 22:01 ` [RFC PATCH 3/6] dt-bindings: xen: Add xen,dev-domid " Stefano Stabellini 2022-04-15 22:01 ` Stefano Stabellini 2022-04-17 17:24 ` Oleksandr 2022-04-17 17:24 ` Oleksandr 2022-04-14 19:19 ` [RFC PATCH 4/6] virtio: Various updates to xen-virtio DMA ops layer Oleksandr Tyshchenko 2022-04-14 19:19 ` Oleksandr Tyshchenko 2022-04-15 22:02 ` Stefano Stabellini 2022-04-15 22:02 ` Stefano Stabellini 2022-04-17 18:21 ` Oleksandr 2022-04-17 18:21 ` Oleksandr 2022-04-18 19:11 ` Stefano Stabellini 2022-04-18 19:11 ` Stefano Stabellini 2022-04-19 6:58 ` Juergen Gross 2022-04-19 6:58 ` Juergen Gross 2022-04-19 7:07 ` Oleksandr 2022-04-19 7:07 ` Oleksandr 2022-04-16 6:05 ` Christoph Hellwig 2022-04-16 6:05 ` Christoph Hellwig 2022-04-17 18:39 ` Oleksandr 2022-04-17 18:39 ` Oleksandr 2022-04-14 19:19 ` [RFC PATCH 5/6] arm/xen: Introduce xen_setup_dma_ops() Oleksandr Tyshchenko 2022-04-14 19:19 ` Oleksandr Tyshchenko 2022-04-15 22:02 ` Stefano Stabellini 2022-04-15 22:02 ` Stefano Stabellini 2022-04-17 18:43 ` Oleksandr 2022-04-17 18:43 ` Oleksandr 2022-04-14 19:19 ` [RFC PATCH 6/6] arm/xen: Assign xen-virtio DMA ops for virtio devices in Xen guests Oleksandr Tyshchenko 2022-04-14 19:19 ` Oleksandr Tyshchenko 2022-04-15 22:02 ` Stefano Stabellini 2022-04-15 22:02 ` Stefano Stabellini 2022-04-16 6:07 ` Christoph Hellwig 2022-04-16 6:07 ` Christoph Hellwig 2022-04-17 21:05 ` Oleksandr 2022-04-17 21:05 ` Oleksandr 2022-04-18 19:11 ` Stefano Stabellini 2022-04-18 19:11 ` Stefano Stabellini 2022-04-19 12:17 ` Oleksandr 2022-04-19 12:17 ` Oleksandr 2022-04-19 14:48 ` Juergen Gross 2022-04-19 14:48 ` Juergen Gross 2022-04-19 17:11 ` Oleksandr 2022-04-19 17:11 ` Oleksandr 2022-04-20 0:23 ` Stefano Stabellini 2022-04-20 0:23 ` Stefano Stabellini 2022-04-20 9:00 ` Oleksandr 2022-04-20 9:00 ` Oleksandr 2022-04-20 22:49 ` Stefano Stabellini 2022-04-20 22:49 ` Stefano Stabellini 2022-04-17 19:20 ` Oleksandr [this message] 2022-04-17 19:20 ` Oleksandr 2022-04-15 7:41 ` [RFC PATCH 0/6] virtio: Solution to restrict memory access under Xen using xen-virtio DMA ops layer Christoph Hellwig 2022-04-15 7:41 ` Christoph Hellwig 2022-04-15 7:41 ` Christoph Hellwig 2022-04-15 10:04 ` Oleksandr 2022-04-15 10:04 ` Oleksandr 2022-04-15 8:44 ` Michael S. Tsirkin 2022-04-15 8:44 ` Michael S. Tsirkin 2022-04-15 8:44 ` Michael S. Tsirkin 2022-04-15 15:29 ` Oleksandr 2022-04-15 15:29 ` 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=8df1dc60-614a-67fa-3a9d-e2db4a7e0132@gmail.com \ --to=olekstysh@gmail.com \ --cc=boris.ostrovsky@oracle.com \ --cc=hch@infradead.org \ --cc=jgross@suse.com \ --cc=julien@xen.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mst@redhat.com \ --cc=oleksandr_tyshchenko@epam.com \ --cc=sstabellini@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: linkBe 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.