From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Hans J. Koch" <hjk@hansjkoch.de>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
linux-mm@kvack.org
Subject: Re: [PATCH v2 1/2] uio: provide vm access to UIO_MEM_PHYS maps
Date: Tue, 30 Jul 2013 07:38:57 -0700 [thread overview]
Message-ID: <20130730143857.GA29376@kroah.com> (raw)
In-Reply-To: <20130730143237.GU1754@pengutronix.de>
On Tue, Jul 30, 2013 at 04:32:37PM +0200, Uwe Kleine-Konig wrote:
> Hello Greg,
>
> On Tue, Jul 30, 2013 at 06:49:50AM -0700, Greg Kroah-Hartman wrote:
> > On Tue, Jul 30, 2013 at 09:52:39AM +0200, Uwe Kleine-Konig wrote:
> > > [expanding Cc: to also include akpm and linux-mm]
> > >
> > > Hello,
> > >
> > > On Mon, Jul 29, 2013 at 01:09:14PM -0700, Greg Kroah-Hartman wrote:
> > > > On Sun, Jul 28, 2013 at 12:09:37AM +0200, Uwe Kleine-Konig wrote:
> > > > > This makes it possible to let gdb access mappings of the process that is
> > > > > being debugged.
> > > > >
> > > > > uio_mmap_logical was moved and uio_vm_ops renamed to group related code
> > > > > and differentiate to new stuff.
> > > > >
> > > > > Signed-off-by: Uwe Kleine-Konig <u.kleine-koenig@pengutronix.de>
> > > > > ---
> > > > > Changes since v1:
> > > > > - only use generic_access_phys ifdef CONFIG_HAVE_IOREMAP_PROT
> > > > > - fix all users of renamed struct
> > > >
> > > > I still get a build error with this patch:
> > > >
> > > > MODPOST 384 modules
> > > > ERROR: "generic_access_phys" [drivers/uio/uio.ko] undefined!
> > > >
> > > > So something isn't quite right.
> > > Ah, you built as a module and generic_access_phys isn't exported. The
> > > other users of generic_access_phys (arch/x86/pci/i386.c and
> > > drivers/char/mem.c) can only be builtin.
> > >
> > > So the IMHO best option is to add an EXPORT_SYMBOL(generic_access_phys)
> > > to mm/memory.c.
> >
> > EXPORT_SYMBOL_GPL() perhaps?
> Yeah, that would work just fine, too. Who takes care for mm/memory.c,
> Andrew? Should I send a separate patch or is it ok to do it in the patch
> making use of it and let it go in via Greg?
I can take it, in a patch before this one, if I get the acks from Andrew
and anyone else who "owns" that file (use get_maintainer.pl to determine
the proper people please.)
> > And why all of a sudden does the uio driver need this change? It is
> > working just fine right now without it, right?
> Yeah it works. But if you gdb your userspace driver, gdb cannot access
> the mappings without my patch.
Ah, but who needs to use a debugger... :)
thanks,
greg k-h
--
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:[~2013-07-30 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130727214911.GK1754@pengutronix.de>
[not found] ` <1374962978-1860-1-git-send-email-u.kleine-koenig@pengutronix.de>
[not found] ` <20130729200914.GA6146@kroah.com>
2013-07-30 7:52 ` Uwe Kleine-König
2013-07-30 13:49 ` Greg Kroah-Hartman
2013-07-30 14:32 ` Uwe Kleine-König
2013-07-30 14:38 ` Greg Kroah-Hartman [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=20130730143857.GA29376@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=hjk@hansjkoch.de \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=u.kleine-koenig@pengutronix.de \
/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