linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jerome Glisse <j.glisse@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Kyungmin Park <kmpark@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	vdumpa@nvidia.com, hdoyu@nvidia.com, konrad.wilk@oracle.com
Subject: Re: Linux 3.4-rc1
Date: Tue, 3 Apr 2012 10:58:36 -0400	[thread overview]
Message-ID: <CAH3drwaGz0m_hnZqj41yAFXVLc++ZFBYR4G-ydUa6=NrkS78kQ@mail.gmail.com> (raw)
In-Reply-To: <201204030907.29306.arnd@arndb.de>

On Tue, Apr 3, 2012 at 5:07 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Tuesday 03 April 2012, Kyungmin Park wrote:
>> >
>> >  - DMA-mapping framework. The tree now has a few more acks from
>> > people, and it's largely in the same situation as HSI is: I'll
>> > probably pull, but I really wanted the users who are impacted to
>> > actually talk to me about it.
>> >
>> Hi,
>>
>> Now Marek and Nvidia persons are used it for DMA mapping based IOMMU.
>>
>> Are there other person who help to merge it?
>> (+CC related persons).
>
> I can give a little more background information.
>
> We used to have separate implementations of dma_map_ops for each
> architecture that had the need to abstract dma_alloc_coherent
> and dma_map_* across both IOMMU and linear (virt_to_bus style)
> mappings and/or swiotlb. Those dma_map_ops imlpementations were
> already merged before the start of the git history and subsequently
> got used on powerpc, ia64, x86_64, sparc, alpha, mips, unicore32
> and hexagon, roughly in that order.
>
> We are seeing lots of IOMMUs come up on ARM now, but unfortunately
> the existing dma_map_ops do not cover the need on ARM to have
> two different kind of coherent memory (write-combine and not
> write-combine) that we have traditionally abstracted using
> the dma_alloc_coherent and dma_alloc_writecombine functions on both
> arm and avr32. In order to support IOMMUs on ARM using the same
> API as everyone else, I've asked Marek to use dma_map_ops on
> ARM, which requires slightly extending the include/linux/dma-mapping.h
> interfaces so they cover this variation.
>
> The actually interesting work to implement a better abstraction for
> IOMMUs, building the dma-mapping.h API on top of the iommu.h API
> in an architecture independent way has also been implemented but
> requires these changes as a prerequisite.
>
>        Arnd

Out of curiosity where is the IOMMU abstraction work being discussed ?
Worked on ? I would like similar things on x86 platform and i spend
sometimes thinking on it in the past. Would like to make sure this
could also fit our need.

Cheers,
Jerome

  reply	other threads:[~2012-04-03 14:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-31 23:58 Linux 3.4-rc1 Linus Torvalds
2012-04-01  0:09 ` Christoph Hellwig
2012-04-01  1:46 ` Shea Levy
2012-04-01  3:11   ` Linus Torvalds
2012-04-01  1:48 ` Shea Levy
2012-04-01  2:07   ` Shea Levy
2012-04-01  8:34 ` Ingo Molnar
2012-04-01 12:03 ` Stephen Rothwell
2012-04-01 19:19   ` David Miller
2012-04-01 13:14 ` linux-next stats (Was: Linux 3.4-rc1) Stephen Rothwell
2012-04-01 15:34 ` Linux 3.4-rc1 Rob Clark
2012-04-02  3:40   ` Kyungmin Park
2012-04-02  8:41     ` Daniel Vetter
2012-04-04 12:24       ` Subash Patel
2012-04-04 12:33         ` Anca Emanuel
2012-04-05  7:41           ` Marek Szyprowski
2012-04-02 12:31   ` Alex Deucher
2012-04-02  9:15 ` Artem Bityutskiy
2012-04-02  9:20   ` Shubhrajyoti Datta
2012-04-02 15:48 ` Linus Walleij
2012-04-02 20:30 ` Carlos Chinea
2012-04-03  2:57 ` Kyungmin Park
2012-04-03  3:57   ` Linus Torvalds
2012-04-03  6:29     ` Hiroshi Doyu
2012-04-03  9:07   ` Arnd Bergmann
2012-04-03 14:58     ` Jerome Glisse [this message]
2012-04-03 15:35       ` Arnd Bergmann
2012-04-03 19:26     ` Krishna Reddy
2012-04-04 12:10       ` Anca Emanuel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH3drwaGz0m_hnZqj41yAFXVLc++ZFBYR4G-ydUa6=NrkS78kQ@mail.gmail.com' \
    --to=j.glisse@gmail.com \
    --cc=arnd@arndb.de \
    --cc=hdoyu@nvidia.com \
    --cc=kmpark@infradead.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vdumpa@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).