All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: Include .BTF section
Date: Mon, 24 Feb 2020 09:33:15 +0530	[thread overview]
Message-ID: <1582516561.ya4ydk7t7x.naveen@linux.ibm.com> (raw)
In-Reply-To: <8736b0j090.fsf@mpe.ellerman.id.au>

Michael Ellerman wrote:
> "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> writes:
>> Selecting CONFIG_DEBUG_INFO_BTF results in the below warning from ld:
>>   ld: warning: orphan section `.BTF' from `.btf.vmlinux.bin.o' being placed in section `.BTF'
>>
>> Include .BTF section in vmlinux explicitly to fix the same.
> 
> I don't see any other architectures doing this in their linker script.
> Why are we special?

I think this is due to commit 83a092cf95f28 ("powerpc: Link warning for 
orphan sections"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=83a092cf95f28

If your question was why I didn't include the .BTF section in .data, 
it's because libbpf seems to expect the .BTF section to be separate.


- Naveen

PS: I also see a linker warning for '.gnu.hash' if I enable 
CONFIG_RELOCATABLE, but I couldn't decipher what that was for, and if it 
should be retained.


  reply	other threads:[~2020-02-24  4:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 11:31 [PATCH] powerpc: Include .BTF section Naveen N. Rao
2020-02-24  0:29 ` Michael Ellerman
2020-02-24  4:03   ` Naveen N. Rao [this message]
2020-02-24 11:03     ` Michael Ellerman
2020-02-27 12:31 ` Michael Ellerman

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=1582516561.ya4ydk7t7x.naveen@linux.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.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 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.