From: Ingo Molnar <mingo@kernel.org>
To: Rik van Riel <riel@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Olu Ogunbowale <Olu.Ogunbowale@imgtec.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Michel Lespinasse <walken@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Russell King <linux@arm.linux.org.uk>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Mundt <lethal@linux-sh.org>,
"David S. Miller" <davem@davemloft.net>,
Chris Metcalf <cmetcalf@tilera.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] mm: Export symbols unmapped_area() & unmapped_area_topdown()
Date: Thu, 17 Mar 2016 08:24:56 +0100 [thread overview]
Message-ID: <20160317072456.GA2522@gmail.com> (raw)
In-Reply-To: <1458162041.14723.32.camel@redhat.com>
* Rik van Riel <riel@redhat.com> wrote:
> On Wed, 2016-03-16 at 13:36 -0700, Christoph Hellwig wrote:
> > On Wed, Mar 16, 2016 at 05:10:34PM +0000, Olu Ogunbowale wrote:
> > >
> > > From: Olujide Ogunbowale <Olu.Ogunbowale@imgtec.com>
> > >
> > > Export the memory management functions, unmapped_area() &
> > > unmapped_area_topdown(), as GPL symbols; this allows the kernel to
> > > better support process address space mirroring on both CPU and
> > > device
> > > for out-of-tree drivers by allowing the use of vm_unmapped_area()
> > > in a
> > > driver's file operation get_unmapped_area().
> > No new exports without in-tree drivers. How about you get started
> > to get your drives into the tree first?
>
> The drivers appear to require the HMM framework though,
> which people are also reluctant to merge without the
> drivers.
>
> How do we get past this chicken & egg situation?
Submit the export together with the drivers for review and Cc: VM folks - it all
looks pretty small on the VM side.
Thanks,
Ingo
--
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>
next prev parent reply other threads:[~2016-03-17 7:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 17:10 Mirroring process address space on device Olu Ogunbowale
2016-03-16 17:10 ` [PATCH] mm: Export symbols unmapped_area() & unmapped_area_topdown() Olu Ogunbowale
2016-03-16 20:36 ` Christoph Hellwig
2016-03-16 21:00 ` Rik van Riel
2016-03-17 7:24 ` Ingo Molnar [this message]
2016-03-17 14:37 ` Jerome Glisse
2016-03-17 15:38 ` Oded Gabbay
2016-03-17 15:46 ` Olu Ogunbowale
2016-03-17 17:03 ` Jerome Glisse
2016-03-17 17:42 ` Olu Ogunbowale
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=20160317072456.GA2522@gmail.com \
--to=mingo@kernel.org \
--cc=Olu.Ogunbowale@imgtec.com \
--cc=akpm@linux-foundation.org \
--cc=cmetcalf@tilera.com \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=hughd@google.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@elte.hu \
--cc=ralf@linux-mips.org \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=walken@google.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).