[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43426798-44df-c2c7-1f46-0b79201cb620@sifive.com>
Date: Mon, 11 Jul 2022 11:42:43 +0100
From: Ben Dooks <ben.dooks@...ive.com>
To: Christoph Hellwig <hch@....de>
Cc: Robin Murphy <robin.murphy@....com>, linux-kernel@...r.kernel.org,
iommu@...ts.linux.dev, iommu@...ts.linux-foundation.org,
Sudip Mukherjee <sudip.mukherjee@...ive.com>,
Jude Onyenegecha <jude.onyenegecha@...ive.com>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [PATCH] swiotlb: ensure io_tlb_default_mem spinlock always
initialised
On 11/07/2022 11:39, Christoph Hellwig wrote:
> On Mon, Jul 11, 2022 at 11:24:51AM +0100, Ben Dooks wrote:
>> On 11/07/2022 11:21, Christoph Hellwig wrote:
>>> On Mon, Jul 11, 2022 at 11:07:17AM +0100, Robin Murphy wrote:
>>>> If none of your peripherals should need SWIOTLB, then the fact that
>>>> you're ending up in swiotlb_map() at all is a clear sign that
>>>> something's wrong. Most likely someone's forgotten to set their DMA
>>>> masks correctly.
>>>
>>> Yes.
>>
>> Possibly, we had at least one driver which attempted to set a 32 bit
>> DMA mask which had to be removed as the DMA layer accepts this but
>> since there is no DMA32 memory the allocator then just fails.
>>
>> I expect the above may need to be a separate discussion(s) of how to
>> default the DMA mask and how to stop the implicit acceptance of setting
>> a 32-bit DMA mask.
>
> No. Linux simply assumes you can do 32-bit DMA and this won't
> change. So we'll need to fix your platform to support swiotlb
> eventually.
Ok, is there any examples currently in the kernel that have no memory
in the DMA32 zone that do use swiotlb?
Powered by blists - more mailing lists