From: Edward Cree <ecree@solarflare.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Jiong Wang <jiong.wang@netronome.com>,
"David S. Miller" <davem@davemloft.net>,
"Yonghong Song" <yhs@fb.com>, Martin KaFai Lau <kafai@fb.com>,
Andrii Nakryiko <andriin@fb.com>, <binutils@sourceware.org>,
Daniel Borkmann <daniel@iogearbox.net>, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH 0/9] eBPF support for GNU binutils
Date: Tue, 21 May 2019 20:49:16 +0100 [thread overview]
Message-ID: <3be85ea0-2f81-a6bd-5291-6d6aed5aa554@solarflare.com> (raw)
In-Reply-To: <87tvdnlhyl.fsf@oracle.com>
On 21/05/2019 20:34, Jose E. Marchesi wrote:
> On 21/05/2019 19:18, Alexei Starovoitov wrote:
> > I think Ed had an idea on how to specify BTF in asm syntax.
> Specifically, see [1] for BTF as implemented in ebpf_asm, though note
> that it doesn't (yet) cover .btf.ext or lineinfo.
>
> [1]: https://github.com/solarflarecom/ebpf_asm/tree/btfdoc#type-definitions
>
> Thanks for the reference. I just checked out your `btfdoc' branch. I
> will take a look.
>
> Where would you like to get feedback/suggestions/questions btw?
For ebpf_asm? Either through GitHub Issues, or this address (ecree@solarflare.com).
I'm not actually on bpf@vger (though maybe I ought to subscribe...)
BTW I'm really happy to see someone working on eBPF support in the GNU
toolchain; being tied to an LLVM monoculture has been bad for eBPF imho.
-Ed
prev parent reply other threads:[~2019-05-21 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190520164526.13491-1-jose.marchesi () oracle ! com>
2019-05-21 15:41 ` [PATCH 0/9] eBPF support for GNU binutils Jiong Wang
2019-05-21 17:06 ` Jose E. Marchesi
2019-05-21 18:14 ` Jiong Wang
2019-05-21 19:13 ` Jose E. Marchesi
2019-05-21 17:43 ` David Miller
2019-05-21 18:18 ` Alexei Starovoitov
2019-05-21 18:58 ` Jose E. Marchesi
2019-05-21 19:02 ` Edward Cree
2019-05-21 19:34 ` Jose E. Marchesi
2019-05-21 19:49 ` Edward Cree [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=3be85ea0-2f81-a6bd-5291-6d6aed5aa554@solarflare.com \
--to=ecree@solarflare.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andriin@fb.com \
--cc=binutils@sourceware.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jiong.wang@netronome.com \
--cc=jose.marchesi@oracle.com \
--cc=kafai@fb.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).