Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Stripping kernel modules for ARC
Date: Wed, 14 Sep 2016 11:29:26 +0000	[thread overview]
Message-ID: <1473852437.3766.15.camel@synopsys.com> (raw)

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. 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

             reply	other threads:[~2016-09-14 11:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 11:29 Alexey Brodkin [this message]
2016-09-14 19:00 ` [Buildroot] Stripping kernel modules for ARC Arnout Vandecappelle
2016-09-14 19:18 ` Vineet Gupta
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=1473852437.3766.15.camel@synopsys.com \
    --to=alexey.brodkin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox