From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: jgross@suse.com, Peng Fan <peng.fan@nxp.com>,
konrad.wilk@oracle.com, jasowang@redhat.com, x86@kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Christoph Hellwig <hch@infradead.org>,
iommu@lists.linux-foundation.org, linux-imx@nxp.com,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
Date: Sat, 11 Jul 2020 14:44:34 -0400 [thread overview]
Message-ID: <20200711144334-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2007101019340.4124@sstabellini-ThinkPad-T480s>
On Fri, Jul 10, 2020 at 10:23:22AM -0700, Stefano Stabellini wrote:
> Sorry for the late reply -- a couple of conferences kept me busy.
>
>
> On Wed, 1 Jul 2020, Michael S. Tsirkin wrote:
> > On Wed, Jul 01, 2020 at 10:34:53AM -0700, Stefano Stabellini wrote:
> > > Would you be in favor of a more flexible check along the lines of the
> > > one proposed in the patch that started this thread:
> > >
> > > if (xen_vring_use_dma())
> > > return true;
> > >
> > >
> > > xen_vring_use_dma would be implemented so that it returns true when
> > > xen_swiotlb is required and false otherwise.
> >
> > Just to stress - with a patch like this virtio can *still* use DMA API
> > if PLATFORM_ACCESS is set. So if DMA API is broken on some platforms
> > as you seem to be saying, you guys should fix it before doing something
> > like this..
>
> Yes, DMA API is broken with some interfaces (specifically: rpmesg and
> trusty), but for them PLATFORM_ACCESS is never set. That is why the
> errors weren't reported before. Xen special case aside, there is no
> problem under normal circumstances.
So why not fix DMA API? Then this patch is not needed.
>
> If you are OK with this patch (after a little bit of clean-up), Peng,
> are you OK with sending an update or do you want me to?
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: jgross@suse.com, Peng Fan <peng.fan@nxp.com>,
konrad.wilk@oracle.com, x86@kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Christoph Hellwig <hch@infradead.org>,
iommu@lists.linux-foundation.org, linux-imx@nxp.com,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
Date: Sat, 11 Jul 2020 14:44:34 -0400 [thread overview]
Message-ID: <20200711144334-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2007101019340.4124@sstabellini-ThinkPad-T480s>
On Fri, Jul 10, 2020 at 10:23:22AM -0700, Stefano Stabellini wrote:
> Sorry for the late reply -- a couple of conferences kept me busy.
>
>
> On Wed, 1 Jul 2020, Michael S. Tsirkin wrote:
> > On Wed, Jul 01, 2020 at 10:34:53AM -0700, Stefano Stabellini wrote:
> > > Would you be in favor of a more flexible check along the lines of the
> > > one proposed in the patch that started this thread:
> > >
> > > if (xen_vring_use_dma())
> > > return true;
> > >
> > >
> > > xen_vring_use_dma would be implemented so that it returns true when
> > > xen_swiotlb is required and false otherwise.
> >
> > Just to stress - with a patch like this virtio can *still* use DMA API
> > if PLATFORM_ACCESS is set. So if DMA API is broken on some platforms
> > as you seem to be saying, you guys should fix it before doing something
> > like this..
>
> Yes, DMA API is broken with some interfaces (specifically: rpmesg and
> trusty), but for them PLATFORM_ACCESS is never set. That is why the
> errors weren't reported before. Xen special case aside, there is no
> problem under normal circumstances.
So why not fix DMA API? Then this patch is not needed.
>
> If you are OK with this patch (after a little bit of clean-up), Peng,
> are you OK with sending an update or do you want me to?
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: jgross@suse.com, Peng Fan <peng.fan@nxp.com>,
konrad.wilk@oracle.com, jasowang@redhat.com, x86@kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Christoph Hellwig <hch@infradead.org>,
iommu@lists.linux-foundation.org, linux-imx@nxp.com,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
Date: Sat, 11 Jul 2020 14:44:34 -0400 [thread overview]
Message-ID: <20200711144334-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2007101019340.4124@sstabellini-ThinkPad-T480s>
On Fri, Jul 10, 2020 at 10:23:22AM -0700, Stefano Stabellini wrote:
> Sorry for the late reply -- a couple of conferences kept me busy.
>
>
> On Wed, 1 Jul 2020, Michael S. Tsirkin wrote:
> > On Wed, Jul 01, 2020 at 10:34:53AM -0700, Stefano Stabellini wrote:
> > > Would you be in favor of a more flexible check along the lines of the
> > > one proposed in the patch that started this thread:
> > >
> > > if (xen_vring_use_dma())
> > > return true;
> > >
> > >
> > > xen_vring_use_dma would be implemented so that it returns true when
> > > xen_swiotlb is required and false otherwise.
> >
> > Just to stress - with a patch like this virtio can *still* use DMA API
> > if PLATFORM_ACCESS is set. So if DMA API is broken on some platforms
> > as you seem to be saying, you guys should fix it before doing something
> > like this..
>
> Yes, DMA API is broken with some interfaces (specifically: rpmesg and
> trusty), but for them PLATFORM_ACCESS is never set. That is why the
> errors weren't reported before. Xen special case aside, there is no
> problem under normal circumstances.
So why not fix DMA API? Then this patch is not needed.
>
> If you are OK with this patch (after a little bit of clean-up), Peng,
> are you OK with sending an update or do you want me to?
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: jgross@suse.com, Peng Fan <peng.fan@nxp.com>,
konrad.wilk@oracle.com, jasowang@redhat.com, x86@kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Christoph Hellwig <hch@infradead.org>,
iommu@lists.linux-foundation.org, linux-imx@nxp.com,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
Date: Sat, 11 Jul 2020 14:44:34 -0400 [thread overview]
Message-ID: <20200711144334-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2007101019340.4124@sstabellini-ThinkPad-T480s>
On Fri, Jul 10, 2020 at 10:23:22AM -0700, Stefano Stabellini wrote:
> Sorry for the late reply -- a couple of conferences kept me busy.
>
>
> On Wed, 1 Jul 2020, Michael S. Tsirkin wrote:
> > On Wed, Jul 01, 2020 at 10:34:53AM -0700, Stefano Stabellini wrote:
> > > Would you be in favor of a more flexible check along the lines of the
> > > one proposed in the patch that started this thread:
> > >
> > > if (xen_vring_use_dma())
> > > return true;
> > >
> > >
> > > xen_vring_use_dma would be implemented so that it returns true when
> > > xen_swiotlb is required and false otherwise.
> >
> > Just to stress - with a patch like this virtio can *still* use DMA API
> > if PLATFORM_ACCESS is set. So if DMA API is broken on some platforms
> > as you seem to be saying, you guys should fix it before doing something
> > like this..
>
> Yes, DMA API is broken with some interfaces (specifically: rpmesg and
> trusty), but for them PLATFORM_ACCESS is never set. That is why the
> errors weren't reported before. Xen special case aside, there is no
> problem under normal circumstances.
So why not fix DMA API? Then this patch is not needed.
>
> If you are OK with this patch (after a little bit of clean-up), Peng,
> are you OK with sending an update or do you want me to?
_______________________________________________
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:[~2020-07-11 18:44 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 9:17 [PATCH] xen: introduce xen_vring_use_dma Peng Fan
2020-06-24 9:17 ` Peng Fan
2020-06-24 9:17 ` Peng Fan
2020-06-24 9:17 ` Peng Fan
2020-06-24 9:17 ` Peng Fan
2020-06-24 9:06 ` Michael S. Tsirkin
2020-06-24 9:06 ` Michael S. Tsirkin
2020-06-24 9:06 ` Michael S. Tsirkin
2020-06-24 9:06 ` Michael S. Tsirkin
2020-06-24 17:59 ` Stefano Stabellini
2020-06-24 17:59 ` Stefano Stabellini
2020-06-24 17:59 ` Stefano Stabellini
2020-06-24 17:59 ` Stefano Stabellini
2020-06-24 20:47 ` Michael S. Tsirkin
2020-06-24 20:47 ` Michael S. Tsirkin
2020-06-24 20:47 ` Michael S. Tsirkin
2020-06-24 20:47 ` Michael S. Tsirkin
2020-06-24 20:47 ` Michael S. Tsirkin
2020-06-24 21:53 ` Stefano Stabellini
2020-06-24 21:53 ` Stefano Stabellini
2020-06-24 21:53 ` Stefano Stabellini
2020-06-24 21:53 ` Stefano Stabellini
2020-06-24 22:16 ` Michael S. Tsirkin
2020-06-24 22:16 ` Michael S. Tsirkin
2020-06-24 22:16 ` Michael S. Tsirkin
2020-06-24 22:16 ` Michael S. Tsirkin
2020-06-24 22:16 ` Michael S. Tsirkin
2020-06-25 17:31 ` Stefano Stabellini
2020-06-25 17:31 ` Stefano Stabellini
2020-06-25 17:31 ` Stefano Stabellini
2020-06-25 17:31 ` Stefano Stabellini
2020-06-26 15:32 ` Michael S. Tsirkin
2020-06-26 15:32 ` Michael S. Tsirkin
2020-06-26 15:32 ` Michael S. Tsirkin
2020-06-26 15:32 ` Michael S. Tsirkin
2020-06-26 15:32 ` Michael S. Tsirkin
2020-06-29 3:05 ` Peng Fan
2020-06-29 3:05 ` Peng Fan
2020-06-29 3:05 ` Peng Fan
2020-06-29 3:05 ` Peng Fan
2020-06-29 3:05 ` Peng Fan
2020-06-29 6:21 ` Michael S. Tsirkin
2020-06-29 6:21 ` Michael S. Tsirkin
2020-06-29 6:21 ` Michael S. Tsirkin
2020-06-29 6:21 ` Michael S. Tsirkin
2020-06-29 6:21 ` Michael S. Tsirkin
2020-06-29 6:25 ` Peng Fan
2020-06-29 6:25 ` Peng Fan
2020-06-29 6:25 ` Peng Fan
2020-06-29 6:25 ` Peng Fan
2020-06-29 6:25 ` Peng Fan
2020-06-29 6:33 ` Michael S. Tsirkin
2020-06-29 6:33 ` Michael S. Tsirkin
2020-06-29 6:33 ` Michael S. Tsirkin
2020-06-29 6:33 ` Michael S. Tsirkin
2020-06-29 6:33 ` Michael S. Tsirkin
2020-06-29 6:35 ` Peng Fan
2020-06-29 6:35 ` Peng Fan
2020-06-29 6:35 ` Peng Fan
2020-06-29 6:35 ` Peng Fan
2020-06-29 6:35 ` Peng Fan
2020-06-29 23:49 ` Stefano Stabellini
2020-06-29 23:49 ` Stefano Stabellini
2020-06-29 23:49 ` Stefano Stabellini
2020-06-29 23:49 ` Stefano Stabellini
2020-06-30 1:40 ` Peng Fan
2020-06-30 1:40 ` Peng Fan
2020-06-30 1:40 ` Peng Fan
2020-06-30 1:40 ` Peng Fan
2020-06-29 23:46 ` Stefano Stabellini
2020-06-29 23:46 ` Stefano Stabellini
2020-06-29 23:46 ` Stefano Stabellini
2020-06-29 23:46 ` Stefano Stabellini
2020-07-01 13:34 ` Christoph Hellwig
2020-07-01 13:34 ` Christoph Hellwig
2020-07-01 13:34 ` Christoph Hellwig
2020-07-01 13:34 ` Christoph Hellwig
2020-07-01 17:34 ` Stefano Stabellini
2020-07-01 17:34 ` Stefano Stabellini
2020-07-01 17:34 ` Stefano Stabellini
2020-07-01 17:34 ` Stefano Stabellini
2020-07-01 20:47 ` Michael S. Tsirkin
2020-07-01 20:47 ` Michael S. Tsirkin
2020-07-01 20:47 ` Michael S. Tsirkin
2020-07-01 20:47 ` Michael S. Tsirkin
2020-07-01 20:47 ` Michael S. Tsirkin
2020-07-01 21:23 ` Michael S. Tsirkin
2020-07-01 21:23 ` Michael S. Tsirkin
2020-07-01 21:23 ` Michael S. Tsirkin
2020-07-01 21:23 ` Michael S. Tsirkin
2020-07-10 17:23 ` Stefano Stabellini
2020-07-10 17:23 ` Stefano Stabellini
2020-07-10 17:23 ` Stefano Stabellini
2020-07-10 17:23 ` Stefano Stabellini
2020-07-11 18:44 ` Michael S. Tsirkin [this message]
2020-07-11 18:44 ` Michael S. Tsirkin
2020-07-11 18:44 ` Michael S. Tsirkin
2020-07-11 18:44 ` Michael S. Tsirkin
2020-07-15 17:06 ` Stefano Stabellini
2020-07-15 17:06 ` Stefano Stabellini
2020-07-15 17:06 ` Stefano Stabellini
2020-07-15 17:06 ` Stefano Stabellini
2024-07-30 10:59 ` Amneesh Singh
2024-07-30 22:29 ` Stefano Stabellini
2020-07-13 1:53 ` Peng Fan
2020-07-13 1:53 ` Peng Fan
2020-07-13 1:53 ` Peng Fan
2020-06-29 3:00 ` Peng Fan
2020-06-29 3:00 ` Peng Fan
2020-06-29 3:00 ` Peng Fan
2020-06-29 3:00 ` Peng Fan
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=20200711144334-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jasowang@redhat.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=sstabellini@kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@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.