From: "srinuvasan.a via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: srinuvasan <srinuvasan.a@siemens.com>
Subject: [PATCH] meta/classes-recipe/linux-kselftest: remove forced ISAR_CROSS_COMPILE = "0"
Date: Thu, 11 Dec 2025 09:21:56 +0530 [thread overview]
Message-ID: <20251211035156.6941-1-srinuvasan.a@siemens.com> (raw)
From: srinuvasan <srinuvasan.a@siemens.com>
Removing the forced ISAR_CROSS_COMPILE = "0" improves kselftest build performance.
When cross-compilation is disabled, kselftests are executed under
QEMU emulated environment for foreign architectures, which significantly increases build time.
By dropping this override, ISAR can correctly enable or disable cross-compilation
based on the target architecture, resulting in much faster builds for non-native architectures.
Note: The memfd test case passes under both native and cross builds.
If you observe inconsistencies in other test cases,
they should be investigated and addressed in the upstream kselftest framework.
Signed-off-by: srinuvasan <srinuvasan.a@siemens.com>
---
meta/classes-recipe/linux-kselftest.bbclass | 19 +++++++------------
1 file changed, 7 insertions(+), 12 deletions(-)
diff --git a/meta/classes-recipe/linux-kselftest.bbclass b/meta/classes-recipe/linux-kselftest.bbclass
index ec2d267e..67165683 100644
--- a/meta/classes-recipe/linux-kselftest.bbclass
+++ b/meta/classes-recipe/linux-kselftest.bbclass
@@ -8,11 +8,6 @@
inherit dpkg
-# Some test-cases like memfd compilation failed in cross-compilation.
-# Force native compilation for now to have consistent output across
-# ISAR native/cross compilation setups.
-ISAR_CROSS_COMPILE = "0"
-
DESCRIPTION ?= "Kernel selftests from Linux kernel ${PV}"
DEBIAN_BUILD_DEPENDS ?= " \
@@ -20,13 +15,13 @@ DEBIAN_BUILD_DEPENDS ?= " \
flex, \
bison, \
${@ 'fuse' if d.getVar('BASE_DISTRO_CODENAME') in ['bullseye', 'buster'] else 'fuse3'}, \
- libelf-dev:native, \
- libcap-ng-dev:native, \
- libpopt-dev:native, \
- libcap-dev:native, \
- libmount-dev:native, \
- libfuse-dev:native, \
- libmnl-dev:native, \
+ libelf-dev, \
+ libcap-ng-dev, \
+ libpopt-dev, \
+ libcap-dev, \
+ libmount-dev, \
+ libfuse-dev, \
+ libmnl-dev, \
pkg-config, \
clang:native, \
llvm:native, \
--
2.39.5
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20251211035156.6941-1-srinuvasan.a%40siemens.com.
next reply other threads:[~2025-12-11 3:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 3:51 srinuvasan.a via isar-users [this message]
2025-12-16 7:29 ` Anton Mikanovich
2025-12-16 8:26 ` 'MOESSBAUER, Felix' via isar-users
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=20251211035156.6941-1-srinuvasan.a@siemens.com \
--to=isar-users@googlegroups.com \
--cc=srinuvasan.a@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