linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Rogers <irogers@google.com>
To: debian-kernel@lists.debian.org,
	Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>, ben@decadent.org.uk
Subject: Getting the latest and greatest Linux perf features on every Debian kernel
Date: Thu, 11 Nov 2021 22:34:33 -0800	[thread overview]
Message-ID: <CAP-5=fW7La9ZNv8Z6LHRRNXne4+dWK6dR1ye2P=zETFELtK=fg@mail.gmail.com> (raw)

(Apologies, resending in plain-text to allow linux-perf-users to
follow along - the 1st e-mail bounced)

Hi,

Debian currently tries to match the Linux perf tool to the version of
the kernel that it is being run upon. Reaching out to Ben Hutchings,
he explained to me that this was done back in 2010 due to kernel and
Linux perf incompatibilities. This was likely the case, but it was a
bug in the Linux perf tool that should have been fixed. It is the goal
of the tool to be backward compatible. A problem with matching the
tool to the kernel version is that users miss out on new features and
fixes (this topic came up in a recent interview of the maintainer
Arnaldo Carvalho de Melo [1]).

Ben Hutchings informs me that making it so that Debian ships the
latest Linux perf tool requires updates both to the linux-base and
linux source packages. The Linux perf tool also has many other often
optional dependencies, like libunwind, libbpf, libpfm4, libtraceevent,
etc. In general, having the dependency will unlock more features.
Linux tools has its own copies of libbpf and libtraceevent, and so
these may pose some versioning issues.

I think it'd be great to get Debian shipping the latest version of
Linux perf for its users. Hopefully we can agree to change how Debian
packages perf currently and then work out the best way to package and
keep it up-to-date. I look forward to everyone's help and input.

Thanks in advance,
Ian Rogers

[1] https://youtu.be/aUDtN0qjxD0?t=5869

             reply	other threads:[~2021-11-12  6:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12  6:34 Ian Rogers [this message]
2021-11-12 14:39 ` Getting the latest and greatest Linux perf features on every Debian kernel Arnaldo Carvalho de Melo
2021-11-22  2:18   ` Ian Rogers
2021-11-22 12:54     ` Moessbauer, Felix
2021-11-22 16:57       ` Ian Rogers
2021-11-23  7:46         ` Moessbauer, Felix
2022-01-09 23:54     ` Ben Hutchings
2022-01-10 18:44       ` Arnaldo Carvalho de Melo
2022-12-23  1:43         ` Ian Rogers
2022-12-25 11:51           ` Andi Kleen
2022-12-26 16:12             ` Moessbauer, Felix
2022-12-26 19:15           ` Ben Hutchings
2023-01-10  1:32             ` Ian Rogers
2023-01-13 22:06               ` Ben Hutchings
2022-01-09 23:41   ` Ben Hutchings

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='CAP-5=fW7La9ZNv8Z6LHRRNXne4+dWK6dR1ye2P=zETFELtK=fg@mail.gmail.com' \
    --to=irogers@google.com \
    --cc=acme@kernel.org \
    --cc=ben@decadent.org.uk \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-perf-users@vger.kernel.org \
    /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).