From: Baruch Siach <baruch@tkos.co.il>
To: Gioh Kim <gioh.kim@lge.com>
Cc: Russell King <linux@arm.linux.org.uk>,
linux-mm@kvack.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
HyoJun Im <hyojun.im@lge.com>
Subject: Re: ARM: mm: Could I change module space size or place modules in vmalloc area?
Date: Thu, 2 Jan 2014 12:13:59 +0200 [thread overview]
Message-ID: <20140102101359.GU6589@tarshish> (raw)
In-Reply-To: <002001cf07a1$fd4bdc10$f7e39430$@lge.com>
Hi Gioh,
On Thu, Jan 02, 2014 at 07:04:13PM +0900, Gioh Kim wrote:
> I run out of module space because I have several big driver modules.
> I know I can strip the modules to decrease size but I need debug info now.
Are you sure you need the debug info in kernel memory? I don't think the
kernel is actually able to parse DWARF. You can load stripped binaries into
the kernel, and still use the debug info with whatever tool you have.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
--
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:[~2014-01-02 10:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 10:04 ARM: mm: Could I change module space size or place modules in vmalloc area? Gioh Kim
2014-01-02 10:13 ` Baruch Siach [this message]
2014-01-03 0:39 ` Gioh Kim
2014-01-03 0:47 ` Russell King - ARM Linux
2014-01-03 2:52 ` Gioh Kim
2014-04-26 2:12 ` Jianguo Wu
2014-04-29 11:19 ` Will Deacon
2014-04-29 11:35 ` Arnd Bergmann
2014-04-29 12:40 ` Will Deacon
2014-01-03 12:10 ` Arnd Bergmann
2014-01-03 12:22 ` Russell King - ARM Linux
2014-01-03 13:23 ` Arnd Bergmann
2014-03-12 6:38 ` Gioh Kim
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=20140102101359.GU6589@tarshish \
--to=baruch@tkos.co.il \
--cc=gioh.kim@lge.com \
--cc=hyojun.im@lge.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
/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).