From: Dan Williams <dan.j.williams@gmail.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 1/1] mm: EXPORT_SYMBOL_GPL(find_vm_area);
Date: Fri, 15 Jan 2016 08:59:01 -0800 [thread overview]
Message-ID: <CAA9_cmeneVE_VvCz_6=oOL6+_ZzFscv9P9b9nO8GkR=QpwgW_g@mail.gmail.com> (raw)
In-Reply-To: <5693A77E.4020809@linux.intel.com>
On Mon, Jan 11, 2016 at 5:00 AM, Sakari Ailus
<sakari.ailus@linux.intel.com> wrote:
> Hi Andrew,
>
> Andrew Morton wrote:
>> On Wed, 11 Nov 2015 15:06:24 +0200 Sakari Ailus <sakari.ailus@linux.intel.com> wrote:
>>
>>> find_vm_area() is needed in implementing the DMA mapping API as a module.
>>> Device specific IOMMUs with associated DMA mapping implementations should be
>>> buildable as modules.
>>>
>>> ...
>>>
>>> --- a/mm/vmalloc.c
>>> +++ b/mm/vmalloc.c
>>> @@ -1416,6 +1416,7 @@ struct vm_struct *find_vm_area(const void *addr)
>>>
>>> return NULL;
>>> }
>>> +EXPORT_SYMBOL_GPL(find_vm_area);
>>
>> Confused. Who is setting CONFIG_HAS_DMA=m?
>>
>
> Apologies for the late reply --- CONFIG_HAS_DMA isn't configured as a
> module, but some devices are not DMA coherent even on x86. The existing
> x86 DMA mapping implementation doesn't quite work for those at the
> moment, and nothing prevents using another one (and as a module, in
> which case this patch is required).
Why not teach the DMA mapping api how to do cache management for such
devices? Why would you need find_vm_area() exported?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-01-15 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 13:06 Sakari Ailus
2015-12-03 0:25 ` Andrew Morton
2016-01-11 13:00 ` Sakari Ailus
2016-01-11 21:31 ` Andrew Morton
2016-01-15 16:59 ` Dan Williams [this message]
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='CAA9_cmeneVE_VvCz_6=oOL6+_ZzFscv9P9b9nO8GkR=QpwgW_g@mail.gmail.com' \
--to=dan.j.williams@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=sakari.ailus@linux.intel.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