[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y/aECHpCo4LJ1Rw2@nvidia.com>
Date: Wed, 22 Feb 2023 17:07:20 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Yi Liu <yi.l.liu@...el.com>
Cc: joro@...tes.org, alex.williamson@...hat.com, kevin.tian@...el.com,
robin.murphy@....com, cohuck@...hat.com, eric.auger@...hat.com,
nicolinc@...dia.com, kvm@...r.kernel.org, mjrosato@...ux.ibm.com,
chao.p.peng@...ux.intel.com, yi.y.sun@...ux.intel.com,
peterx@...hat.com, jasowang@...hat.com,
shameerali.kolothum.thodi@...wei.com, lulu@...hat.com,
suravee.suthikulpanit@....com, iommu@...ts.linux.dev,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
baolu.lu@...ux.intel.com
Subject: Re: [PATCH 0/6] iommufd: Add iommu capability reporting
On Wed, Feb 08, 2023 at 08:16:36PM -0800, Yi Liu wrote:
> iommufd gives userspace the capabilty to manipulating iommu subsytem.
> e.g. DMA map/unmap etc. In the near future, it will also support iommu
> nested translation. Different platform vendors have different implementation
> for the nested translation. So before set up nested translation, userspace
> needs to know the hardware iommu capabilities. For example, Intel platform
> supports guest I/O page table to be the first stage translation structure.
>
> This series reports the iommu capability for a given iommufd_device which
> has been bound to iommufd. It is a preparation work for nested translation
> support[1]. In this series, Intel VT-d capability reporting is added. Other
> vendors may add their own reporting based on this series.
>
> [1] https://github.com/yiliu1765/iommufd/tree/iommufd_nesting_vtd_v1
Let's have the comments addressed and this rebased on top of
https://github.com/jgunthorpe/linux/commits/iommufd_hwpt
Which should address eg the selftest issue
I want to start chipping away at bits of the nesting patch pile and
this part looks close
Thanks,
Jason
Powered by blists - more mailing lists