On 12 August 2016 at 15:52, Russell King - ARM Linux
<linux@xxxxxxxxxxxxxxx> wrote:
> On Fri, Aug 12, 2016 at 03:50:17PM +0200, Ard Biesheuvel wrote:
>> $ objdump -dr vmlinux |grep -A1 -E \\sb\.w |less
>>
>> I get numerous instances of b.w that are not covered by any
>> relocations, so i assume that will be the case for modules as well.
>
> Not surprising. vmlinux is fully linked. There's no relocations.
>
My bad. It does if you link it with --emit-relocs.
Random snippet:
c036b098: f7ff bff8 b.w c036b08c <rcu_barrier>
c036b098: R_ARM_THM_JUMP24 rcu_barrier
--
c036b5ae: f7ff ba5b b.w c036aa68 <rcu_gp_kthread_wake>
c036b5b2: bf00 nop
--
c036bc28: f1c6 b6da b.w c09329e0 <_raw_spin_unlock_irqrestore>
c036bc28: R_ARM_THM_JUMP24
_raw_spin_unlock_irqrestore
--
c036bcbc: f7ee bc2e b.w c035a51c <swake_up>
c036bcbc: R_ARM_THM_JUMP24 swake_up
--
c036c63a: f7ff bfd5 b.w c036c5e8 <synchronize_sched>
c036c63a: R_ARM_THM_JUMP24 synchronize_sched
--
c036c640: f7ff bff0 b.w c036c624 <cond_synchronize_sched>
c036c640: R_ARM_THM_JUMP24 cond_synchronize_sched
--
c036c644: f7ff bb3e b.w c036bcc4 <synchronize_sched_expedited>
c036c644: R_ARM_THM_JUMP24
synchronize_sched_expedited
--
c036c690: f7dc ba0a b.w c0348aa8 <resched_cpu>
c036c690: R_ARM_THM_JUMP24 resched_cpu
--
c036c6a2: f7ff baad b.w c036bc00
<rcu_report_exp_cpu_mult.constprop.22>
c036c6a6: bf00 nop
--
c036c716: f7ff ba73 b.w c036bc00
<rcu_report_exp_cpu_mult.constprop.22>
c036c71a: bf00 nop
--
c036cf3a: f7fd bc4d b.w c036a7d8 <rcu_eqs_enter_common>
c036cf3e: bf00 nop
So some branches are relocated, some have already been resolved at compile time.
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
