From: Rafael David Tinoco <rafaeldtinoco@ubuntu.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Vamsi Kodavanty <vamsi@araalinetworks.com>,
bpf <bpf@vger.kernel.org>
Subject: Re: [BPF CO-RE clarification] Use CO-RE on older kernel versions.
Date: Fri, 5 Mar 2021 03:32:37 -0300 [thread overview]
Message-ID: <043B1B9B-EEF7-49CD-88AF-29A2A3E97304@ubuntu.com> (raw)
In-Reply-To: <CAEf4BzZE_Ss7-cNdVpKJbC57mr2V_-OMcC9fvHw7XTntn3K2jA@mail.gmail.com>
>> Specially the attach_kprobe_legacy() function:
>>
>> https://github.com/rafaeldtinoco/portablebpf/blob/master/mine.c#L31
>>
>> I wanted to reply here in case others also face this.
>
> Great, glad it worked out. It would be great if you could contribute
> legacy kprobe support for libbpf as a proper patch, since it probably
> would be useful for a bunch of other people stuck with old kernels.
Definitely! Will suggest a patch for this soon.
Thanks for the feedback.
-rafaeldtinoco
next prev parent reply other threads:[~2021-03-05 6:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 18:02 [BPF CO-RE clarification] Use CO-RE on older kernel versions Vamsi Kodavanty
2021-01-06 23:55 ` Andrii Nakryiko
2021-01-07 18:12 ` Vamsi Kodavanty
2021-01-07 18:52 ` Andrii Nakryiko
2021-01-07 22:45 ` Vamsi Kodavanty
2021-01-07 23:32 ` Andrii Nakryiko
2021-01-08 0:16 ` Vamsi Kodavanty
2021-01-08 1:31 ` Vamsi Kodavanty
2021-03-03 18:14 ` Rafael David Tinoco
2021-03-04 7:05 ` Andrii Nakryiko
2021-03-04 13:10 ` Arnaldo Carvalho de Melo
2021-03-05 6:32 ` Rafael David Tinoco [this message]
[not found] ` <67E3C788-2835-4793-8A9C-51C5D807C294@ubuntu.com>
2021-03-10 6:00 ` Fwd: " Rafael David Tinoco
2021-03-10 19:19 ` Andrii Nakryiko
2021-03-10 22:45 ` Rafael David Tinoco
2021-03-12 18:36 ` Andrii Nakryiko
2021-03-17 4:39 ` Rafael David Tinoco
2021-03-17 14:31 ` Rafael David Tinoco
2021-03-19 4:36 ` Andrii Nakryiko
2021-03-19 4:42 ` Rafael David Tinoco
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=043B1B9B-EEF7-49CD-88AF-29A2A3E97304@ubuntu.com \
--to=rafaeldtinoco@ubuntu.com \
--cc=acme@redhat.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=vamsi@araalinetworks.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).