From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [1/3] powerpc/64s: tool to flag direct branches from unrelocated interrupt vectors
Date: Tue, 30 May 2017 19:11:19 +1000 (AEST) [thread overview]
Message-ID: <3wcSX73tslz9s65@ozlabs.org> (raw)
In-Reply-To: <20170511174040.19728-2-npiggin@gmail.com>
On Thu, 2017-05-11 at 17:40:38 UTC, Nicholas Piggin wrote:
> Direct banches from code below __end_interrupts to code above
> __end_interrupts when built with CONFIG_RELOCATABLE are disallowed
> because they will break when the kernel is not located at 0.
>
> Sample output:
>
> WARNING: Unrelocated relative branches
> c000000000000118 bl-> 0xc000000000038fb8 <pnv_restore_hyp_resource>
> c00000000000013c b-> 0xc0000000001068a4 <kvm_start_guest>
> c000000000000148 b-> 0xc00000000003919c <pnv_wakeup_loss>
> c00000000000014c b-> 0xc00000000003923c <pnv_wakeup_noloss>
> c0000000000005a4 b-> 0xc000000000106ffc <kvmppc_interrupt_hv>
> c000000000001af0 b-> 0xc000000000106ffc <kvmppc_interrupt_hv>
> c000000000001b24 b-> 0xc000000000106ffc <kvmppc_interrupt_hv>
> c000000000001b58 b-> 0xc000000000106ffc <kvmppc_interrupt_hv>
>
> Signed-off-by: Balbir Singh <bsingharora@gmail.com>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/4ea80652dc75482dca1739762075dd
cheers
next prev parent reply other threads:[~2017-05-30 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 17:40 [PATCH 0/3] more build time checks Nicholas Piggin
2017-05-11 17:40 ` [PATCH 1/3] powerpc/64s: tool to flag direct branches from unrelocated interrupt vectors Nicholas Piggin
2017-05-30 9:11 ` Michael Ellerman [this message]
2017-05-11 17:40 ` [PATCH 2/3] powerpc/64: tool to check head sections location sanity Nicholas Piggin
2017-05-11 17:40 ` [PATCH 3/3] powerpc: link warning for orphan sections Nicholas Piggin
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=3wcSX73tslz9s65@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
/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).