From: Tomasz Jeznach <tjeznach@rivosinc.com> To: Jason Gunthorpe <jgg@ziepe.ca> Cc: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>, Robin Murphy <robin.murphy@arm.com>, Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Anup Patel <apatel@ventanamicro.com>, Sunil V L <sunilvl@ventanamicro.com>, Nick Kossifidis <mick@ics.forth.gr>, Sebastien Boeuf <seb@rivosinc.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzk+dt@kernel.org>, Conor Dooley <conor+dt@kernel.org>, devicetree@vger.kernel.org, iommu@lists.linux.dev, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, linux@rivosinc.com Subject: Re: [PATCH v2 7/7] iommu/riscv: Paging domain support Date: Wed, 24 Apr 2024 16:30:45 -0700 [thread overview] Message-ID: <CAH2o1u5+XD9YN=gdMVtfkyhKoKha0UpwKgOVbCAwOQa+saPfRw@mail.gmail.com> (raw) In-Reply-To: <20240419125627.GD223006@ziepe.ca> On Fri, Apr 19, 2024 at 5:56 AM Jason Gunthorpe <jgg@ziepe.ca> wrote: > > On Thu, Apr 18, 2024 at 09:32:25AM -0700, Tomasz Jeznach wrote: > > > diff --git a/drivers/iommu/riscv/iommu.c b/drivers/iommu/riscv/iommu.c > > index a4f74588cdc2..32ddc372432d 100644 > > --- a/drivers/iommu/riscv/iommu.c > > +++ b/drivers/iommu/riscv/iommu.c > > @@ -46,6 +46,10 @@ MODULE_LICENSE("GPL"); > > #define dev_to_iommu(dev) \ > > container_of((dev)->iommu->iommu_dev, struct riscv_iommu_device, iommu) > > > > +/* IOMMU PSCID allocation namespace. */ > > +static DEFINE_IDA(riscv_iommu_pscids); > > +#define RISCV_IOMMU_MAX_PSCID BIT(20) > > + > > You may consider putting this IDA in the riscv_iommu_device() and move > the pscid from the domain to the bond? > I've been considering containing IDA inside riscv_iommu_device at some point, but it made PCSID management more complicated. In the follow up patches it is desired for PSCID to be unique across all IOMMUs in the system (within guest's GSCID), as the protection domains might (and will) be shared between more than single IOMMU device. > > /* Device resource-managed allocations */ > > struct riscv_iommu_devres { > > unsigned long addr; > > @@ -752,12 +756,77 @@ static int riscv_iommu_ddt_alloc(struct riscv_iommu_device *iommu) > > return 0; > > } > > > > +struct riscv_iommu_bond { > > + struct list_head list; > > + struct rcu_head rcu; > > + struct device *dev; > > +}; > > + > > +/* This struct contains protection domain specific IOMMU driver data. */ > > +struct riscv_iommu_domain { > > + struct iommu_domain domain; > > + struct list_head bonds; > > + int pscid; > > + int numa_node; > > + int amo_enabled:1; > > + unsigned int pgd_mode; > > + /* paging domain */ > > + unsigned long pgd_root; > > +}; > > Glad to see there is no riscv_iommu_device pointer in the domain! > > > +static void riscv_iommu_iotlb_inval(struct riscv_iommu_domain *domain, > > + unsigned long start, unsigned long end) > > +{ > > + struct riscv_iommu_bond *bond; > > + struct riscv_iommu_device *iommu; > > + struct riscv_iommu_command cmd; > > + unsigned long len = end - start + 1; > > + unsigned long iova; > > + > > + rcu_read_lock(); > > + list_for_each_entry_rcu(bond, &domain->bonds, list) { > > + iommu = dev_to_iommu(bond->dev); > > Pedantically this locking isn't locked right, there is technically > nothing that prevents bond->dev and the iommu instance struct from > being freed here. eg iommufd can hit races here if userspace can hot > unplug devices. > > I suggest storing the iommu pointer itself in the bond instead of the > device then add a synchronize_rcu() to the iommu unregister path. > Very good point. Thanks for pointing this out. Reworked to add locking around list modifications (and do not incorrectly rely on iommu group mutex locks). > > + riscv_iommu_cmd_inval_vma(&cmd); > > + riscv_iommu_cmd_inval_set_pscid(&cmd, domain->pscid); > > + if (len > 0 && len < RISCV_IOMMU_IOTLB_INVAL_LIMIT) { > > + for (iova = start; iova < end; iova += PAGE_SIZE) { > > + riscv_iommu_cmd_inval_set_addr(&cmd, iova); > > + riscv_iommu_cmd_send(iommu, &cmd, 0); > > + } > > + } else { > > + riscv_iommu_cmd_send(iommu, &cmd, 0); > > + } > > + } > > This seems suboptimal, you probably want to copy the new design that > Intel is doing where you allocate "bonds" that are already > de-duplicated. Ie if I have 10 devices on the same iommu sharing the > domain the above will invalidate the PSCID 10 times. It should only be > done once. > > ie add a "bond" for the (iommu,pscid) and refcount that based on how > many devices are used. Then another "bond" for the ATS stuff eventually. > Agree, not perfect to send duplicate invalidations. This should improve with follow up patchsets introducing of SVA (reusing the same, extended bond structure) and update to send IOTLB range invalidations. For this change I've decided to go with as simple as possible implementation and over-invalidate for domains with multiple devices attached. Hope this makes sense. > > + > > + list_for_each_entry_rcu(bond, &domain->bonds, list) { > > + iommu = dev_to_iommu(bond->dev); > > + > > + riscv_iommu_cmd_iofence(&cmd); > > + riscv_iommu_cmd_send(iommu, &cmd, RISCV_IOMMU_QUEUE_TIMEOUT); > > + } > > + rcu_read_unlock(); > > +} > > + > > > @@ -787,12 +870,390 @@ static int riscv_iommu_attach_domain(struct riscv_iommu_device *iommu, > > xchg64(&dc->ta, ta); > > xchg64(&dc->tc, tc); > > > > - /* Device context invalidation will be required. Ignoring for now. */ > > + if (!(tc & RISCV_IOMMU_DC_TC_V)) > > + continue; > > No negative caching in HW? > No. Disallowed by the spec. > > + /* Invalidate device context cache */ > > + riscv_iommu_cmd_iodir_inval_ddt(&cmd); > > + riscv_iommu_cmd_iodir_set_did(&cmd, fwspec->ids[i]); > > + riscv_iommu_cmd_send(iommu, &cmd, 0); > > + > > + if (FIELD_GET(RISCV_IOMMU_PC_FSC_MODE, fsc) == RISCV_IOMMU_DC_FSC_MODE_BARE) > > + continue; > > + > > + /* Invalidate last valid PSCID */ > > + riscv_iommu_cmd_inval_vma(&cmd); > > + riscv_iommu_cmd_inval_set_pscid(&cmd, FIELD_GET(RISCV_IOMMU_DC_TA_PSCID, ta)); > > + riscv_iommu_cmd_send(iommu, &cmd, 0); > > + } > > + > > + /* Synchronize directory update */ > > + riscv_iommu_cmd_iofence(&cmd); > > + riscv_iommu_cmd_send(iommu, &cmd, RISCV_IOMMU_IOTINVAL_TIMEOUT); > > + > > + /* Track domain to devices mapping. */ > > + if (bond) > > + list_add_rcu(&bond->list, &domain->bonds); > > This is in the wrong order, the invalidation on the pscid needs to > start before the pscid is loaded into HW in the first place otherwise > concurrent invalidations may miss HW updates. > > > + > > + /* Remove tracking from previous domain, if needed. */ > > + iommu_domain = iommu_get_domain_for_dev(dev); > > + if (iommu_domain && !!(iommu_domain->type & __IOMMU_DOMAIN_PAGING)) { > > No need for !!, && is already booleanizing > > > + domain = iommu_domain_to_riscv(iommu_domain); > > + bond = NULL; > > + rcu_read_lock(); > > + list_for_each_entry_rcu(b, &domain->bonds, list) { > > + if (b->dev == dev) { > > + bond = b; > > + break; > > + } > > + } > > + rcu_read_unlock(); > > + > > + if (bond) { > > + list_del_rcu(&bond->list); > > + kfree_rcu(bond, rcu); > > + } > > + } > > + > > + return 0; > > +} > > > +static inline size_t get_page_size(size_t size) > > +{ > > + if (size >= IOMMU_PAGE_SIZE_512G) > > + return IOMMU_PAGE_SIZE_512G; > > + if (size >= IOMMU_PAGE_SIZE_1G) > > + return IOMMU_PAGE_SIZE_1G; > > + if (size >= IOMMU_PAGE_SIZE_2M) > > + return IOMMU_PAGE_SIZE_2M; > > + return IOMMU_PAGE_SIZE_4K; > > +} > > + > > +#define _io_pte_present(pte) ((pte) & (_PAGE_PRESENT | _PAGE_PROT_NONE)) > > +#define _io_pte_leaf(pte) ((pte) & _PAGE_LEAF) > > +#define _io_pte_none(pte) ((pte) == 0) > > +#define _io_pte_entry(pn, prot) ((_PAGE_PFN_MASK & ((pn) << _PAGE_PFN_SHIFT)) | (prot)) > > + > > +static void riscv_iommu_pte_free(struct riscv_iommu_domain *domain, > > + unsigned long pte, struct list_head *freelist) > > +{ > > + unsigned long *ptr; > > + int i; > > + > > + if (!_io_pte_present(pte) || _io_pte_leaf(pte)) > > + return; > > + > > + ptr = (unsigned long *)pfn_to_virt(__page_val_to_pfn(pte)); > > + > > + /* Recursively free all sub page table pages */ > > + for (i = 0; i < PTRS_PER_PTE; i++) { > > + pte = READ_ONCE(ptr[i]); > > + if (!_io_pte_none(pte) && cmpxchg_relaxed(ptr + i, pte, 0) == pte) > > + riscv_iommu_pte_free(domain, pte, freelist); > > + } > > + > > + if (freelist) > > + list_add_tail(&virt_to_page(ptr)->lru, freelist); > > + else > > + free_page((unsigned long)ptr); > > +} > > Consider putting the page table handling in its own file? > It was in separate file at some point, but merged to iommu.c, as its simple enough with ~300 lines only. Probably not worth separating this out. > > +static int riscv_iommu_attach_paging_domain(struct iommu_domain *iommu_domain, > > + struct device *dev) > > +{ > > + struct riscv_iommu_device *iommu = dev_to_iommu(dev); > > + struct riscv_iommu_domain *domain = iommu_domain_to_riscv(iommu_domain); > > + struct page *page; > > + > > + if (!riscv_iommu_pt_supported(iommu, domain->pgd_mode)) > > + return -ENODEV; > > + > > + domain->numa_node = dev_to_node(iommu->dev); > > + domain->amo_enabled = !!(iommu->caps & RISCV_IOMMU_CAP_AMO_HWAD); > > + > > + if (!domain->pgd_root) { > > + page = alloc_pages_node(domain->numa_node, > > + GFP_KERNEL_ACCOUNT | __GFP_ZERO, 0); > > + if (!page) > > + return -ENOMEM; > > + domain->pgd_root = (unsigned long)page_to_virt(page); > > The pgd_root should be allocated by the alloc_paging function, not > during attach. There is no locking here that will protect against > concurrent attach and also map before attach should work. > > You can pick up the numa affinity from the alloc paging dev pointer > (note it may be null still in some cases) > Good point. Thanks. Will send update shortly with v3. > Jason Ack to all other comments, thank you! Best, - Tomasz
WARNING: multiple messages have this Message-ID (diff)
From: Tomasz Jeznach <tjeznach@rivosinc.com> To: Jason Gunthorpe <jgg@ziepe.ca> Cc: Anup Patel <apatel@ventanamicro.com>, devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>, Albert Ou <aou@eecs.berkeley.edu>, linux@rivosinc.com, Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>, linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>, Sebastien Boeuf <seb@rivosinc.com>, iommu@lists.linux.dev, Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley <paul.walmsley@sifive.com>, Nick Kossifidis <mick@ics.forth.gr>, Krzysztof Kozlowski <krzk+dt@kernel.org>, Robin Murphy <robin.murphy@arm.com>, linux-riscv@lists.infradead.org Subject: Re: [PATCH v2 7/7] iommu/riscv: Paging domain support Date: Wed, 24 Apr 2024 16:30:45 -0700 [thread overview] Message-ID: <CAH2o1u5+XD9YN=gdMVtfkyhKoKha0UpwKgOVbCAwOQa+saPfRw@mail.gmail.com> (raw) In-Reply-To: <20240419125627.GD223006@ziepe.ca> On Fri, Apr 19, 2024 at 5:56 AM Jason Gunthorpe <jgg@ziepe.ca> wrote: > > On Thu, Apr 18, 2024 at 09:32:25AM -0700, Tomasz Jeznach wrote: > > > diff --git a/drivers/iommu/riscv/iommu.c b/drivers/iommu/riscv/iommu.c > > index a4f74588cdc2..32ddc372432d 100644 > > --- a/drivers/iommu/riscv/iommu.c > > +++ b/drivers/iommu/riscv/iommu.c > > @@ -46,6 +46,10 @@ MODULE_LICENSE("GPL"); > > #define dev_to_iommu(dev) \ > > container_of((dev)->iommu->iommu_dev, struct riscv_iommu_device, iommu) > > > > +/* IOMMU PSCID allocation namespace. */ > > +static DEFINE_IDA(riscv_iommu_pscids); > > +#define RISCV_IOMMU_MAX_PSCID BIT(20) > > + > > You may consider putting this IDA in the riscv_iommu_device() and move > the pscid from the domain to the bond? > I've been considering containing IDA inside riscv_iommu_device at some point, but it made PCSID management more complicated. In the follow up patches it is desired for PSCID to be unique across all IOMMUs in the system (within guest's GSCID), as the protection domains might (and will) be shared between more than single IOMMU device. > > /* Device resource-managed allocations */ > > struct riscv_iommu_devres { > > unsigned long addr; > > @@ -752,12 +756,77 @@ static int riscv_iommu_ddt_alloc(struct riscv_iommu_device *iommu) > > return 0; > > } > > > > +struct riscv_iommu_bond { > > + struct list_head list; > > + struct rcu_head rcu; > > + struct device *dev; > > +}; > > + > > +/* This struct contains protection domain specific IOMMU driver data. */ > > +struct riscv_iommu_domain { > > + struct iommu_domain domain; > > + struct list_head bonds; > > + int pscid; > > + int numa_node; > > + int amo_enabled:1; > > + unsigned int pgd_mode; > > + /* paging domain */ > > + unsigned long pgd_root; > > +}; > > Glad to see there is no riscv_iommu_device pointer in the domain! > > > +static void riscv_iommu_iotlb_inval(struct riscv_iommu_domain *domain, > > + unsigned long start, unsigned long end) > > +{ > > + struct riscv_iommu_bond *bond; > > + struct riscv_iommu_device *iommu; > > + struct riscv_iommu_command cmd; > > + unsigned long len = end - start + 1; > > + unsigned long iova; > > + > > + rcu_read_lock(); > > + list_for_each_entry_rcu(bond, &domain->bonds, list) { > > + iommu = dev_to_iommu(bond->dev); > > Pedantically this locking isn't locked right, there is technically > nothing that prevents bond->dev and the iommu instance struct from > being freed here. eg iommufd can hit races here if userspace can hot > unplug devices. > > I suggest storing the iommu pointer itself in the bond instead of the > device then add a synchronize_rcu() to the iommu unregister path. > Very good point. Thanks for pointing this out. Reworked to add locking around list modifications (and do not incorrectly rely on iommu group mutex locks). > > + riscv_iommu_cmd_inval_vma(&cmd); > > + riscv_iommu_cmd_inval_set_pscid(&cmd, domain->pscid); > > + if (len > 0 && len < RISCV_IOMMU_IOTLB_INVAL_LIMIT) { > > + for (iova = start; iova < end; iova += PAGE_SIZE) { > > + riscv_iommu_cmd_inval_set_addr(&cmd, iova); > > + riscv_iommu_cmd_send(iommu, &cmd, 0); > > + } > > + } else { > > + riscv_iommu_cmd_send(iommu, &cmd, 0); > > + } > > + } > > This seems suboptimal, you probably want to copy the new design that > Intel is doing where you allocate "bonds" that are already > de-duplicated. Ie if I have 10 devices on the same iommu sharing the > domain the above will invalidate the PSCID 10 times. It should only be > done once. > > ie add a "bond" for the (iommu,pscid) and refcount that based on how > many devices are used. Then another "bond" for the ATS stuff eventually. > Agree, not perfect to send duplicate invalidations. This should improve with follow up patchsets introducing of SVA (reusing the same, extended bond structure) and update to send IOTLB range invalidations. For this change I've decided to go with as simple as possible implementation and over-invalidate for domains with multiple devices attached. Hope this makes sense. > > + > > + list_for_each_entry_rcu(bond, &domain->bonds, list) { > > + iommu = dev_to_iommu(bond->dev); > > + > > + riscv_iommu_cmd_iofence(&cmd); > > + riscv_iommu_cmd_send(iommu, &cmd, RISCV_IOMMU_QUEUE_TIMEOUT); > > + } > > + rcu_read_unlock(); > > +} > > + > > > @@ -787,12 +870,390 @@ static int riscv_iommu_attach_domain(struct riscv_iommu_device *iommu, > > xchg64(&dc->ta, ta); > > xchg64(&dc->tc, tc); > > > > - /* Device context invalidation will be required. Ignoring for now. */ > > + if (!(tc & RISCV_IOMMU_DC_TC_V)) > > + continue; > > No negative caching in HW? > No. Disallowed by the spec. > > + /* Invalidate device context cache */ > > + riscv_iommu_cmd_iodir_inval_ddt(&cmd); > > + riscv_iommu_cmd_iodir_set_did(&cmd, fwspec->ids[i]); > > + riscv_iommu_cmd_send(iommu, &cmd, 0); > > + > > + if (FIELD_GET(RISCV_IOMMU_PC_FSC_MODE, fsc) == RISCV_IOMMU_DC_FSC_MODE_BARE) > > + continue; > > + > > + /* Invalidate last valid PSCID */ > > + riscv_iommu_cmd_inval_vma(&cmd); > > + riscv_iommu_cmd_inval_set_pscid(&cmd, FIELD_GET(RISCV_IOMMU_DC_TA_PSCID, ta)); > > + riscv_iommu_cmd_send(iommu, &cmd, 0); > > + } > > + > > + /* Synchronize directory update */ > > + riscv_iommu_cmd_iofence(&cmd); > > + riscv_iommu_cmd_send(iommu, &cmd, RISCV_IOMMU_IOTINVAL_TIMEOUT); > > + > > + /* Track domain to devices mapping. */ > > + if (bond) > > + list_add_rcu(&bond->list, &domain->bonds); > > This is in the wrong order, the invalidation on the pscid needs to > start before the pscid is loaded into HW in the first place otherwise > concurrent invalidations may miss HW updates. > > > + > > + /* Remove tracking from previous domain, if needed. */ > > + iommu_domain = iommu_get_domain_for_dev(dev); > > + if (iommu_domain && !!(iommu_domain->type & __IOMMU_DOMAIN_PAGING)) { > > No need for !!, && is already booleanizing > > > + domain = iommu_domain_to_riscv(iommu_domain); > > + bond = NULL; > > + rcu_read_lock(); > > + list_for_each_entry_rcu(b, &domain->bonds, list) { > > + if (b->dev == dev) { > > + bond = b; > > + break; > > + } > > + } > > + rcu_read_unlock(); > > + > > + if (bond) { > > + list_del_rcu(&bond->list); > > + kfree_rcu(bond, rcu); > > + } > > + } > > + > > + return 0; > > +} > > > +static inline size_t get_page_size(size_t size) > > +{ > > + if (size >= IOMMU_PAGE_SIZE_512G) > > + return IOMMU_PAGE_SIZE_512G; > > + if (size >= IOMMU_PAGE_SIZE_1G) > > + return IOMMU_PAGE_SIZE_1G; > > + if (size >= IOMMU_PAGE_SIZE_2M) > > + return IOMMU_PAGE_SIZE_2M; > > + return IOMMU_PAGE_SIZE_4K; > > +} > > + > > +#define _io_pte_present(pte) ((pte) & (_PAGE_PRESENT | _PAGE_PROT_NONE)) > > +#define _io_pte_leaf(pte) ((pte) & _PAGE_LEAF) > > +#define _io_pte_none(pte) ((pte) == 0) > > +#define _io_pte_entry(pn, prot) ((_PAGE_PFN_MASK & ((pn) << _PAGE_PFN_SHIFT)) | (prot)) > > + > > +static void riscv_iommu_pte_free(struct riscv_iommu_domain *domain, > > + unsigned long pte, struct list_head *freelist) > > +{ > > + unsigned long *ptr; > > + int i; > > + > > + if (!_io_pte_present(pte) || _io_pte_leaf(pte)) > > + return; > > + > > + ptr = (unsigned long *)pfn_to_virt(__page_val_to_pfn(pte)); > > + > > + /* Recursively free all sub page table pages */ > > + for (i = 0; i < PTRS_PER_PTE; i++) { > > + pte = READ_ONCE(ptr[i]); > > + if (!_io_pte_none(pte) && cmpxchg_relaxed(ptr + i, pte, 0) == pte) > > + riscv_iommu_pte_free(domain, pte, freelist); > > + } > > + > > + if (freelist) > > + list_add_tail(&virt_to_page(ptr)->lru, freelist); > > + else > > + free_page((unsigned long)ptr); > > +} > > Consider putting the page table handling in its own file? > It was in separate file at some point, but merged to iommu.c, as its simple enough with ~300 lines only. Probably not worth separating this out. > > +static int riscv_iommu_attach_paging_domain(struct iommu_domain *iommu_domain, > > + struct device *dev) > > +{ > > + struct riscv_iommu_device *iommu = dev_to_iommu(dev); > > + struct riscv_iommu_domain *domain = iommu_domain_to_riscv(iommu_domain); > > + struct page *page; > > + > > + if (!riscv_iommu_pt_supported(iommu, domain->pgd_mode)) > > + return -ENODEV; > > + > > + domain->numa_node = dev_to_node(iommu->dev); > > + domain->amo_enabled = !!(iommu->caps & RISCV_IOMMU_CAP_AMO_HWAD); > > + > > + if (!domain->pgd_root) { > > + page = alloc_pages_node(domain->numa_node, > > + GFP_KERNEL_ACCOUNT | __GFP_ZERO, 0); > > + if (!page) > > + return -ENOMEM; > > + domain->pgd_root = (unsigned long)page_to_virt(page); > > The pgd_root should be allocated by the alloc_paging function, not > during attach. There is no locking here that will protect against > concurrent attach and also map before attach should work. > > You can pick up the numa affinity from the alloc paging dev pointer > (note it may be null still in some cases) > Good point. Thanks. Will send update shortly with v3. > Jason Ack to all other comments, thank you! Best, - Tomasz _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-04-24 23:30 UTC|newest] Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-18 16:32 [PATCH v2 0/7] Linux RISC-V IOMMU Support Tomasz Jeznach 2024-04-18 16:32 ` Tomasz Jeznach 2024-04-18 16:32 ` [PATCH v2 1/7] dt-bindings: iommu: riscv: Add bindings for RISC-V IOMMU Tomasz Jeznach 2024-04-18 16:32 ` Tomasz Jeznach 2024-04-18 17:04 ` Conor Dooley 2024-04-18 17:04 ` Conor Dooley 2024-04-24 22:37 ` Tomasz Jeznach 2024-04-24 22:37 ` Tomasz Jeznach 2024-04-25 17:11 ` Conor Dooley 2024-04-25 17:11 ` Conor Dooley 2024-04-22 14:04 ` Rob Herring 2024-04-22 14:04 ` Rob Herring 2024-04-18 16:32 ` [PATCH v2 2/7] iommu/riscv: Add RISC-V IOMMU platform device driver Tomasz Jeznach 2024-04-18 16:32 ` Tomasz Jeznach 2024-04-18 21:22 ` Robin Murphy 2024-04-18 21:22 ` Robin Murphy 2024-04-24 21:59 ` Tomasz Jeznach 2024-04-24 21:59 ` Tomasz Jeznach 2024-04-25 11:23 ` Robin Murphy 2024-04-25 11:23 ` Robin Murphy 2024-04-18 16:32 ` [PATCH v2 3/7] iommu/riscv: Add RISC-V IOMMU PCIe " Tomasz Jeznach 2024-04-18 16:32 ` Tomasz Jeznach 2024-04-18 22:07 ` Robin Murphy 2024-04-18 22:07 ` Robin Murphy 2024-04-18 16:32 ` [PATCH v2 4/7] iommu/riscv: Enable IOMMU registration and device probe Tomasz Jeznach 2024-04-18 16:32 ` Tomasz Jeznach 2024-04-18 16:32 ` [PATCH v2 5/7] iommu/riscv: Device directory management Tomasz Jeznach 2024-04-18 16:32 ` Tomasz Jeznach 2024-04-19 12:40 ` Jason Gunthorpe 2024-04-19 12:40 ` Jason Gunthorpe 2024-04-24 23:01 ` Tomasz Jeznach 2024-04-24 23:01 ` Tomasz Jeznach 2024-04-24 23:07 ` Jason Gunthorpe 2024-04-24 23:07 ` Jason Gunthorpe 2024-04-22 5:11 ` Baolu Lu 2024-04-22 5:11 ` Baolu Lu 2024-04-24 23:07 ` Tomasz Jeznach 2024-04-24 23:07 ` Tomasz Jeznach 2024-04-18 16:32 ` [PATCH v2 6/7] iommu/riscv: Command and fault queue support Tomasz Jeznach 2024-04-18 16:32 ` Tomasz Jeznach 2024-04-18 16:32 ` [PATCH v2 7/7] iommu/riscv: Paging domain support Tomasz Jeznach 2024-04-18 16:32 ` Tomasz Jeznach 2024-04-19 12:56 ` Jason Gunthorpe 2024-04-19 12:56 ` Jason Gunthorpe 2024-04-22 7:40 ` Baolu Lu 2024-04-22 7:40 ` Baolu Lu 2024-04-24 23:30 ` Tomasz Jeznach [this message] 2024-04-24 23:30 ` Tomasz Jeznach 2024-04-24 23:39 ` Jason Gunthorpe 2024-04-24 23:39 ` Jason Gunthorpe 2024-04-24 23:54 ` Tomasz Jeznach 2024-04-24 23:54 ` Tomasz Jeznach 2024-04-25 0:48 ` Jason Gunthorpe 2024-04-25 0:48 ` Jason Gunthorpe 2024-04-22 5:21 ` Baolu Lu 2024-04-22 5:21 ` Baolu Lu 2024-04-22 19:30 ` Jason Gunthorpe 2024-04-22 19:30 ` Jason Gunthorpe 2024-04-23 17:00 ` Andrew Jones 2024-04-23 17:00 ` Andrew Jones
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAH2o1u5+XD9YN=gdMVtfkyhKoKha0UpwKgOVbCAwOQa+saPfRw@mail.gmail.com' \ --to=tjeznach@rivosinc.com \ --cc=aou@eecs.berkeley.edu \ --cc=apatel@ventanamicro.com \ --cc=conor+dt@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=iommu@lists.linux.dev \ --cc=jgg@ziepe.ca \ --cc=joro@8bytes.org \ --cc=krzk+dt@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=linux@rivosinc.com \ --cc=mick@ics.forth.gr \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=robh+dt@kernel.org \ --cc=robin.murphy@arm.com \ --cc=seb@rivosinc.com \ --cc=sunilvl@ventanamicro.com \ --cc=will@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.