[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221116154507.GB18491@lst.de>
Date: Wed, 16 Nov 2022 16:45:07 +0100
From: Christoph Hellwig <hch@....de>
To: Robin Murphy <robin.murphy@....com>
Cc: Dean Luick <dean.luick@...nelisnetworks.com>,
Christoph Hellwig <hch@....de>,
Dennis Dalessandro <dennis.dalessandro@...nelisnetworks.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Alexandra Winter <wintera@...ux.ibm.com>,
Wenjia Zhang <wenjia@...ux.ibm.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Russell King <linux@...linux.org.uk>,
linux-arm-kernel@...ts.infradead.org, linux-rdma@...r.kernel.org,
iommu@...ts.linux.dev, linux-media@...r.kernel.org,
netdev@...r.kernel.org, linux-s390@...r.kernel.org,
alsa-devel@...a-project.org
Subject: Re: [PATCH 2/7] RDMA/hfi1: don't pass bogus GFP_ flags to
dma_alloc_coherent
On Wed, Nov 16, 2022 at 03:15:10PM +0000, Robin Murphy wrote:
> Coherent DMA buffers are allocated by a kernel driver or subsystem for the
> use of a device managed by that driver or subsystem, and thus they
> fundamentally belong to the kernel as proxy for the device. Any coherent
> DMA buffer may be mapped to userspace with the dma_mmap_*() interfaces, but
> they're never a "userspace allocation" in that sense.
Exactly. I could not find a place to map the buffers to userspace,
so if it does that without using the proper interfaces we need to fix
that as well. Dean, can you point me to the mmap code?
Powered by blists - more mailing lists