All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Rogers <irogers@google.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: debian-kernel@lists.debian.org,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	waldi@debian.org,
	linux-perf-users <linux-perf-users@vger.kernel.org>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>
Subject: Re: Getting the latest and greatest Linux perf features on every Debian kernel
Date: Mon, 9 Jan 2023 17:32:11 -0800	[thread overview]
Message-ID: <CAP-5=fUcc-SmxqgNCnqNAc=adGdzK31eQtv8XKQLt8v4EtLguQ@mail.gmail.com> (raw)
In-Reply-To: <62af20e156e799350b0281b7769442c4f1d414a3.camel@decadent.org.uk>

On Mon, Dec 26, 2022 at 11:15 AM Ben Hutchings <ben@decadent.org.uk> wrote:
>
> On Thu, 2022-12-22 at 17:43 -0800, Ian Rogers wrote:
> [...]
> > I had a few things to ask wrt this thread and getting the best
> > possible Debian experience:
> >  - in Linux 6.2 the libtraceevent will need to become an external
> > library dependency
>
> This shouldn't be a problem; it's already packaged separately in Debian
> and we can build-depend on that.
>
> >  - are there issues with debuginfod/zstd enablement? libbfd has
> > licensing issues. libcrypto is only used by the JIT support, but still
> > may be nice to enable.
>
> - debuginfod is licensed under GPLv3+, so has the same issue as libbfd
> - libzstd is licensed under GPLv2 (with most of its code also
> permissively licensed)
> - libcrypto is now licensed under Apache 2.0, which is not compatible
> with GPLv2
>
> So I think only libzstd can be enabled in official packages.
>
> [...]
> >  - are there some residual wrapper artifacts in the package, for example:
> > ```
> > $ dpkg -L linux-perf
> > /.
> > /usr
> > /usr/bin
> > /usr/bin/perf
> > package diverts others to: /usr/bin/perf.wrapper
> > ...
> > package diverts others to: /usr/share/bash-completion/completions/perf.wrapper
> > ...
> > package diverts others to: /usr/share/man/man1/perf.wrapper.1.gz
> > ...
> > ```
> [...]
>
> These diversions are present to avoid conflicts with the wrappers in
> older versions of linux-base.  We can remove them after the next stable
> release.
>
> Ben.

Thanks again Ben! With the releases, the plan is to follow the kernel
releases? We could potentially be more aggressive with the perf tool
given its backward compatibility. That would benefit people using
older kernels who want the latest perf tool bug fixes and features.

Ian

> --
> Ben Hutchings
> Klipstein's 4th Law of Prototyping and Production:
>                                A fail-safe circuit will destroy others.

  reply	other threads:[~2023-01-10  1:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12  6:34 Getting the latest and greatest Linux perf features on every Debian kernel Ian Rogers
2021-11-12 14:39 ` 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 [this message]
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=fUcc-SmxqgNCnqNAc=adGdzK31eQtv8XKQLt8v4EtLguQ@mail.gmail.com' \
    --to=irogers@google.com \
    --cc=acme@kernel.org \
    --cc=ben@decadent.org.uk \
    --cc=debian-kernel@lists.debian.org \
    --cc=jolsa@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=waldi@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.