On Thu, Feb 28, 2019 at 01:15:49PM -0800, Jacob Pan wrote:
> On Thu, 28 Feb 2019 15:09:50 +0100
> Joerg Roedel wrote:
>
> > Hi Jacob,
> >
> > On Wed, Feb 27, 2019 at 01:41:29PM -0800, Jacob Pan wrote:
> > > On Tue, 26 Feb 2019 12:17:43 +0100
> > > Joerg Roedel wrote:
> >
> > > Just trying to
On Thu, 28 Feb 2019 15:09:50 +0100
Joerg Roedel wrote:
> Hi Jacob,
>
> On Wed, Feb 27, 2019 at 01:41:29PM -0800, Jacob Pan wrote:
> > On Tue, 26 Feb 2019 12:17:43 +0100
> > Joerg Roedel wrote:
>
> > Just trying to understand how to use this API.
> > So if we bind the same mm to two different
On Thu, 28 Feb 2019 01:10:55 +
"Tian, Kevin" wrote:
> > From: Jacob Pan [mailto:jacob.jun@linux.intel.com]
> > Sent: Thursday, February 28, 2019 5:41 AM
> >
> > On Tue, 26 Feb 2019 12:17:43 +0100
> > Joerg Roedel wrote:
> >
> > >
> > > How about a 'struct iommu_sva' with an iommu-pri
On Thu, 28 Feb 2019 12:19:22 +
Jean-Philippe Brucker wrote:
> On 27/02/2019 21:41, Jacob Pan wrote:
> > On Tue, 26 Feb 2019 12:17:43 +0100
> > Joerg Roedel wrote:
> >
> >> Hi Jean-Philippe,
> >>
> >> Thanks for the patch! I think this is getting close to be applied
> >> after the next mer
Hi Jacob,
On Wed, Feb 27, 2019 at 01:41:29PM -0800, Jacob Pan wrote:
> On Tue, 26 Feb 2019 12:17:43 +0100
> Joerg Roedel wrote:
> Just trying to understand how to use this API.
> So if we bind the same mm to two different devices, we should get two
> different iommu_sva handle, right?
> I think
On 27/02/2019 21:41, Jacob Pan wrote:
> On Tue, 26 Feb 2019 12:17:43 +0100
> Joerg Roedel wrote:
>
>> Hi Jean-Philippe,
>>
>> Thanks for the patch! I think this is getting close to be applied
>> after the next merge window.
>>
>> On Wed, Feb 20, 2019 at 02:27:59PM +, Jean-Philippe Brucker wro
> From: Jacob Pan [mailto:jacob.jun@linux.intel.com]
> Sent: Thursday, February 28, 2019 5:41 AM
>
> On Tue, 26 Feb 2019 12:17:43 +0100
> Joerg Roedel wrote:
>
> >
> > How about a 'struct iommu_sva' with an iommu-private definition that
> > is returned by this function:
> >
> > struct io
On Tue, 26 Feb 2019 12:17:43 +0100
Joerg Roedel wrote:
> Hi Jean-Philippe,
>
> Thanks for the patch! I think this is getting close to be applied
> after the next merge window.
>
> On Wed, Feb 20, 2019 at 02:27:59PM +, Jean-Philippe Brucker wrote:
> > +int iommu_sva_bind_device(struct device
On Tue, Feb 26, 2019 at 12:49:15PM +, Jean-Philippe Brucker wrote:
> On 26/02/2019 11:17, Joerg Roedel wrote:
> > int iommu_sva_get_pasid(struct iommu_sva *handle);
> > void iommu_sva_set_exit_handler(struct iommu_sva *handle,
> > iommu_mm_exit_handle
On 26/02/2019 11:17, Joerg Roedel wrote:
> Hi Jean-Philippe,
>
> Thanks for the patch! I think this is getting close to be applied after
> the next merge window.
>
> On Wed, Feb 20, 2019 at 02:27:59PM +, Jean-Philippe Brucker wrote:
>> +int iommu_sva_bind_device(struct device *dev, struct mm_
Hi Jean-Philippe,
Thanks for the patch! I think this is getting close to be applied after
the next merge window.
On Wed, Feb 20, 2019 at 02:27:59PM +, Jean-Philippe Brucker wrote:
> +int iommu_sva_bind_device(struct device *dev, struct mm_struct *mm, int
> *pasid,
> + i
11 matches
Mail list logo
