public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>
Cc: <isar-users@googlegroups.com>, <adriaan.schmidt@siemens.com>,
	<jan.kiszka@siemens.com>,
	Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: Re: [PATCH 0/1] RFC: Package perf from linux kernel tools
Date: Wed, 20 Jan 2021 12:12:52 +0100	[thread overview]
Message-ID: <20210120121252.12fe7d43@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20210119124157.12662-1-felix.moessbauer@siemens.com>

Hi,

i think perf support in general is something we clearly want to have.
As far as i remember Cedric might be interested as well, adding him to
CC.

Maybe a split into the basic support and the python bindings is useful.
Because those python bindings are pretty different from upstream, and
they probably deserve a test-package if we agree that we want to
support them in isar.

Henning

Am Tue, 19 Jan 2021 13:41:57 +0100
schrieb Felix Moessbauer <felix.moessbauer@siemens.com>:

> Hi all,
> 
> this patch adds support to build the linux-perf<version> package
> that includes the kernel specific perf tooling.
> 
> During implementation I tried two different approaches:
> 1. package as part of the kernel receipt (as Debian does)
> 2. package as a regular package (similar to how the kselftest is
> packaged)
> 
> This RFC implements approach 2 but tries to be as close as possible
> to the Debian upstream packaging.
> By that, we use the same patches from Debian upstream to build our
> package. Note, that these are dependent on the exact kernel version.
> Here, I used the latest available bugfix version from upstream
> (4.19.160). Perf should then be compatible with 4.19 kernels (only
> partially tested).
> 
> A major obstacle in implementing approach 1 was that the patches for
> linux-tools are not trivial and have to match with the corresponding
> kernel version. Writing that in a way that works for various kernel
> versions was something I was not able to accomplish.
> Hence, I decided that it might be better to avoid that much
> complexity in the kernel receipt. Most users might not need the tools
> anyways, but probably a custom kernel.
> 
> Finally, this patch also builds the kernel specific python bindings
> of perf. This patch has already been sent upstream, but is not yet
> integrated in Debian. For reference, see here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860957
> 
> Best regards,
> Felix Mößbauer
> 
> Felix Moessbauer (1):
>   RFC: Package perf from linux kernel tools
> 
>  .../recipes-kernel/linux-perf/files/rules     |  53 ++++++++
>  .../linux-perf/files/tools-perf-install.patch |  58 +++++++++
>  .../linux-perf/files/tools-perf-python.patch  |  55 ++++++++
>  .../linux-perf/files/tools-perf-version.patch | 119
> ++++++++++++++++++ .../linux-perf/linux-perf-4.19_4.19.160.bb    |
> 11 ++ .../recipes-kernel/linux-perf/linux-perf.inc  |  46 +++++++
>  6 files changed, 342 insertions(+)
>  create mode 100644 meta-isar/recipes-kernel/linux-perf/files/rules
>  create mode 100644
> meta-isar/recipes-kernel/linux-perf/files/tools-perf-install.patch
> create mode 100644
> meta-isar/recipes-kernel/linux-perf/files/tools-perf-python.patch
> create mode 100644
> meta-isar/recipes-kernel/linux-perf/files/tools-perf-version.patch
> create mode 100644
> meta-isar/recipes-kernel/linux-perf/linux-perf-4.19_4.19.160.bb
> create mode 100644 meta-isar/recipes-kernel/linux-perf/linux-perf.inc
> 


  parent reply	other threads:[~2021-01-20 11:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 12:41 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
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 ` Henning Schild [this message]
2021-01-20 11:21 ` [PATCH 0/1] RFC: Package perf from linux kernel tools 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=20210120121252.12fe7d43@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=Cedric_Hombourger@mentor.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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