From: Yonghong Song <yhs@fb.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
<dwarves@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>, <bpf@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>, <kernel-team@fb.com>
Subject: Re: [PATCH dwarves] libbpf: Get latest libbpf
Date: Sun, 19 Sep 2021 16:10:32 -0700 [thread overview]
Message-ID: <1c7ff967-f056-7cf9-9a14-8ce35db25c91@fb.com> (raw)
In-Reply-To: <YUZbpcO1il2WgNR8@kernel.org>
On 9/18/21 2:35 PM, Arnaldo Carvalho de Melo wrote:
> Em Fri, Sep 17, 2021 at 03:48:18PM -0700, Yonghong Song escreveu:
>> Latest upstream LLVM now supports to emit btf_tag to
>> dwarf ([1]) and the kernel support for btf_tag is also
>> landed ([2]). Sync with latest libbpf which has
>> btf_tag support. Next step will be to implement
>> dwarf -> btf conversion for btf_tag.
>
> Thanks, applied and pushed out. Looking forward to the upcoming btf_tag
> patches!
Great! Thanks. I already have a rough pahole patch. Will do a little bit
more testing and add flags control and then will send out.
>
> - Arnaldo
>
>> [1] https://reviews.llvm.org/D106621
>> [2] https://lore.kernel.org/bpf/20210914223015.245546-1-yhs@fb.com
>>
>> Signed-off-by: Yonghong Song <yhs@fb.com>
>> ---
>> lib/bpf | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/bpf b/lib/bpf
>> index 986962f..980777c 160000
>> --- a/lib/bpf
>> +++ b/lib/bpf
>> @@ -1 +1 @@
>> -Subproject commit 986962fade5dfa89c2890f3854eb040d2a64ab38
>> +Subproject commit 980777cc16db75d5628a537c892aefc2640bb242
>> --
>> 2.30.2
>
prev parent reply other threads:[~2021-09-19 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 22:48 [PATCH dwarves] libbpf: Get latest libbpf Yonghong Song
2021-09-18 21:35 ` Arnaldo Carvalho de Melo
2021-09-19 23:10 ` Yonghong Song [this message]
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=1c7ff967-f056-7cf9-9a14-8ce35db25c91@fb.com \
--to=yhs@fb.com \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dwarves@vger.kernel.org \
--cc=kernel-team@fb.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).