From: Yonghong Song <yhs@fb.com>
To: <sedat.dilek@gmail.com>
Cc: "Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Arnaldo Carvalho de Melo" <arnaldo.melo@gmail.com>,
dwarves@vger.kernel.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
bpf@vger.kernel.org, "Jiri Olsa" <jolsa@kernel.org>,
"Jan Engelhardt" <jengelh@inai.de>,
"Domenico Andreoli" <cavok@debian.org>,
"Matthias Schwarzott" <zzam@gentoo.org>,
"Andrii Nakryiko" <andriin@fb.com>,
"Mark Wieelard" <mjw@redhat.com>,
"Paul Moore" <paul@paul-moore.com>,
"Ondrej Mosnacek" <omosnace@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Tom Stellard" <tstellar@redhat.com>
Subject: Re: ERROR: INT DW_ATE_unsigned_1 Error emitting BTF type
Date: Fri, 5 Feb 2021 13:54:02 -0800 [thread overview]
Message-ID: <d59c2a53-976c-c304-f208-67110bdd728a@fb.com> (raw)
In-Reply-To: <CA+icZUUcjJASPN8NVgWNp+2h=WO-PT4Su3-yHZpynNHCrHEb-w@mail.gmail.com>
On 2/5/21 12:31 PM, Sedat Dilek wrote:
> On Fri, Feb 5, 2021 at 9:03 PM Yonghong Song <yhs@fb.com> wrote:
>>
>>
>>
>> On 2/5/21 11:24 AM, Arnaldo Carvalho de Melo wrote:
>>> Em Fri, Feb 05, 2021 at 11:10:08AM -0800, Yonghong Song escreveu:
>>>> On 2/5/21 11:06 AM, Sedat Dilek wrote:
>>>>> On Fri, Feb 5, 2021 at 7:53 PM Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>>>> Grepping through linux.git/tools I guess some BTF tools/libs need to
>>>>> know what BTF_INT_UNSIGNED is?
>>>
>>>> BTF_INT_UNSIGNED needs kernel support. Maybe to teach pahole to
>>>> ignore this for now until kernel infrastructure is ready.
>>>
>>> Yeah, I thought about doing that.
>>>
>>>> Not sure whether this information will be useful or not
>>>> for BTF. This needs to be discussed separately.
>>>
>>> Maybe search for the rationale for its introduction in DWARF.
>>
>> In LLVM, we have:
>> uint8_t BTFEncoding;
>> switch (Encoding) {
>> case dwarf::DW_ATE_boolean:
>> BTFEncoding = BTF::INT_BOOL;
>> break;
>> case dwarf::DW_ATE_signed:
>> case dwarf::DW_ATE_signed_char:
>> BTFEncoding = BTF::INT_SIGNED;
>> break;
>> case dwarf::DW_ATE_unsigned:
>> case dwarf::DW_ATE_unsigned_char:
>> BTFEncoding = 0;
>> break;
>>
>> I think DW_ATE_unsigned can be ignored in pahole since
>> the default encoding = 0. A simple comment is enough.
>>
>
> Yonghong Son, do you have a patch/diff for me?
Looking at error message from log:
LLVM_OBJCOPY=/opt/binutils/bin/objcopy /opt/pahole/bin/pahole -J
.tmp_vmlinux.btf
[115] INT DW_ATE_unsigned_1 Error emitting BTF type
Encountered error while encoding BTF.
Not exactly what is the root cause. Maybe bt->bit_size is not
encoded correctly. Could you put vmlinux (in the above it is
.tmp_vmlinux.btf) somewhere, I or somebody else can investigate
and provide a proper fix.
> Thanks.
>
> - Sedat -
>
next prev parent reply other threads:[~2021-02-05 21:57 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 22:07 ANNOUNCE: pahole v1.20 (gcc11 DWARF5's default, lots of ELF sections, BTF) Arnaldo Carvalho de Melo
2021-02-04 22:10 ` Sedat Dilek
2021-02-05 0:01 ` Andrii Nakryiko
2021-02-05 4:33 ` Arnaldo Carvalho de Melo
2021-02-05 7:39 ` Andrii Nakryiko
2021-02-05 9:33 ` Arnaldo Carvalho de Melo
2021-02-05 16:25 ` Arnaldo Carvalho de Melo
2021-02-05 22:11 ` Andrii Nakryiko
2021-02-05 23:55 ` Arnaldo Carvalho de Melo
2021-02-07 6:40 ` Andrii Nakryiko
2021-02-05 14:37 ` ERROR: INT DW_ATE_unsigned_1 Error emitting BTF type Sedat Dilek
2021-02-05 14:41 ` Sedat Dilek
2021-02-05 15:23 ` Sedat Dilek
2021-02-05 15:28 ` Arnaldo Carvalho de Melo
2021-02-05 15:40 ` Sedat Dilek
2021-02-05 17:48 ` Sedat Dilek
2021-02-05 18:53 ` Sedat Dilek
2021-02-05 19:06 ` Sedat Dilek
2021-02-05 19:10 ` Yonghong Song
2021-02-05 19:15 ` Sedat Dilek
2021-02-05 19:20 ` Yonghong Song
2021-02-05 19:24 ` Sedat Dilek
2021-02-05 19:44 ` Sedat Dilek
2021-02-05 19:21 ` Sedat Dilek
2021-02-05 19:30 ` Fāng-ruì Sòng
2021-02-05 19:38 ` Sedat Dilek
2021-02-05 19:24 ` Arnaldo Carvalho de Melo
2021-02-05 20:03 ` Yonghong Song
2021-02-05 20:31 ` Sedat Dilek
2021-02-05 21:54 ` Yonghong Song [this message]
2021-02-06 3:34 ` Sedat Dilek
2021-02-06 5:44 ` Sedat Dilek
2021-02-06 5:53 ` Sedat Dilek
2021-02-06 6:26 ` Sedat Dilek
2021-02-06 6:52 ` Sedat Dilek
2021-02-06 8:26 ` Yonghong Song
2021-02-06 8:32 ` Sedat Dilek
2021-02-06 9:32 ` Sedat Dilek
2021-02-06 9:37 ` Sedat Dilek
2021-02-06 9:48 ` Sedat Dilek
2021-02-06 10:16 ` Sedat Dilek
2021-02-06 10:23 ` Sedat Dilek
2021-02-06 11:27 ` Sedat Dilek
2021-02-06 12:54 ` Sedat Dilek
2021-02-06 16:24 ` Mark Wieelard
2021-02-06 17:53 ` Yonghong Song
2021-02-06 18:10 ` Sedat Dilek
2021-02-06 19:17 ` Yonghong Song
2021-02-06 19:22 ` Sedat Dilek
2021-02-06 19:28 ` Sedat Dilek
2021-02-06 19:32 ` Yonghong Song
2021-02-06 19:44 ` Sedat Dilek
2021-02-06 20:12 ` Yonghong Song
2021-02-06 20:46 ` Sedat Dilek
2021-02-06 7:26 ` Sedat Dilek
2021-02-05 21:10 ` Nick Desaulniers
2021-02-05 21:16 ` Sedat Dilek
2021-02-05 21:40 ` Nick Desaulniers
2021-02-05 21:42 ` Sedat Dilek
2021-02-08 2:44 ` ANNOUNCE: pahole v1.20 (gcc11 DWARF5's default, lots of ELF sections, BTF) Sedat Dilek
2021-02-08 12:32 ` Arnaldo Carvalho de Melo
2021-02-08 12:36 ` Sedat Dilek
2021-02-17 12:08 ` Domenico Andreoli
2021-02-17 12:48 ` Arnaldo Carvalho de Melo
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=d59c2a53-976c-c304-f208-67110bdd728a@fb.com \
--to=yhs@fb.com \
--cc=acme@kernel.org \
--cc=andriin@fb.com \
--cc=arnaldo.melo@gmail.com \
--cc=berrange@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=cavok@debian.org \
--cc=dwarves@vger.kernel.org \
--cc=jengelh@inai.de \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjw@redhat.com \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=sedat.dilek@gmail.com \
--cc=tstellar@redhat.com \
--cc=zzam@gentoo.org \
/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
all inboxes | Powered by JetHome®