Hey Jason,
> From: Jason Wang
> Sent: Tuesday, October 20, 2020 2:18 PM
>
> On 2020/10/15 ??6:14, Liu, Yi L wrote:
> >> From: Jason Wang
> >> Sent: Thursday, October 15, 2020 4:41 PM
> >>
> >>
> >> On 2020/10/15 ??3:58, Tian, Kevin wrote:
> From: Jason Wang
> Sent: Thursday, October
On 9/30/2020 1:14 PM, vji...@codeaurora.org wrote:
> From: Vijayanand Jitta
>
> When ever a new iova alloc request comes iova is always searched
> from the cached node and the nodes which are previous to cached
> node. So, even if there is free iova space available in the nodes
> which are nex
On 9/30/2020 1:14 PM, vji...@codeaurora.org wrote:
> From: Vijayanand Jitta
>
> When ever an iova alloc request fails we free the iova
> ranges present in the percpu iova rcaches and then retry
> but the global iova rcache is not freed as a result we could
> still see iova alloc failure even a
Hi Yi:
On 2020/10/20 下午4:19, Liu, Yi L wrote:
Yes, but since PASID is a global identifier now, I think kernel should
track the a device list per PASID?
We have such track. It's done in iommu driver. You can refer to the
struct intel_svm. PASID is a global identifier, but it doesn’t affect that
> From: Jason Wang
> Sent: Tuesday, October 20, 2020 5:20 PM
>
> Hi Yi:
>
> On 2020/10/20 ??4:19, Liu, Yi L wrote:
> >> Yes, but since PASID is a global identifier now, I think kernel
> >> should track the a device list per PASID?
> > We have such track. It's done in iommu driver. You can refer
Due to a mismerge a bunch of prototypes that should have moved to
dma-map-ops.h are still in dma-mapping.h, fix that up.
Signed-off-by: Christoph Hellwig
---
include/linux/dma-map-ops.h | 23 +++
include/linux/dma-mapping.h | 24
kernel/dma/remap.c
> From: Jason Gunthorpe
> Sent: Monday, October 19, 2020 10:25 PM
>
> On Mon, Oct 19, 2020 at 08:39:03AM +, Liu, Yi L wrote:
> > Hi Jason,
> >
> > Good to see your response.
>
> Ah, I was away
got it. :-)
> > > > > Second, IOMMU nested translation is a per IOMMU domain
> > > > > capability
On Tue, Oct 20, 2020 at 09:40:14AM +, Liu, Yi L wrote:
> > See previous discussion with Kevin. If I understand correctly, you expect a
> > shared
> > L2 table if vDPA and VFIO device are using the same PASID.
>
> L2 table sharing is not mandatory. The mapping is the same, but no need to
> as
On Mon, Sep 28, 2020 at 02:38:28PM -0700, Jacob Pan wrote:
> IOASID is used to identify address spaces that can be targeted by device
> DMA. It is a system-wide resource that is essential to its many users.
> This document is an attempt to help developers from all vendors navigate
> the APIs. At th
> From: Jason Gunthorpe
> Sent: Tuesday, October 20, 2020 9:55 PM
>
> On Tue, Oct 20, 2020 at 09:40:14AM +, Liu, Yi L wrote:
>
> > > See previous discussion with Kevin. If I understand correctly, you expect
> > > a
> shared
> > > L2 table if vDPA and VFIO device are using the same PASID.
>
On Tue, Oct 20, 2020 at 10:21:41AM +, Liu, Yi L wrote:
> > I'm sure there will be some
> > weird overlaps because we can't delete any of the existing VFIO APIs, but
> > that
> > should not be a blocker.
>
> but the weird thing is what we should consider. And it perhaps not just
> overlap, it
On Tue, Oct 20, 2020 at 02:00:31PM +, Liu, Yi L wrote:
> > From: Jason Gunthorpe
> > Sent: Tuesday, October 20, 2020 9:55 PM
> >
> > On Tue, Oct 20, 2020 at 09:40:14AM +, Liu, Yi L wrote:
> >
> > > > See previous discussion with Kevin. If I understand correctly, you
> > > > expect a
> >
> From: Jason Gunthorpe
> Sent: Tuesday, October 20, 2020 10:05 PM
> To: Liu, Yi L
>
> On Tue, Oct 20, 2020 at 02:00:31PM +, Liu, Yi L wrote:
> > > From: Jason Gunthorpe
> > > Sent: Tuesday, October 20, 2020 9:55 PM
> > >
> > > On Tue, Oct 20, 2020 at 09:40:14AM +, Liu, Yi L wrote:
> >
> From: Jason Gunthorpe
> Sent: Tuesday, October 20, 2020 10:02 PM
[...]
> > > Whoever provides the vIOMMU emulation and relays the page fault to the
> guest
> > > has to translate the RID -
> >
> > that's the point. But the device info (especially the sub-device info) is
> > within the passthru f
Hi Jason,
On Tue, Oct 20, 2020 at 11:02:17AM -0300, Jason Gunthorpe wrote:
> On Tue, Oct 20, 2020 at 10:21:41AM +, Liu, Yi L wrote:
>
> > > I'm sure there will be some
> > > weird overlaps because we can't delete any of the existing VFIO APIs, but
> > > that
> > > should not be a blocker.
>
The pull request you sent on Mon, 19 Oct 2020 17:44:23 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git
> tags/iommu-fix-v5.10
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5c7e3f3f5cbc31118914ceee969154582ad3aa6b
Thank you!
--
Deet-doot-dot,
On Tue, Oct 20, 2020 at 09:24:30AM -0700, Raj, Ashok wrote:
> Hi Jason,
>
>
> On Tue, Oct 20, 2020 at 11:02:17AM -0300, Jason Gunthorpe wrote:
> > On Tue, Oct 20, 2020 at 10:21:41AM +, Liu, Yi L wrote:
> >
> > > > I'm sure there will be some
> > > > weird overlaps because we can't delete any
On Tue, Oct 20, 2020 at 02:03:36PM -0300, Jason Gunthorpe wrote:
> On Tue, Oct 20, 2020 at 09:24:30AM -0700, Raj, Ashok wrote:
> > Hi Jason,
> >
> >
> > On Tue, Oct 20, 2020 at 11:02:17AM -0300, Jason Gunthorpe wrote:
> > > On Tue, Oct 20, 2020 at 10:21:41AM +, Liu, Yi L wrote:
> > >
> > > >
On Tue, Oct 20, 2020 at 12:51:46PM -0700, Raj, Ashok wrote:
> I think we agreed (or agree to disagree and commit) for device types that
> we have for SIOV, VFIO based approach works well without having to re-invent
> another way to do the same things. Not looking for a shortcut by any means,
> b
On Tue, Oct 20, 2020 at 04:55:57PM -0300, Jason Gunthorpe wrote:
> On Tue, Oct 20, 2020 at 12:51:46PM -0700, Raj, Ashok wrote:
> > I think we agreed (or agree to disagree and commit) for device types that
> > we have for SIOV, VFIO based approach works well without having to
> > re-invent
> > an
On Tue, Oct 20, 2020 at 01:08:44PM -0700, Raj, Ashok wrote:
> On Tue, Oct 20, 2020 at 04:55:57PM -0300, Jason Gunthorpe wrote:
> > On Tue, Oct 20, 2020 at 12:51:46PM -0700, Raj, Ashok wrote:
> > > I think we agreed (or agree to disagree and commit) for device types that
> > > we have for SIOV, VFI
On Tue, Oct 20, 2020 at 05:14:03PM -0300, Jason Gunthorpe wrote:
> On Tue, Oct 20, 2020 at 01:08:44PM -0700, Raj, Ashok wrote:
> > On Tue, Oct 20, 2020 at 04:55:57PM -0300, Jason Gunthorpe wrote:
> > > On Tue, Oct 20, 2020 at 12:51:46PM -0700, Raj, Ashok wrote:
> > > > I think we agreed (or agree t
On 2020/10/20 下午10:19, Liu, Yi L wrote:
From: Jason Gunthorpe
Sent: Tuesday, October 20, 2020 10:02 PM
[...]
Whoever provides the vIOMMU emulation and relays the page fault to the
guest
has to translate the RID -
that's the point. But the device info (especially the sub-device info) is
wit
23 matches
Mail list logo
