From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Felix Moessbauer" <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/2] RFC: Package perf from linux kernel tools
Date: Thu, 21 Jan 2021 12:56:28 +0100 [thread overview]
Message-ID: <e569b683-0306-3e22-1d3a-9b73ed38afd1@siemens.com> (raw)
In-Reply-To: <20210121105224.26285-1-felix.moessbauer@siemens.com>
On 21.01.21 11:52, [ext] Felix Moessbauer wrote:
> Hi,
>
> thanks for your input that is reflected in the following patchsets.
>
> Changes since v1:
>
> - package as part of kernel recipe
> - put python patch in dedicated commit
> - add support for 5.4 kernels
> - enable users to provide custom patches
>
> One pain point is still that we have to copy the patches
> from upstream debian. IMO it would be better to just fetch
> them, but then we would have to somehow map to a branch on
> salsa. Any recommendations?
>
The patches are targeting the kernel sources, right? Then upstream the
features that we are missing from the kernel. After that, we will "only"
have to deal with a shrinking number of backports for which we can
provide a view references. When keeping the patches downstream, we will
soon have a huge number of additional patches to carry - or perf support
will even bitrot again with newer kernels.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-01-21 11:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 12:41 [PATCH 0/1] " Felix Moessbauer
2021-01-19 12:41 ` [PATCH 1/1] " Felix Moessbauer
2021-01-19 16:31 ` Baurzhan Ismagulov
2021-01-20 15:23 ` Moessbauer, Felix
2021-01-20 15:26 ` Henning Schild
2021-01-21 10:52 ` [PATCH v2 0/2] " Felix Moessbauer
2021-01-21 11:56 ` Jan Kiszka [this message]
2021-01-21 15:00 ` Moessbauer, Felix
2021-01-21 16:35 ` Jan Kiszka
2021-02-09 8:58 ` Anton Mikanovich
2021-02-17 10:18 ` Baurzhan Ismagulov
2021-01-21 10:52 ` [PATCH 1/2] feat: package linux-perf-<version> in kernel recipe Felix Moessbauer
2021-02-17 10:28 ` Baurzhan Ismagulov
2021-02-18 8:01 ` Moessbauer, Felix
2021-02-18 8:28 ` Jan Kiszka
2021-04-22 9:52 ` Anton Mikanovich
2021-04-27 9:24 ` [RFC v2 0/2] " Felix Moessbauer
2021-04-27 9:24 ` [PATCH v2 1/2] RFC: Package perf from linux kernel tools Felix Moessbauer
2021-04-27 9:24 ` [PATCH v2 2/2] Add wrapper to load correct python perf module based on kernel Felix Moessbauer
2021-01-21 10:52 ` [PATCH 2/2] feat: add and package python bindings for perf Felix Moessbauer
2021-01-20 11:12 ` [PATCH 0/1] RFC: Package perf from linux kernel tools Henning Schild
2021-01-20 11:21 ` Henning Schild
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=e569b683-0306-3e22-1d3a-9b73ed38afd1@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.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