Re: [PATCH v2 02/40] iommu/sva: Bind process address spaces to devices

2018-09-06 Thread Jean-Philippe Brucker
On 05/09/2018 12:29, Auger Eric wrote: >> +/** >> + * iommu_sva_bind_device() - Bind a process address space to a device >> + * @dev: the device >> + * @mm: the mm to bind, caller must hold a reference to it >> + * @pasid: valid address where the PASID will be stored >> + * @flags: bond properties

Re: [PATCH v2 02/40] iommu/sva: Bind process address spaces to devices

2018-09-05 Thread Auger Eric
Hi Jean-Philippe, On 05/11/2018 09:06 PM, Jean-Philippe Brucker wrote: > Add bind() and unbind() operations to the IOMMU API. Bind() returns a > PASID that drivers can program in hardware, to let their devices access an > mm. This patch only adds skeletons for the device driver API, most of the >

Re: [PATCH v2 02/40] iommu/sva: Bind process address spaces to devices

2018-05-21 Thread Jean-Philippe Brucker
On 17/05/18 14:10, Jonathan Cameron wrote: > On Fri, 11 May 2018 20:06:03 +0100 > Jean-Philippe Brucker wrote: > >> Add bind() and unbind() operations to the IOMMU API. Bind() returns a >> PASID that drivers can program in hardware, to let their devices access an

Re: [PATCH v2 02/40] iommu/sva: Bind process address spaces to devices

2018-05-17 Thread Jonathan Cameron
On Fri, 11 May 2018 20:06:03 +0100 Jean-Philippe Brucker wrote: > Add bind() and unbind() operations to the IOMMU API. Bind() returns a > PASID that drivers can program in hardware, to let their devices access an > mm. This patch only adds skeletons for the device

[PATCH v2 02/40] iommu/sva: Bind process address spaces to devices

2018-05-11 Thread Jean-Philippe Brucker
Add bind() and unbind() operations to the IOMMU API. Bind() returns a PASID that drivers can program in hardware, to let their devices access an mm. This patch only adds skeletons for the device driver API, most of the implementation is still missing. IOMMU groups with more than one device aren't