search for: dma_generic_alloc_coherent

On Thu, 2018-05-10 at 12:28 +0200, Mike Galbraith wrote: > On Thu, 2018-05-10 at 11:10 +0200, Mike Galbraith wrote: > > Greetings, > > > > When box is earning its keep, nouveau/swiotlb grumble.. a LOT. The > > below is from master.today. > > > > [12594.640959] nouveau 0000:01:00.0: swiotlb buffer is full (sz: 2097152 bytes) > > [12594.693000] nouveau

...7]? [<ffffffff81188810>] warn_alloc_failed+0x110/0x180 [Mon Oct 23 16:43:32 2017]? [<ffffffff8169fd8a>] __alloc_pages_slowpath+0x6b6/0x724 [Mon Oct 23 16:43:32 2017]? [<ffffffff8118cd85>] __alloc_pages_nodemask+0x405/0x420 [Mon Oct 23 16:43:32 2017]? [<ffffffff81030f8f>] dma_generic_alloc_coherent+0x8f/0x140 [Mon Oct 23 16:43:32 2017]? [<ffffffff81065c0d>] gart_alloc_coherent+0x2d/0x40 [Mon Oct 23 16:43:32 2017]? [<ffffffffc012e4d3>] mlx4_buf_direct_alloc.isra.6+0xd3/0x1a0 [mlx4_core] [Mon Oct 23 16:43:32 2017]? [<ffffffffc012e76b>] mlx4_buf_alloc+0x1cb/0x240 [mlx4_core]...

...a_addr_t dma_mask = dma_alloc_coherent_mask(dev, gfp); if (dma_mask <= DMA_BIT_MASK(24)) gfp |= GFP_DMA; diff --git a/arch/x86/kernel/pci-dma.c b/arch/x86/kernel/pci-dma.c index 872079a..a061f7b 100644 --- a/arch/x86/kernel/pci-dma.c +++ b/arch/x86/kernel/pci-dma.c @@ -90,7 +90,7 @@ void *dma_generic_alloc_coherent(struct device *dev, size_t size, dma_addr_t *dma_addr, gfp_t flag, struct dma_attrs *attrs) { - unsigned long dma_mask; + dma_addr_t dma_mask; struct page *page; unsigned int count = PAGE_ALIGN(size) >> PAGE_SHIFT; dma_addr_t addr; diff --git a/drivers/xen/swiotlb-xen.c b/d...

Hi, This is third approach (complete this time) for replacing struct dma_attrs with unsigned long. The main patch (2/45) doing the change is split into many subpatches for easier review (3-43). They should be squashed together when applying. *Important:* Patchset is *only* build tested on allyesconfigs: ARM, ARM64, i386, x86_64 and powerpc. Please provide reviewes and tests for other

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine