From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: isar-users@googlegroups.com
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v2 0/2] RFC: Package perf from linux kernel tools
Date: Thu, 21 Jan 2021 11:52:22 +0100 [thread overview]
Message-ID: <20210121105224.26285-1-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <AM0PR10MB1939687D1ABFBE66DAAB702689A20@AM0PR10MB1939.EURPRD10.PROD.OUTLOOK.COM>
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?
Best regards,
Felix
Felix Moessbauer (2):
feat: package linux-perf-<version> in kernel recipe
feat: package perf for 5.4 kernels
.../linux/files/debian/control.tmpl | 31 +++++
.../files/debian/rules.d/tools/perf/Makefile | 60 +++++++++
.../linux/files/debian/rules.tmpl | 18 ++-
.../perf/4.19/tools-perf-install.patch | 58 +++++++++
.../perf/4.19/tools-perf-version.patch | 119 ++++++++++++++++++
.../patches/perf/5.4/tools-perf-install.patch | 51 ++++++++
.../patches/perf/5.4/tools-perf-python.patch | 16 +++
.../patches/perf/5.4/tools-perf-version.patch | 111 ++++++++++++++++
meta/recipes-kernel/linux/linux-custom.inc | 11 +-
meta/recipes-kernel/linux/linux-tools.inc | 67 ++++++++++
10 files changed, 538 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-kernel/linux/files/debian/rules.d/tools/perf/Makefile
create mode 100644 meta/recipes-kernel/linux/files/patches/perf/4.19/tools-perf-install.patch
create mode 100644 meta/recipes-kernel/linux/files/patches/perf/4.19/tools-perf-version.patch
create mode 100644 meta/recipes-kernel/linux/files/patches/perf/4.19/tools-perf-version.patch
create mode 100644 meta/recipes-kernel/linux/files/patches/perf/5.4/tools-perf-install.patch
create mode 100644 meta/recipes-kernel/linux/files/patches/perf/5.4/tools-perf-python.patch
create mode 100644 meta/recipes-kernel/linux/linux-tools.inc
--
2.20.1
next prev parent reply other threads:[~2021-01-21 10:52 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 ` Felix Moessbauer [this message]
2021-01-21 11:56 ` [PATCH v2 0/2] " Jan Kiszka
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=20210121105224.26285-1-felix.moessbauer@siemens.com \
--to=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