From: Sean Young <sean@mess.org>
To: Yonghong Song <yhs@fb.com>
Cc: "Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Martin KaFai Lau" <kafai@fb.com>,
"Song Liu" <songliubraving@fb.com>,
"John Fastabend" <john.fastabend@gmail.com>,
"KP Singh" <kpsingh@kernel.org>,
"Nathan Chancellor" <natechancellor@gmail.com>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Quentin Monnet" <quentin@isovalent.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH v2] btf: support ints larger than 128 bits
Date: Tue, 5 Jan 2021 13:58:08 +0000 [thread overview]
Message-ID: <20210105135808.GA13438@gofer.mess.org> (raw)
In-Reply-To: <bf26fcc9-a2b5-9d6f-a2ac-e39a0b14d838@fb.com>
On Wed, Dec 30, 2020 at 10:21:09AM -0800, Yonghong Song wrote:
> On 12/19/20 8:36 AM, Sean Young wrote:
> > clang supports arbitrary length ints using the _ExtInt extension. This
> > can be useful to hold very large values, e.g. 256 bit or 512 bit types.
> >
> > Larger types (e.g. 1024 bits) are possible but I am unaware of a use
> > case for these.
> >
> > This requires the _ExtInt extension enabled in clang, which is under
> > review.
> >
> > Link: https://clang.llvm.org/docs/LanguageExtensions.html#extended-integer-types
> > Link: https://reviews.llvm.org/D93103
> >
> > Signed-off-by: Sean Young <sean@mess.org>
> > ---
> > changes since v2:
> > - added tests as suggested by Yonghong Song
> > - added kernel pretty-printer
> >
> > Documentation/bpf/btf.rst | 4 +-
> > include/uapi/linux/btf.h | 2 +-
> > kernel/bpf/btf.c | 54 +-
> > tools/bpf/bpftool/btf_dumper.c | 40 ++
> > tools/include/uapi/linux/btf.h | 2 +-
> > tools/lib/bpf/btf.c | 2 +-
> > tools/testing/selftests/bpf/Makefile | 3 +-
> > tools/testing/selftests/bpf/prog_tests/btf.c | 3 +-
> > .../selftests/bpf/progs/test_btf_extint.c | 50 ++
> > tools/testing/selftests/bpf/test_extint.py | 535 ++++++++++++++++++
>
> For easier review, maybe you can break this patch into a patch series like
> below?
> patch 1 (kernel related changes and doc)
> kernel/bpf/btf.c, include/uapi/linux/btf.h,
> tools/include/uapi/linux/btf.h
> Documentation/bpf/btf.rst
> patch 2 (libbpf support)
> tools/lib/bpf/btf.c
> patch 3 (bpftool support)
> tools/bpf/bpftool/btf_dumper.c
> patch 4 (testing)
> rest files
That makes sense, I'll send out v3 shortly.
Thanks,
Sean
prev parent reply other threads:[~2021-01-05 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 16:36 [PATCH v2] btf: support ints larger than 128 bits Sean Young
2020-12-30 18:21 ` Yonghong Song
2021-01-05 13:58 ` Sean Young [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=20210105135808.GA13438@gofer.mess.org \
--to=sean@mess.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=songliubraving@fb.com \
--cc=toke@redhat.com \
--cc=yhs@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).