From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Jakov Petrina <jakov.petrina@sartura.hr>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
Luka Perkov <luka.perkov@sartura.hr>,
Juraj Vijtiuk <juraj.vijtiuk@sartura.hr>,
Jakov Smolic <jakov.smolic@sartura.hr>,
bpf@vger.kernel.org, Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Andrii Nakryiko <andriin@fb.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: eBPF CO-RE cross-compilation for 32-bit ARM platforms
Date: Tue, 11 Aug 2020 11:05:01 +0100 [thread overview]
Message-ID: <20200811100500.GK1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <6872df6c-c541-5b35-a07d-77b2862c5333@sartura.hr>
On Mon, Aug 10, 2020 at 09:52:17AM +0200, Jakov Petrina wrote:
> Hi,
>
> On 07/08/2020 21:00, Russell King - ARM Linux admin wrote:
> >
> > For those of us not familiar with what CO-RE is, this doesn't help.
> > I assume the [0] was a reference to something that explained it,
> > but that isn't included.
> >
>
> the reference [0] is link to a blog post which explains the eBPF CO-RE
> concept; I have added this link as a reference below.
>
> >
> > What is "BTF information"? Google suggests it's something to do with
> > the British Thyroid Foundation.
> >
> > Please don't use three letter abbreviations unless they are widely
> > understood, or if you wish to, please ensure that you explain them.
> > TLAs otherwise are an exclusion mechanism.
> > >
> > What is this "vmlinux.h" ? It isn't something that the kernel provides
> > afaics. It doesn't seem to be present on my existing x86 Debian system.
> > I've seen it on Fedora systems in the dim and distant past.
> >
> > Where do you think it comes from? Where are you finding it?
> >
>
> The blog post [0] provides description and context for the references and
> abbreviations used, but in the future I will be sure to avoid using
> abbreviations unless they are commonly understood.
>
> [0] https://facebookmicrosites.github.io/bpf/blog/2020/02/19/bpf-portability-and-co-re.html
Okay, you've addressed one point I raised, but you have not addressed
any of the questions I raised. I'll take this thread as just noise on
the mailing list since it seems to contain nothing of any relevance to
the Linux kernel, and no one seems willing to explain why they think it
is relevant.
Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-11 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f1b8e140-bc41-4e56-e73f-db11062dddbd@sartura.hr>
2020-08-07 17:23 ` eBPF CO-RE cross-compilation for 32-bit ARM platforms Jean-Philippe Brucker
2020-08-07 18:40 ` Andrii Nakryiko
2020-08-07 20:54 ` Alexei Starovoitov
2020-08-10 12:57 ` Jean-Philippe Brucker
2020-08-11 6:54 ` Andrii Nakryiko
2020-08-11 9:54 ` Jean-Philippe Brucker
2020-08-12 3:18 ` Andrii Nakryiko
2020-08-07 19:00 ` Russell King - ARM Linux admin
2020-08-10 7:52 ` Jakov Petrina
2020-08-11 10:05 ` Russell King - ARM Linux admin [this message]
2020-08-10 7:39 ` Jakov Petrina
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=20200811100500.GK1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=bpf@vger.kernel.org \
--cc=jakov.petrina@sartura.hr \
--cc=jakov.smolic@sartura.hr \
--cc=jean-philippe@linaro.org \
--cc=juraj.vijtiuk@sartura.hr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=luka.perkov@sartura.hr \
/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).