linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Balbir Singh <bsingharora@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH 3/7] powerpc/64s: tool to flag direct branches from unrelocated interrupt vectors
Date: Wed, 19 Oct 2016 17:01:46 +1100	[thread overview]
Message-ID: <20161019170146.75d936bc@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <408e4f35-17a6-8738-c711-8bfb39928628@gmail.com>

On Wed, 19 Oct 2016 15:28:40 +1100
Balbir Singh <bsingharora@gmail.com> wrote:

> On 19/10/16 14:15, 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: Nicholas Piggin <npiggin@gmail.com>
> > ---  
> 
> If this is the same script I gave you, you can add my SOB line as well

I can't remember now, but I know you had something... I'm usually careful
to get attributions right. I'll add your SOB.

  reply	other threads:[~2016-10-19  6:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19  3:15 [PATCH 0/7] build updates Nicholas Piggin
2016-10-19  3:15 ` [PATCH 1/7] powerpc: use the new post-link pass to check relocations Nicholas Piggin
2016-10-19  3:15 ` [PATCH 2/7] powerpc: add arch/powerpc/tools directory Nicholas Piggin
2016-10-19  3:15 ` [PATCH 3/7] powerpc/64s: tool to flag direct branches from unrelocated interrupt vectors Nicholas Piggin
2016-10-19  4:28   ` Balbir Singh
2016-10-19  6:01     ` Nicholas Piggin [this message]
2016-10-19 10:57   ` Michael Ellerman
2016-10-19  3:15 ` [PATCH 4/7] powerpc/64: tool to check head sections location sanity Nicholas Piggin
2016-11-15  0:55   ` Michael Ellerman
2016-11-22  4:54     ` Nicholas Piggin
2016-11-22  5:56       ` Michael Ellerman
2016-10-19  3:15 ` [PATCH 5/7] powerpc/64: handle linker stubs in low .text code Nicholas Piggin
2016-10-19  3:15 ` [PATCH 6/7] powerpc: switch to using thin archives if COMPILE_TEST is set Nicholas Piggin
2016-10-19  5:57   ` Stephen Rothwell
2016-10-19  9:26     ` Nicholas Piggin
2016-10-19 11:00   ` Michael Ellerman
2016-10-20  3:48     ` Nicholas Piggin
2016-11-22  0:34   ` [6/7] " Michael Ellerman
2016-10-19  3:16 ` [PATCH 7/7] powerpc/64: allow CONFIG_RELOCATABLE if COMPILE_TEST Nicholas Piggin
2017-05-03 22:18   ` [7/7] " Michael Ellerman
2016-10-19  7:44 ` [PATCH 0/7] build updates Nicholas Piggin
2016-10-21  6:35   ` [PATCH 0/7] build updates (and RFC on one-pass kallsyms generation) 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=20161019170146.75d936bc@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=bsingharora@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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).