From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 8/9] [HACK] ARM: imx: work around v7_cpu_resume link error
Date: Fri, 15 Feb 2013 11:05:14 +0000 [thread overview]
Message-ID: <201302151105.14253.arnd@arndb.de> (raw)
In-Reply-To: <511D7701.8040809@wwwdotorg.org>
On Thursday 14 February 2013, Stephen Warren wrote:
> On 02/14/2013 03:47 PM, Arnd Bergmann wrote:
> > Patch c08e20d24 "arm: Add v7_invalidate_l1 to cache-v7.S"
> > moves the v7_invalidate_l1 symbol out of imx/headsmp.S,
> > which seems to cause a link error because it is now
> > too far away from v7_cpu_resume when building an
> > allyesconfig kernel.
>
> Is the problem from the following in arch/arm/mach-imx/headsmp.S:
>
> ENTRY(v7_cpu_resume)
> bl v7_invalidate_l1
>
> Isn't the range of bl +/- 32MiB (or +/- 16MibB in Thumb 2). Is the
> kernel really that big? Sorry, I'm having trouble understanding what
> causes the problem.
Well, it is an "allyesconfig" kernel, so things can get pretty big:
$ size obj-tmp/vmlinux -A
obj-tmp/vmlinux :
section size addr
.head.text 504 3221258240
.text 32707336 3221258752
.text.head 8 3253966088
.rodata 14028722 3253968896
__bug_table 127764 3267997624
.builtin_fw 684 3268125388
__ksymtab 53424 3268126072
__ksymtab_gpl 43560 3268179496
__kcrctab 26712 3268223056
__kcrctab_gpl 21780 3268249768
__ksymtab_strings 233706 3268271548
__param 33104 3268505256
__modver 4104 3268538360
__ex_table 4112 3268542464
.ARM.unwind_idx 967784 3268546576
.ARM.unwind_tab 1452168 3269514360
.notes 36 3270966528
.init.text 677840 3270967296
.exit.text 125672 3271645136
.init.arch.info 5396 3271770808
.init.tagtable 72 3271776204
.init.smpalt 928 3271776276
.init.pv_table 1704 3271777204
.init.data 678108 3271778912
.exit.data 119 3272457020
.data..percpu 1460032 3272458240
.data 3370068 3273924608
.tcm_start 940 3277294676
.bss 8007724 3277295616
.comment 43 0
.ARM.attributes 50 0
.debug_line 15780363 0
.debug_info 57192143 0
.debug_abbrev 5747374 0
.debug_aranges 299608 0
.debug_ranges 5414592 0
.debug_frame 4801748 0
.debug_str 7003282 0
.debug_loc 36237476 0
Total 196510790
THUMB2 support is obviously enabled (allyesconfig), and from the start of the
.head.text section to the end of .bss, it is 64,045,100 bytes, using yesterday's
linux-next kernel with my fixes. It will get bigger as we add more stuff
to multiplatform. The .text section alone is just short of 32MB.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, arm@kernel.org,
Shawn Guo <shawn.guo@linaro.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Dinh Nguyen <dinguyen@altera.com>, Pavel Machek <pavel@denx.de>,
Stephen Warren <swarren@nvidia.com>,
Simon Horman <horms+renesas@verge.net.au>
Subject: Re: [PATCH 8/9] [HACK] ARM: imx: work around v7_cpu_resume link error
Date: Fri, 15 Feb 2013 11:05:14 +0000 [thread overview]
Message-ID: <201302151105.14253.arnd@arndb.de> (raw)
In-Reply-To: <511D7701.8040809@wwwdotorg.org>
On Thursday 14 February 2013, Stephen Warren wrote:
> On 02/14/2013 03:47 PM, Arnd Bergmann wrote:
> > Patch c08e20d24 "arm: Add v7_invalidate_l1 to cache-v7.S"
> > moves the v7_invalidate_l1 symbol out of imx/headsmp.S,
> > which seems to cause a link error because it is now
> > too far away from v7_cpu_resume when building an
> > allyesconfig kernel.
>
> Is the problem from the following in arch/arm/mach-imx/headsmp.S:
>
> ENTRY(v7_cpu_resume)
> bl v7_invalidate_l1
>
> Isn't the range of bl +/- 32MiB (or +/- 16MibB in Thumb 2). Is the
> kernel really that big? Sorry, I'm having trouble understanding what
> causes the problem.
Well, it is an "allyesconfig" kernel, so things can get pretty big:
$ size obj-tmp/vmlinux -A
obj-tmp/vmlinux :
section size addr
.head.text 504 3221258240
.text 32707336 3221258752
.text.head 8 3253966088
.rodata 14028722 3253968896
__bug_table 127764 3267997624
.builtin_fw 684 3268125388
__ksymtab 53424 3268126072
__ksymtab_gpl 43560 3268179496
__kcrctab 26712 3268223056
__kcrctab_gpl 21780 3268249768
__ksymtab_strings 233706 3268271548
__param 33104 3268505256
__modver 4104 3268538360
__ex_table 4112 3268542464
.ARM.unwind_idx 967784 3268546576
.ARM.unwind_tab 1452168 3269514360
.notes 36 3270966528
.init.text 677840 3270967296
.exit.text 125672 3271645136
.init.arch.info 5396 3271770808
.init.tagtable 72 3271776204
.init.smpalt 928 3271776276
.init.pv_table 1704 3271777204
.init.data 678108 3271778912
.exit.data 119 3272457020
.data..percpu 1460032 3272458240
.data 3370068 3273924608
.tcm_start 940 3277294676
.bss 8007724 3277295616
.comment 43 0
.ARM.attributes 50 0
.debug_line 15780363 0
.debug_info 57192143 0
.debug_abbrev 5747374 0
.debug_aranges 299608 0
.debug_ranges 5414592 0
.debug_frame 4801748 0
.debug_str 7003282 0
.debug_loc 36237476 0
Total 196510790
THUMB2 support is obviously enabled (allyesconfig), and from the start of the
.head.text section to the end of .bss, it is 64,045,100 bytes, using yesterday's
linux-next kernel with my fixes. It will get bigger as we add more stuff
to multiplatform. The .text section alone is just short of 32MB.
Arnd
next prev parent reply other threads:[~2013-02-15 11:05 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 22:47 [PATCH 0/9] arm-soc/for-next allyesconfig build regressions Arnd Bergmann
2013-02-14 22:47 ` Arnd Bergmann
2013-02-14 22:47 ` [PATCH 1/9] ARM: arch_timer: include linux/errno.h Arnd Bergmann
2013-02-14 22:47 ` Arnd Bergmann
2013-02-15 10:26 ` Mark Rutland
2013-02-15 10:26 ` Mark Rutland
2013-02-15 18:33 ` Arnd Bergmann
2013-02-15 18:33 ` Arnd Bergmann
2013-02-14 22:47 ` [PATCH 2/9] ARM: imx: MACH_MX31ADS_WM1133_EV1 needs REGULATOR_WM8350 Arnd Bergmann
2013-02-14 22:47 ` Arnd Bergmann
2013-02-15 17:21 ` Sascha Hauer
2013-02-15 17:21 ` Sascha Hauer
2013-02-14 22:47 ` [PATCH 3/9] ARM: omap2: include linux/errno.h in hwmod_reset Arnd Bergmann
2013-02-14 22:47 ` Arnd Bergmann
2013-02-14 22:51 ` Tony Lindgren
2013-02-14 22:51 ` Tony Lindgren
2013-02-15 12:38 ` Arnd Bergmann
2013-02-15 12:38 ` Arnd Bergmann
2013-02-14 22:58 ` Paul Walmsley
2013-02-14 22:58 ` Paul Walmsley
2013-02-14 22:47 ` [PATCH 4/9] ARM: omap: add include guard for soc.h Arnd Bergmann
2013-02-14 22:47 ` Arnd Bergmann
2013-02-14 22:55 ` Tony Lindgren
2013-02-14 22:55 ` Tony Lindgren
2013-02-14 23:11 ` Arnd Bergmann
2013-02-14 23:11 ` Arnd Bergmann
2013-02-15 12:40 ` Arnd Bergmann
2013-02-15 12:40 ` Arnd Bergmann
2013-02-14 22:47 ` [PATCH 5/9] drm: export drm_vm_open_locked Arnd Bergmann
2013-02-14 22:47 ` Arnd Bergmann
2013-02-14 22:47 ` [PATCH 6/9] net: cwdavinci_cpdma: export symbols for cpsw Arnd Bergmann
2013-02-14 22:47 ` Arnd Bergmann
2013-02-14 22:52 ` David Miller
2013-02-14 22:52 ` David Miller
2013-02-14 22:47 ` [PATCH 7/9] remoteproc: omap: depend on OMAP_MBOX_FWK Arnd Bergmann
2013-02-14 22:47 ` Arnd Bergmann
2013-02-14 22:55 ` Tony Lindgren
2013-02-14 22:55 ` Tony Lindgren
2013-02-15 6:56 ` Ohad Ben-Cohen
2013-02-15 6:56 ` Ohad Ben-Cohen
2013-02-14 22:47 ` [PATCH 8/9] [HACK] ARM: imx: work around v7_cpu_resume link error Arnd Bergmann
2013-02-14 22:47 ` Arnd Bergmann
2013-02-14 23:45 ` Stephen Warren
2013-02-14 23:45 ` Stephen Warren
2013-02-15 11:05 ` Arnd Bergmann [this message]
2013-02-15 11:05 ` Arnd Bergmann
2013-02-15 11:13 ` Russell King - ARM Linux
2013-02-15 11:13 ` Russell King - ARM Linux
2013-02-15 15:49 ` Arnd Bergmann
2013-02-15 15:49 ` Arnd Bergmann
2013-02-15 11:07 ` Russell King - ARM Linux
2013-02-15 11:07 ` Russell King - ARM Linux
2013-02-16 5:14 ` Nicolas Pitre
2013-02-16 5:14 ` Nicolas Pitre
2013-02-18 5:55 ` Shawn Guo
2013-02-18 5:55 ` Shawn Guo
2013-02-18 17:06 ` Nicolas Pitre
2013-02-18 17:06 ` Nicolas Pitre
2013-02-19 1:42 ` Shawn Guo
2013-02-19 1:42 ` Shawn Guo
2013-02-19 4:11 ` Nicolas Pitre
2013-02-19 4:11 ` Nicolas Pitre
2013-02-19 5:10 ` Shawn Guo
2013-02-19 5:10 ` Shawn Guo
2013-02-14 22:47 ` [PATCH 9/9] [media] davinci: do not include mach/hardware.h Arnd Bergmann
2013-02-14 22:47 ` Arnd Bergmann
2013-02-14 22:57 ` Tony Lindgren
2013-02-14 22:57 ` Tony Lindgren
2013-02-15 5:06 ` Prabhakar Lad
2013-02-15 5:06 ` Prabhakar Lad
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=201302151105.14253.arnd@arndb.de \
--to=arnd@arndb.de \
--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 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.