From: Adrian Bunk <bunk@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>, lguest <lguest@ozlabs.org>,
linux-kernel@vger.kernel.org,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: [PATCH 1/2] Export get_user_pages_fast
Date: Wed, 30 Jul 2008 20:39:44 +0300 [thread overview]
Message-ID: <20080730173944.GC28604@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <20080730102817.c74a9e33.akpm@linux-foundation.org>
On Wed, Jul 30, 2008 at 10:28:17AM -0700, Andrew Morton wrote:
> On Wed, 30 Jul 2008 20:18:45 +0300 Adrian Bunk <bunk@kernel.org> wrote:
>
> > > > The export would still only be available on x86 since no other arch
> > > > would define CONFIG_HAVE_GET_USER_PAGES_FAST.
> > > >
> > >
> > > That's presently true in Linus mainline. The powerpc implementation is
> > > in -mm, but apprarently needs a bit more work.
> >
> > I still don't get the advantage of your suggestion.
> >
> > With the powerpc implementation included your suggestion doesn't change
> > the fact that the export is available only on x86 and powerpc, and if a
> > driver author mistakenly uses it and only tests it's driver on x86 it
> > will still break on architectures other than x86 or powerpc.
>
> On non-CONFIG_HAVE_GET_USER_PAGES_FAST architectures a
> get_user_pages_fast() call will in fact call get_user_pages().
>
> On CONFIG_HAVE_GET_USER_PAGES_FAST architectures, get_user_pages_fast()
> is a real function. All architectures which implement that function
> should export it to modules. Hence it should be exported from within
> generic code.
Are we talking at cross purposes?
I thought you were talking an error due to a missing function.
If you think about an error where the function is present but only the
EXPORT_SYMBOL is missing then I get your point (although I do not
consider it a huge problem).
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-07-30 17:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 4:38 Rusty Russell
2008-07-30 4:39 ` [PATCH 2/2] lguest: use get_user_pages_fast() instead of get_user_pages() Rusty Russell
2008-07-30 5:30 ` Nick Piggin
2008-07-30 6:53 ` Rusty Russell
2008-07-30 5:23 ` [PATCH 1/2] Export get_user_pages_fast Nick Piggin
2008-07-30 10:35 ` Andrew Morton
2008-07-30 15:47 ` Adrian Bunk
2008-07-30 17:03 ` Andrew Morton
2008-07-30 17:09 ` Adrian Bunk
2008-07-30 17:14 ` Andrew Morton
2008-07-30 17:18 ` Adrian Bunk
2008-07-30 17:28 ` Andrew Morton
2008-07-30 17:39 ` Adrian Bunk [this message]
2008-07-30 17:50 ` Andrew Morton
2008-07-30 17:23 ` Avi Kivity
2008-07-30 17:29 ` Andrew Morton
2008-07-31 6:43 ` Avi Kivity
2008-07-31 7:02 ` Andrew Morton
2008-07-31 8:10 ` Nick Piggin
2008-07-31 8:21 ` Andrew Morton
2008-07-31 8:32 ` Benjamin Herrenschmidt
2008-07-31 8:48 ` Nick Piggin
2008-07-31 8:52 ` Benjamin Herrenschmidt
2008-07-31 8:56 ` Nick Piggin
2008-08-05 5:47 ` Rusty Russell
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=20080730173944.GC28604@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®