From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
To: <isar-users@googlegroups.com>
Cc: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: [RFC Kernel PATCH 0/1] support creation of linux-perf packages
Date: Wed, 28 Aug 2019 09:17:32 +0200 [thread overview]
Message-ID: <1566976653-174-1-git-send-email-Cedric_Hombourger@mentor.com> (raw)
Hello all,
As you may know we are using the kernel "make deb-pkg" infrastructure to build and
package our custom kernels. When we upgrade the kernel to a more recent version than
Debian (e.g. when targeting use of 5.x kernel while Debian 10 is on 4.19), we lose
support for perf since the created rootfs will not have a perf binary matching the
kernel version we are running (/usr/bin/perf will be looking for perf_5.3 if you are
running a 5.3 kernel). This patch modifies the builddeb and mkdebian scripts from the
Linux kernel tree to generate linux-perf packages with a structure matching Debian's
I would anticipate that our build-kernel.sh script would be modified to build/package
the kernel with "make deb-pkg KDEB_PERF=1" (should cause no harm for older kernel
builds).
I would appreciate your review comments before submitting this to the Linux kernel
folks
TIA!
Cedric Hombourger (1):
builddeb: support creation of linux-perf packages
scripts/package/builddeb | 32 ++++++++++++++++++++++++++++++++
scripts/package/mkdebian | 26 ++++++++++++++++++++++++++
2 files changed, 58 insertions(+)
--
2.11.0
next reply other threads:[~2019-08-28 7:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 7:17 Cedric Hombourger [this message]
2019-08-28 7:17 ` [RFC Kernel PATCH 1/1] builddeb: " Cedric Hombourger
2019-08-30 13:58 ` Henning Schild
2019-09-03 8:01 ` Cedric Hombourger
2019-09-03 14:59 ` Baurzhan Ismagulov
2019-09-03 15:19 ` Jan Kiszka
2019-09-04 8:37 ` 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=1566976653-174-1-git-send-email-Cedric_Hombourger@mentor.com \
--to=cedric_hombourger@mentor.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