From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Giuliano Procida <gprocida@google.com>
Cc: dwarves@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
maennich@google.com, kernel-team@android.com, kernel-team@fb.com,
bpf@vger.kernel.org
Subject: Re: [PATCH dwarves 0/4] BTF ELF writing changes
Date: Wed, 27 Jan 2021 11:06:01 -0300 [thread overview]
Message-ID: <20210127140601.GA752795@kernel.org> (raw)
In-Reply-To: <20210125130625.2030186-1-gprocida@google.com>
Em Mon, Jan 25, 2021 at 01:06:21PM +0000, Giuliano Procida escreveu:
> Hi.
>
> This follows on from my change to improve the error handling around
> llvm-objcopy in libbtf.c.
>
> Note on recipients: Please let me know if I should adjust To or CC.
>
> Note on style: I've generally placed declarations as allowed by C99,
> closest to point of use. Let me know if you'd prefer otherwise.
>
> 1. Improve ELF error reporting
applied
> 2. Add .BTF section using libelf
>
> This shows the minimal amount of code needed to drive libelf. However,
> it leaves layout up to libelf, which is almost certainly not wanted.
>
> As an unexpcted side-effect, vmlinux is larger than before. It seems
> llvm-objcopy likes to trim down .strtab.
We have to test this thoroughly, I'm adding support to gcc's -gdwarf-5
DW_AT_data_bit_offset, I think I should get that done and release 1.20,
if some bug is still left on that new code, we can just fallback to
-gdwarf-4.
Then get back to the last 2 patches in your series, ok?
- Arnaldo
> 3. Manually lay out updated ELF sections
>
> This does full layout of new and updated ELF sections. If the update
> ELF sections were not the last ones in the file by offset, then it can
> leave gaps between sections.
>
> 4. Align .BTF section to 8 bytes
>
> This was my original aim.
>
> Regards.
>
> Giuliano Procida (4):
> btf_encoder: Improve ELF error reporting
> btf_encoder: Add .BTF section using libelf
> btf_encoder: Manually lay out updated ELF sections
> btf_encoder: Align .BTF section to 8 bytes
>
> libbtf.c | 222 +++++++++++++++++++++++++++++++++++++++++++------------
> 1 file changed, 175 insertions(+), 47 deletions(-)
>
> --
> 2.30.0.280.ga3ce27912f-goog
>
--
- Arnaldo
next prev parent reply other threads:[~2021-01-27 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 13:06 [PATCH dwarves 0/4] BTF ELF writing changes Giuliano Procida
2021-01-25 13:06 ` [PATCH dwarves 1/4] btf_encoder: Improve ELF error reporting Giuliano Procida
2021-01-25 13:06 ` [PATCH dwarves 2/4] btf_encoder: Add .BTF section using libelf Giuliano Procida
2021-01-27 23:23 ` Jiri Olsa
2021-01-28 13:35 ` Giuliano Procida
2021-02-05 13:40 ` Giuliano Procida
2021-01-25 13:06 ` [PATCH dwarves 3/4] btf_encoder: Manually lay out updated ELF sections Giuliano Procida
2021-01-25 13:06 ` [PATCH dwarves 4/4] btf_encoder: Align .BTF section to 8 bytes Giuliano Procida
2021-01-26 19:55 ` [PATCH dwarves 0/4] BTF ELF writing changes Jiri Olsa
2021-01-27 1:10 ` Giuliano Procida
2021-01-27 1:42 ` Arnaldo Carvalho de Melo
2021-01-27 14:06 ` Arnaldo Carvalho de Melo [this message]
2021-01-27 14:36 ` Giuliano Procida
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=20210127140601.GA752795@kernel.org \
--to=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=gprocida@google.com \
--cc=kernel-team@android.com \
--cc=kernel-team@fb.com \
--cc=maennich@google.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