On 05/09/2018 19:18, Jacob Pan wrote:
> On Wed, 5 Sep 2018 14:14:12 +0200
> Auger Eric wrote:
>
>>> + *
>>> + * On Arm and AMD IOMMUs, entry 0 of the PASID table can be used
>>> to hold
>>> + * non-PASID translations. In this case PASID 0 is reserved and
>>> entry 0 points
>>> + * to the io_pgtab
On 05/09/2018 13:14, Auger Eric wrote:
>> +static struct io_mm *
>> +io_mm_alloc(struct iommu_domain *domain, struct device *dev,
>> +struct mm_struct *mm, unsigned long flags)
>> +{
>> +int ret;
>> +int pasid;
>> +struct io_mm *io_mm;
>> +struct iommu_sva_param *param = dev
On Wed, 5 Sep 2018 14:14:12 +0200
Auger Eric wrote:
> > + *
> > + * On Arm and AMD IOMMUs, entry 0 of the PASID table can be used
> > to hold
> > + * non-PASID translations. In this case PASID 0 is reserved and
> > entry 0 points
> > + * to the io_pgtable base. On Intel IOMMU, the io_pgtable base
Hi Jean-Philippe,
On 05/11/2018 09:06 PM, Jean-Philippe Brucker wrote:
> Allocate IOMMU mm structures and binding them to devices. Four operations
s/binding/bind
> are added to IOMMU drivers:
>
> * mm_alloc(): to create an io_mm structure and perform architecture-
> specific operations required
, Jacob Pan ,
> "alex.william...@redhat.com" ,
> "rgum...@xilinx.com" , "thunder.leiz...@huawei.com"
> , "linux-arm-ker...@lists.infradead.org"
> , "shunyong.y...@hxt-semitech.com"
> , "dw...@infradead.org"
> , "liu
.com" , Jacob Pan
> , "alex.william...@redhat.com"
> , "rgum...@xilinx.com" ,
> "thunder.leiz...@huawei.com" ,
> "linux-arm-ker...@lists.infradead.org"
> , "shunyong.y...@hxt-semitech.com"
> , "dw...@infradead.org"
>
, Jacob Pan ,
> "alex.william...@redhat.com" ,
> "rgum...@xilinx.com" , "thunder.leiz...@huawei.com"
> , "linux-arm-ker...@lists.infradead.org"
> , "shunyong.y...@hxt-semitech.com"
> , "dw...@infradead.org"
> , "liu
+CC Kenneth Lee
On Fri, 25 May 2018 09:33:11 +0300
Ilias Apalodimas wrote:
> On Thu, May 24, 2018 at 04:04:39PM +0100, Jean-Philippe Brucker wrote:
> > On 24/05/18 12:50, Ilias Apalodimas wrote:
> > >> Interesting, I hadn't thought about this use-case before. At first I
> > >> thought you were
On Thu, May 24, 2018 at 04:04:39PM +0100, Jean-Philippe Brucker wrote:
> On 24/05/18 12:50, Ilias Apalodimas wrote:
> >> Interesting, I hadn't thought about this use-case before. At first I
> >> thought you were talking about mdev devices assigned to VMs, but I think
> >> you're referring to mdevs
On 24/05/18 12:50, Ilias Apalodimas wrote:
>> Interesting, I hadn't thought about this use-case before. At first I
>> thought you were talking about mdev devices assigned to VMs, but I think
>> you're referring to mdevs assigned to userspace drivers instead? Out of
>> curiosity, is it only theoreti
> Interesting, I hadn't thought about this use-case before. At first I
> thought you were talking about mdev devices assigned to VMs, but I think
> you're referring to mdevs assigned to userspace drivers instead? Out of
> curiosity, is it only theoretical or does someone actually need this?
There
On 22/05/18 17:43, Jacob Pan wrote:
> On Thu, 17 May 2018 11:02:42 +0100
> Jean-Philippe Brucker wrote:
>
>> On 17/05/18 00:31, Jacob Pan wrote:
>>> On Fri, 11 May 2018 20:06:04 +0100
>>> I am a little confused about domain vs. pasid relationship. If
>>> each domain represents a address space, sh
On Thu, 17 May 2018 11:02:42 +0100
Jean-Philippe Brucker wrote:
> On 17/05/18 00:31, Jacob Pan wrote:
> > On Fri, 11 May 2018 20:06:04 +0100
> > I am a little confused about domain vs. pasid relationship. If
> > each domain represents a address space, should there be a domain for
> > each pasid?
On 17/05/18 15:25, Jonathan Cameron wrote:
>> +static struct io_mm *
>> +io_mm_alloc(struct iommu_domain *domain, struct device *dev,
>> +struct mm_struct *mm, unsigned long flags)
>> +{
>> +int ret;
>> +int pasid;
>> +struct io_mm *io_mm;
>> +struct iommu_sva_param *param =
On Fri, 11 May 2018 20:06:04 +0100
Jean-Philippe Brucker wrote:
> Allocate IOMMU mm structures and binding them to devices. Four operations
> are added to IOMMU drivers:
>
> * mm_alloc(): to create an io_mm structure and perform architecture-
> specific operations required to grab the process
On 17/05/18 00:31, Jacob Pan wrote:
> On Fri, 11 May 2018 20:06:04 +0100
> I am a little confused about domain vs. pasid relationship. If
> each domain represents a address space, should there be a domain for
> each pasid?
I don't think there is a formal definition, but from previous discussion
th
On Fri, 11 May 2018 20:06:04 +0100
Jean-Philippe Brucker wrote:
> Allocate IOMMU mm structures and binding them to devices. Four
> operations are added to IOMMU drivers:
>
> * mm_alloc(): to create an io_mm structure and perform architecture-
> specific operations required to grab the process
Allocate IOMMU mm structures and binding them to devices. Four operations
are added to IOMMU drivers:
* mm_alloc(): to create an io_mm structure and perform architecture-
specific operations required to grab the process (for instance on ARM,
pin down the CPU ASID so that the process doesn't ge
18 matches
Mail list logo