From: Vineet Gupta <vgupta@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Stripping kernel modules for ARC
Date: Wed, 14 Sep 2016 12:18:32 -0700 [thread overview]
Message-ID: <d1ed5472-3500-45fc-eb0f-bdd2d6afb441@synopsys.com> (raw)
In-Reply-To: <1473852437.3766.15.camel@synopsys.com>
On 09/14/2016 04:29 AM, Alexey Brodkin wrote:
> Hello,
>
> This is a follow-up of discussion started here
> https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/issues/86
>
> The problem in hand is kernel stack unwinding on ARC historically was done
> with use of debug_frame instead of more common eh_frame.
Just for the record, I will be switching kernel unwinder to .eh_frame anyways -
it's just taking longer than I hoped to. So there is no need to do anything
special for .debug_frame - not as of now.
The question is if we enable BR2_STRIP_NONE=y in buildroot, what strip is run
on kernel / modules. And also does it strip build and target/install modules
differently such that target ones are stripped, but not those for debugging etc.
-Vineet
> And if stripping
> of target binaries is enabled in Buildroot invocation of strip with
> "--strip-unneeded" gets rid of debug_frame section effectively making
> kernel unwinder helpless.
>
> I'm wondering what would be a better way to strip modules on ARC in Buildroot?
>
> I may see at least following solutions:
> 1. Empty STRIP_STRIP_UNNEEDED or even KSTRIPCMD for ARC
> This together with http://lists.infradead.org/pipermail/linux-snps-arc/2016-September/001483.html
> will still produce pretty compact .ko files on target
> 2. Use objdump instead of strip with explicitly mentioned sections to keep or remove
>
> Any thoughts are much appreciated.
>
> -Alexey
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2016-09-14 19:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 11:29 [Buildroot] Stripping kernel modules for ARC Alexey Brodkin
2016-09-14 19:00 ` Arnout Vandecappelle
2016-09-14 19:18 ` Vineet Gupta [this message]
2016-09-14 19:57 ` Peter Korsgaard
2016-09-14 20:00 ` Alexey Brodkin
2016-09-14 20:18 ` Vineet Gupta
2016-09-14 20:21 ` Peter Korsgaard
[not found] ` <CAE2F3rCBwysRFrMf4CD6uLevvfw0TNaZGyptOj6MLDQvGPPwFg@mail.gmail.com>
2016-09-15 6:47 ` Thomas Petazzoni
2016-09-15 7:18 ` Peter Korsgaard
2016-09-15 7:49 ` Thomas Petazzoni
2016-09-15 8:08 ` Peter Korsgaard
2016-09-15 10:53 ` Alexey Brodkin
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=d1ed5472-3500-45fc-eb0f-bdd2d6afb441@synopsys.com \
--to=vgupta@synopsys.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.