From: tonyj@suse.de
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: "Shung-Hsi Yu" <shung-hsi.yu@suse.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Andrii Nakryiko" <andrii@kernel.org>,
bpf@vger.kernel.org, linux-perf-users@vger.kernel.org,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Quentin Monnet" <quentin@isovalent.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"Michal Suchanek" <msuchanek@suse.de>,
"Jesper Dangaard Brouer" <brouer@redhat.com>,
"Jakub Sitnicki" <jakub@cloudflare.com>,
"David Miller" <davem@davemloft.net>
Subject: Re: Packaging bpftool and libbpf: GitHub or kernel?
Date: Wed, 19 Apr 2023 15:23:36 -0700 [thread overview]
Message-ID: <ZEBp6C9zqDnM1PfT@suse.de> (raw)
In-Reply-To: <CAEf4BzbxfvR4Ji1q4wJCFHOxQgFzHr8t7TMK1VJj9sJ+a0srVQ@mail.gmail.com>
On Wed, Apr 19, 2023 at 12:42:39PM -0700, Andrii Nakryiko wrote:
> I won't claim anything for perf, maybe Arnaldo can clarify, but I
> suspect that perf is also meant to be relatively independent from
> specific kernel and work on wide variety of kernels.
Supposedly it is though I've never been able to convince myself to
decouple (and ship the latest perf) for SLE. One reason is documented
userspace functionality that has no backing kernel support which for
an Enterprise distro opens us up to bug reports.
For a while Vince was maintaining a page documenting breakage in the
perf_event ABI but last I checked it ended at V4.0. Not sure if he
just stopped updating, or that's where breakage ended :)
I know how Fedora maintains perf but I keep meaning to look at how
RHEL maintains it. As Michal said our code base is V5.14 for SLE15*
and due to the frequent code-refactoring in perf, backporting perf
userspace fixes for SLE is a real chore unless we agressively maintain
forward porting ("forklifting").
Tony
--
Tony Jones
SUSE Kernel Performance Team
next prev parent reply other threads:[~2023-04-19 22:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 9:23 Packaging bpftool and libbpf: GitHub or kernel? Shung-Hsi Yu
2023-04-13 9:50 ` Shung-Hsi Yu
2023-04-14 1:12 ` Quentin Monnet
2023-04-14 9:33 ` Michal Suchánek
2023-04-18 9:28 ` Shung-Hsi Yu
2023-04-13 11:00 ` Toke Høiland-Jørgensen
2023-04-19 10:54 ` Shung-Hsi Yu
2023-04-19 19:42 ` Andrii Nakryiko
2023-04-19 22:23 ` tonyj [this message]
2023-04-21 21:15 ` Vince Weaver
2023-04-20 19:18 ` Arnaldo Carvalho de Melo
2023-04-14 0:35 ` Quentin Monnet
2023-04-14 9:50 ` Michal Suchánek
2023-04-14 12:30 ` Quentin Monnet
2023-04-14 16:15 ` Michal Suchánek
2023-04-18 0:20 ` Andrii Nakryiko
2023-04-18 11:24 ` Michal Suchánek
2023-04-18 16:38 ` Andrii Nakryiko
2023-04-18 17:41 ` Michal Suchánek
2023-04-19 14:14 ` Shung-Hsi Yu
2023-04-19 19:52 ` Andrii Nakryiko
2023-04-19 21:23 ` Toke Høiland-Jørgensen
2023-04-19 23:42 ` Andrii Nakryiko
2023-04-20 14:46 ` Toke Høiland-Jørgensen
2023-04-20 21:39 ` Andrii Nakryiko
2023-04-28 9:13 ` Shung-Hsi Yu
2023-04-28 21:15 ` Andrii Nakryiko
2023-04-19 19:35 ` Andrii Nakryiko
2023-04-18 12:22 ` Dave Thaler
2023-04-18 0:00 ` Andrii Nakryiko
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=ZEBp6C9zqDnM1PfT@suse.de \
--to=tonyj@suse.de \
--cc=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jakub@cloudflare.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=msuchanek@suse.de \
--cc=quentin@isovalent.com \
--cc=shung-hsi.yu@suse.com \
--cc=toke@redhat.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).