linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arasv@magellan-technology.com (Aras Vaichas)
To: linux-arm-kernel@lists.infradead.org
Subject: cmpxchg() in recent kernels
Date: Tue, 26 Oct 2010 09:48:40 +1100	[thread overview]
Message-ID: <AANLkTimyOYEh0gCZTF3JsXeVT3UwoK1VcXgx+zscZmj1@mail.gmail.com> (raw)
In-Reply-To: <20101025151319.GA21105@n2100.arm.linux.org.uk>

On 26 October 2010 02:13, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Mon, Oct 25, 2010 at 12:33:49PM +1100, Aras Vaichas wrote:
>> On 25 October 2010 09:08, Russell King - ARM Linux
>> <linux@arm.linux.org.uk> wrote:
>> >
>> > On Sun, Oct 24, 2010 at 11:43:38PM +0200, Kristoffer Ericson wrote:
>> > > Im seeing something similiar, using GCC 3.4.5
>> > > ARM HP Jornada 720, 2.6.36
>> snip ...
>> > > kernel/built-in.o(.text+0x1d038): In function `alloc_pid':
>> > > include/asm-generic/cmpxchg-local.h:42: undefined reference to `wrong_size_cmpxchg'
>> > > make: *** [.tmp_vmlinux1] Error 1
>> >
>> > Probably needs to be bisected, but I think in the long run we'll have
>> > to accept that gcc 4 will become the minimum compiler version.
>>
>> I just tested a build with GCC 4.2.3 and it linked correctly. The only
>> problem is that the kernel image size is now 3x as big.
>>
>>
>> Using gcc-3.4.4-glibc-2.3.5:
>>
>> * fails to link without patch to cmpxchg-local.h, but size is similar
>> to my previous builds
>>
>> Created: ? ? ?Mon Oct 25 11:59:04 2010
>> Image Type: ? ARM Linux Kernel Image (gzip compressed)
>> Data Size: ? ?1471354 Bytes = 1436.87 kB = 1.40 MB
>>
>>
>> Using gcc-4.2.3-glibc-2.7:
>>
>> * compiles and links correctly, but size is way too big
>>
>> Created: ? ? ?Mon Oct 25 11:48:26 2010
>> Image Type: ? ARM Linux Kernel Image (gzip compressed)
>> Data Size: ? ?4576155 Bytes = 4468.90 kB = 4.36 MB
>
> This sounds like a regression - can you please bisect to try and find
> which change caused tihs?

OK, problem solved. I had this problem:
http://lists.busybox.net/pipermail/buildroot/2008-June/021158.html

The fix for this problem was included as a patch for the kernel as shown here:
http://lists.busybox.net/pipermail/buildroot/2008-June/021162.html

But my U-Boot uImage build script does its own objcopy and thus didn't
get patched. I've added the extra objcopy arguments to my script and
my final image size is now 1.36MB.

For reference, this is my uImage make script:

make ARCH=arm CROSS_COMPILE=${CROSS_PATH} INSTALL_MOD_PATH=${FS_PATH} Image

${CROSS_PATH}objcopy -O binary -R .note -R .note.gnu.build-id -R
.comment -S vmlinux linux.bin

gzip -v9 linux.bin

${MKIMAGE} -A arm -O linux -C gzip -a 0x20008000 -e 0x20008000 -d
linux.bin.gz uImage


Aras

  reply	other threads:[~2010-10-25 22:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-09  9:32 cmpxchg() in recent kernels Alex Sverdlin
2010-10-15  4:26 ` Aras Vaichas
2010-10-24 21:43   ` Kristoffer Ericson
2010-10-24 22:08     ` Russell King - ARM Linux
2010-10-25  1:33       ` Aras Vaichas
2010-10-25  6:37         ` Uwe Kleine-König
2010-10-25 15:13         ` Russell King - ARM Linux
2010-10-25 22:48           ` Aras Vaichas [this message]
2010-10-26  6:44             ` Uwe Kleine-König
2010-10-26 12:10               ` Aras Vaichas
2010-10-25 21:07         ` Kristoffer Ericson
2010-10-25 22:37           ` Alexander Sverdlin

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=AANLkTimyOYEh0gCZTF3JsXeVT3UwoK1VcXgx+zscZmj1@mail.gmail.com \
    --to=arasv@magellan-technology.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).