Re: [PATCH] iommu/iova: Free all CPU rcache for retry when iova alloc failure

2022-03-03 Thread yf.wang--- via iommu
On Fri, 2022-03-04 at 12:46 +0800, yf.w...@mediatek.com wrote: > From: Yunfei Wang > > In alloc_iova_fast function, if an iova alloc request fail, > it will free the iova ranges present in the percpu iova > rcaches and free global iova rcache and then retry, but > flushing CPU iova rcaches only f

Re: virtio-gpu dedicated heap

2022-03-03 Thread Michael S. Tsirkin
$ ./scripts/get_maintainer.pl -f ./drivers/gpu/drm/virtio/ David Airlie (maintainer:VIRTIO GPU DRIVER) Gerd Hoffmann (maintainer:VIRTIO GPU DRIVER) Daniel Vetter (maintainer:DRM DRIVERS) dri-de...@lists.freedesktop.org (open list:VIRTIO GPU DRIVER) virtualizat...@lists.linux-foundation.org (ope

[PATCH] iommu/iova: Free all CPU rcache for retry when iova alloc failure

2022-03-03 Thread yf.wang--- via iommu
From: Yunfei Wang In alloc_iova_fast function, if an iova alloc request fail, it will free the iova ranges present in the percpu iova rcaches and free global iova rcache and then retry, but flushing CPU iova rcaches only for each online CPU, which will cause incomplete rcache cleaning, and iova r

Re: [PATCH] iommu/iova: Improve 32-bit free space estimate

2022-03-03 Thread Miles Chen via iommu
Hi Robin, > For various reasons based on the allocator behaviour and typical > use-cases at the time, when the max32_alloc_size optimisation was > introduced it seemed reasonable to couple the reset of the tracked > size to the update of cached32_node upon freeing a relevant IOVA. > However, since

Re: [PATCH] iommu/iova: Improve 32-bit free space estimate

2022-03-03 Thread Miles Chen via iommu
> For various reasons based on the allocator behaviour and typical > use-cases at the time, when the max32_alloc_size optimisation was > introduced it seemed reasonable to couple the reset of the tracked > size to the update of cached32_node upon freeing a relevant IOVA. > However, since subsequent

Re: [PATCH 11/12] swiotlb: merge swiotlb-xen initialization into swiotlb

2022-03-03 Thread Stefano Stabellini
On Thu, 3 Mar 2022, Christoph Hellwig wrote: > On Wed, Mar 02, 2022 at 05:25:10PM -0800, Stefano Stabellini wrote: > > Thinking more about it we actually need to drop the xen_initial_domain() > > check otherwise some cases won't be functional (Dom0 not 1:1 mapped, or > > DomU 1:1 mapped). > > Hmm,

Re: [PATCH 11/12] swiotlb: merge swiotlb-xen initialization into swiotlb

2022-03-03 Thread Boris Ostrovsky
On 3/3/22 5:57 AM, Christoph Hellwig wrote: On Wed, Mar 02, 2022 at 08:15:03AM -0500, Boris Ostrovsky wrote: Not for me, I fail to boot with [ 52.202000] bnxt_en :31:00.0: swiotlb buffer is full (sz: 256 bytes), total 0 (slots), used 0 (slots) (this is iscsi root so I need the NIC).

Re: [PATCH 06/12] MIPS/octeon: use swiotlb_init instead of open coding it

2022-03-03 Thread Thomas Bogendoerfer
On Tue, Mar 01, 2022 at 12:53:05PM +0200, Christoph Hellwig wrote: > Use the generic swiotlb initialization helper instead of open coding it. > > Signed-off-by: Christoph Hellwig > --- > arch/mips/cavium-octeon/dma-octeon.c | 15 ++- > arch/mips/pci/pci-octeon.c | 2 +- >

[PATCH] iommu/iova: Improve 32-bit free space estimate

2022-03-03 Thread Robin Murphy
For various reasons based on the allocator behaviour and typical use-cases at the time, when the max32_alloc_size optimisation was introduced it seemed reasonable to couple the reset of the tracked size to the update of cached32_node upon freeing a relevant IOVA. However, since subsequent optimisat

Re: [PATCH v2] iommu/iova: Reset max32_alloc_size after cleaning

2022-03-03 Thread Robin Murphy
On 2022-03-03 03:43, yf.w...@mediatek.com wrote: On Thu, 2022-03-03 at 07:52 +0800, Miles Chen wrote: Thanks for your explanation. YF showed me some numbers yesterday and maybe we can have a further discussion in that test case. (It looks like that some iovas are freed but their pfn_lo(s) are l

RE: [PATCH v8 00/11] ACPI/IORT: Support for IORT RMR node

2022-03-03 Thread Shameerali Kolothum Thodi via iommu
> -Original Message- > From: Steven Price [mailto:steven.pr...@arm.com] > Sent: 03 March 2022 10:38 > To: Shameerali Kolothum Thodi ; > linux-arm-ker...@lists.infradead.org; linux-a...@vger.kernel.org; > iommu@lists.linux-foundation.org > Cc: Linuxarm ; lorenzo.pieral...@arm.com; > j...@

Re: [PATCH v2] iommu/iova: Reset max32_alloc_size after cleaning

2022-03-03 Thread yf.wang--- via iommu
From: yf.w...@mediatek.com On Thu, 2022-03-03 at 07:52 +0800, Miles Chen wrote: > Thanks for your explanation. > > YF showed me some numbers yesterday and maybe we can have a further > discussion in that test case. (It looks like that some iovas are > freed but > their pfn_lo(s) are less than ca

Re: [PATCH] kernel: dma-debug: fix return value of __setup handlers

2022-03-03 Thread Christoph Hellwig
Thanks, applied to the dma-mapping tree. ___ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu

Re: [PATCH 11/12] swiotlb: merge swiotlb-xen initialization into swiotlb

2022-03-03 Thread Christoph Hellwig
On Wed, Mar 02, 2022 at 05:25:10PM -0800, Stefano Stabellini wrote: > Thinking more about it we actually need to drop the xen_initial_domain() > check otherwise some cases won't be functional (Dom0 not 1:1 mapped, or > DomU 1:1 mapped). Hmm, but that would be the case even before this series, righ

Re: [PATCH 11/12] swiotlb: merge swiotlb-xen initialization into swiotlb

2022-03-03 Thread Christoph Hellwig
On Wed, Mar 02, 2022 at 08:15:03AM -0500, Boris Ostrovsky wrote: > Not for me, I fail to boot with > > [ 52.202000] bnxt_en :31:00.0: swiotlb buffer is full (sz: 256 bytes), > total 0 (slots), used 0 (slots) > > (this is iscsi root so I need the NIC). > > > I bisected it to "x86: remove the

Re: [PATCH v8 00/11] ACPI/IORT: Support for IORT RMR node

2022-03-03 Thread Steven Price
On 21/02/2022 15:43, Shameer Kolothum wrote: > Hi, > > Since we now have an updated verion[0] of IORT spec(E.d) which > addresses the memory attributes issues discussed here [1], > this series now make use of it. > > The pull request for ACPICA E.d related changes are already > raised and can be