From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Charles Steinkuehler <charles@steinkuehler.net>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] ARM/BeagleBone Thumb2 Kernels
Date: Fri, 24 Jan 2014 13:28:46 +0100 [thread overview]
Message-ID: <52E25C7E.6040002@xenomai.org> (raw)
In-Reply-To: <52E2544A.3060907@steinkuehler.net>
On 01/24/2014 12:53 PM, Charles Steinkuehler wrote:
> On 1/24/2014 6:18 AM, Gilles Chanteperdrix wrote:
>> On 01/24/2014 12:38 PM, Charles Steinkuehler wrote:
>>> As I understand it, the issue arises as the kernel grows larger and the
>>> distance between the branch and it's target increases. My vmlinux for
>>> the (fixed Thumb2 version) BeagleBone kernel is currently weighing in at
>>> 13225004 bytes.
>>>
>> That is precisely the thing I do not understand: the jump goes from
>> entry-armv.S to entry-common.S which should remain close since they
>> follow each other on the link-edit command line. Since the source files
>> are assembly, the distance should more or less be the same, whatever the
>> compilation options. And if they are not close, this is where the bug
>> is, because this assembly is used for every syscall and every interrupt.
>
> Well I don't pretend to know what goes on in the kernel memory map. Is
> there anything I can send from my kernel builds that would shed light on
> this (a linker map or something)?
>
I have no doubt that in the kernel you build, entry-arm.S and
entry-common.S end up far from each other, which a linker map would
show. What I am interested in is why this happens, for that, I need to
build the kernel the same way you build it, and see what happens. You
have given me all I need.
--
Gilles.
next prev parent reply other threads:[~2014-01-24 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 2:56 [Xenomai] ARM/BeagleBone Thumb2 Kernels Charles Steinkuehler
2014-01-24 10:52 ` Gilles Chanteperdrix
2014-01-24 11:22 ` Gilles Chanteperdrix
2014-01-24 11:38 ` Charles Steinkuehler
2014-01-24 12:18 ` Gilles Chanteperdrix
2014-01-24 11:53 ` Charles Steinkuehler
2014-01-24 12:28 ` Gilles Chanteperdrix [this message]
2014-01-25 18:14 ` Gilles Chanteperdrix
2014-01-25 17:48 ` Charles Steinkuehler
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=52E25C7E.6040002@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=charles@steinkuehler.net \
--cc=xenomai@xenomai.org \
/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.