From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
"jgross@suse.com" <jgross@suse.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
Date: Mon, 29 Jun 2020 02:33:39 -0400 [thread overview]
Message-ID: <20200629023225-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <DB6PR0402MB27602AB2A9A242D79343CE48886E0@DB6PR0402MB2760.eurprd04.prod.outlook.com>
On Mon, Jun 29, 2020 at 06:25:41AM +0000, Peng Fan wrote:
> > > > > Anyway, re-reading the last messages of the original thread [1],
> > > > > it looks like Peng had a clear idea on how to fix the general issue.
> > > > > Peng, what happened with that?
> > >
> > > We shrinked the rpmsg reserved area to workaround the issue.
> > > So still use the dma apis in rpmsg.
> > >
> > > But here I am going to address domu android trusty issue using virtio.
> >
> > My suggestion is to first of all fix DMA API so it works properly.
>
> Could you please elaborate more details?
>
> You mean the DMA API usage of rpmsg? Or xen domu dma_ops?
>
> Thanks,
> Peng.
Not 100% sure but I think xen dma ops.
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: "jgross@suse.com" <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
dl-linux-imx <linux-imx@nxp.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
Date: Mon, 29 Jun 2020 02:33:39 -0400 [thread overview]
Message-ID: <20200629023225-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <DB6PR0402MB27602AB2A9A242D79343CE48886E0@DB6PR0402MB2760.eurprd04.prod.outlook.com>
On Mon, Jun 29, 2020 at 06:25:41AM +0000, Peng Fan wrote:
> > > > > Anyway, re-reading the last messages of the original thread [1],
> > > > > it looks like Peng had a clear idea on how to fix the general issue.
> > > > > Peng, what happened with that?
> > >
> > > We shrinked the rpmsg reserved area to workaround the issue.
> > > So still use the dma apis in rpmsg.
> > >
> > > But here I am going to address domu android trusty issue using virtio.
> >
> > My suggestion is to first of all fix DMA API so it works properly.
>
> Could you please elaborate more details?
>
> You mean the DMA API usage of rpmsg? Or xen domu dma_ops?
>
> Thanks,
> Peng.
Not 100% sure but I think xen dma ops.
--
MST
_______________________________________________
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: Peng Fan <peng.fan@nxp.com>
Cc: "jgross@suse.com" <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
dl-linux-imx <linux-imx@nxp.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
Date: Mon, 29 Jun 2020 02:33:39 -0400 [thread overview]
Message-ID: <20200629023225-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <DB6PR0402MB27602AB2A9A242D79343CE48886E0@DB6PR0402MB2760.eurprd04.prod.outlook.com>
On Mon, Jun 29, 2020 at 06:25:41AM +0000, Peng Fan wrote:
> > > > > Anyway, re-reading the last messages of the original thread [1],
> > > > > it looks like Peng had a clear idea on how to fix the general issue.
> > > > > Peng, what happened with that?
> > >
> > > We shrinked the rpmsg reserved area to workaround the issue.
> > > So still use the dma apis in rpmsg.
> > >
> > > But here I am going to address domu android trusty issue using virtio.
> >
> > My suggestion is to first of all fix DMA API so it works properly.
>
> Could you please elaborate more details?
>
> You mean the DMA API usage of rpmsg? Or xen domu dma_ops?
>
> Thanks,
> Peng.
Not 100% sure but I think xen dma ops.
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: "jgross@suse.com" <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
dl-linux-imx <linux-imx@nxp.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
Date: Mon, 29 Jun 2020 02:33:39 -0400 [thread overview]
Message-ID: <20200629023225-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <DB6PR0402MB27602AB2A9A242D79343CE48886E0@DB6PR0402MB2760.eurprd04.prod.outlook.com>
On Mon, Jun 29, 2020 at 06:25:41AM +0000, Peng Fan wrote:
> > > > > Anyway, re-reading the last messages of the original thread [1],
> > > > > it looks like Peng had a clear idea on how to fix the general issue.
> > > > > Peng, what happened with that?
> > >
> > > We shrinked the rpmsg reserved area to workaround the issue.
> > > So still use the dma apis in rpmsg.
> > >
> > > But here I am going to address domu android trusty issue using virtio.
> >
> > My suggestion is to first of all fix DMA API so it works properly.
>
> Could you please elaborate more details?
>
> You mean the DMA API usage of rpmsg? Or xen domu dma_ops?
>
> Thanks,
> Peng.
Not 100% sure but I think xen dma ops.
--
MST
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: "jgross@suse.com" <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
dl-linux-imx <linux-imx@nxp.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
Date: Mon, 29 Jun 2020 02:33:39 -0400 [thread overview]
Message-ID: <20200629023225-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <DB6PR0402MB27602AB2A9A242D79343CE48886E0@DB6PR0402MB2760.eurprd04.prod.outlook.com>
On Mon, Jun 29, 2020 at 06:25:41AM +0000, Peng Fan wrote:
> > > > > Anyway, re-reading the last messages of the original thread [1],
> > > > > it looks like Peng had a clear idea on how to fix the general issue.
> > > > > Peng, what happened with that?
> > >
> > > We shrinked the rpmsg reserved area to workaround the issue.
> > > So still use the dma apis in rpmsg.
> > >
> > > But here I am going to address domu android trusty issue using virtio.
> >
> > My suggestion is to first of all fix DMA API so it works properly.
>
> Could you please elaborate more details?
>
> You mean the DMA API usage of rpmsg? Or xen domu dma_ops?
>
> Thanks,
> Peng.
Not 100% sure but I think xen dma ops.
--
MST
next prev parent reply other threads:[~2020-06-29 18:38 UTC|newest]
Thread overview: 113+ 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 [this message]
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-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-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
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
2020-07-13 1:53 ` Peng Fan
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
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=20200629023225-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--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.