From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <52E25A15.4080406@xenomai.org> Date: Fri, 24 Jan 2014 13:18:29 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <52E1D646.8050907@steinkuehler.net> <52E24D0C.4050207@xenomai.org> <52E25099.9070107@steinkuehler.net> In-Reply-To: <52E25099.9070107@steinkuehler.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] ARM/BeagleBone Thumb2 Kernels List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Charles Steinkuehler Cc: xenomai@xenomai.org 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. -- Gilles.