linux-kernel - RE: [PATCHv2 2/4] mm: cma: Contiguous Memory Allocator added

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <003f01cb2d92$20819730$6184c590$%szyprowski@samsung.com>
Date:	Tue, 27 Jul 2010 15:46:26 +0200
From:	Marek Szyprowski <m.szyprowski@...sung.com>
To:	'Jonathan Corbet' <corbet@....net>
Cc:	'Russell King - ARM Linux' <linux@....linux.org.uk>,
	Michal Nazarewicz <m.nazarewicz@...sung.com>,
	linux-mm@...ck.org, 'Daniel Walker' <dwalker@...eaurora.org>,
	Pawel Osciak <p.osciak@...sung.com>,
	'Mark Brown' <broonie@...nsource.wolfsonmicro.com>,
	linux-kernel@...r.kernel.org, 'Hiremath Vaibhav' <hvaibhav@...com>,
	'FUJITA Tomonori' <fujita.tomonori@....ntt.co.jp>,
	'Kyungmin Park' <kyungmin.park@...sung.com>,
	'Zach Pfeffer' <zpfeffer@...eaurora.org>,
	linux-media@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: RE: [PATCHv2 2/4] mm: cma: Contiguous Memory Allocator added

Hello,

On Tuesday, July 27, 2010 2:59 PM Jonathan Corbet wrote:

> On Tue, 27 Jul 2010 14:45:58 +0200
> Marek Szyprowski <m.szyprowski@...sung.com> wrote:
> 
> > > How does one obtain the CPU address of this memory in order for the CPU
> > > to access it?
> >
> > Right, we did not cover such case. In CMA approach we tried to separate
> > memory allocation from the memory mapping into user/kernel space. Mapping
> > a buffer is much more complicated process that cannot be handled in a
> > generic way, so we decided to leave this for the device drivers. Usually
> > video processing devices also don't need in-kernel mapping for such
> > buffers at all.
> 
> Still...that *is* why I suggested an interface which would return both
> the DMA address and a kernel-space virtual address, just like the DMA
> API does...  Either that, or just return the void * kernel address and
> let drivers do the DMA mapping themselves.  Returning only the
> dma_addr_t address will make the interface difficult to use in many
> situations.

As I said, drivers usually don't need in-kernel mapping for video buffers.
Is there really a need for creating such mapping?

Best regards
--
Marek Szyprowski
Samsung Poland R&D Center


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/