From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6919450737082630144 X-Received: by 2002:a1c:2289:: with SMTP id i131mr4060190wmi.119.1611060168535; Tue, 19 Jan 2021 04:42:48 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:adf:a54b:: with SMTP id j11ls2712518wrb.3.gmail; Tue, 19 Jan 2021 04:42:47 -0800 (PST) X-Google-Smtp-Source: ABdhPJyPq2jyy/+9AmyUuXHZadJYq2nwxqOBDQbUfT7zRK80ZQKZTf/KmszcksoWvIy454aGCKeT X-Received: by 2002:adf:c40e:: with SMTP id v14mr4224514wrf.163.1611060167664; Tue, 19 Jan 2021 04:42:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611060167; cv=none; d=google.com; s=arc-20160816; b=YR818XpWzBkyCDMtQE7fKr2dEste/3GCUuv94KGP3QIX0UgxdJs+/56v0TqWEqyCp3 EswyMZV8ZB3HxZoTy0Vyf+zefYgizhmkkekieJuai4iVtyxFcvTund6OTkGofkkjcxxx bSbMDMLqbGrr0vOg3kFPUaxBB5dRTBBNt+In6ADCpK85RI1YozlVSFOVePzpBxpjPOAr KhQ9xCVU/T9Lgn/SCqiDh1u6xwqWIrq0y5YzyVaivku79B758+TocVjlATacSQZ38GIk 5AmlwJFSi+dgRXIZ8RHLQoWON2mStUa4csqW5zuODYYwQV2D2leTOGsf2RlAD+72Y0l9 ZyTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from; bh=NWVNJXhMJiCsogomk5V2C3x8lIVzAN9z5UwZ4sYTsRY=; b=s1EkpDy5RMQWlhioLYoR8I4O//TSv4HX5/PUaT1li0DSuEsk0qxrS7uKF1WQcQf1nr S9M1BdWGrEGfmTWqe1DNhsmGUAZl2zCbMbrvS9cXfFTQV94kOUzz1QoItVVaoWy0jOQe S3MtUWnBHMXL8KEEgRe2gs48sGMpf9hJEL+S28IDAZvvhUaEwTSFe/O5ZqeMs04D32TY cqzy1Wob2dDZN3XX15xZAaXEwEe3ytVoCfrIGTOVtV7jcUCKuq1KrIPvqWW9INBMoq6c 6dVQxfFQeu8A3vr5R3fmBi+zUtL8MnlpTwhY5OzYP2bLtxZCcH+Ul3heG/yqISoEn+Fx cI3g== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of felix.moessbauer@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=felix.moessbauer@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id o203si156216wma.0.2021.01.19.04.42.47 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Jan 2021 04:42:47 -0800 (PST) Received-SPF: pass (google.com: domain of felix.moessbauer@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of felix.moessbauer@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=felix.moessbauer@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id 10JCglFZ003906 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 19 Jan 2021 13:42:47 +0100 Received: from MD1T0KAC-VM.ad001.siemens.net (md1t0kac.ad001.siemens.net [139.25.0.7]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id 10JCgkbo025009; Tue, 19 Jan 2021 13:42:46 +0100 From: Felix Moessbauer To: isar-users@googlegroups.com Cc: Felix Moessbauer , adriaan.schmidt@siemens.com, henning.schild@siemens.com, jan.kiszka@siemens.com Subject: [PATCH 0/1] RFC: Package perf from linux kernel tools Date: Tue, 19 Jan 2021 13:41:57 +0100 Message-Id: <20210119124157.12662-1-felix.moessbauer@siemens.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-TUID: k1vdO1N2jbyf Hi all, this patch adds support to build the linux-perf 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 -- 2.20.1