public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Arjunan, Srinu" <srinuvasan.a@siemens.com>
Subject: Re: [PATCH] meta/classes-recipe/linux-kselftest: remove forced ISAR_CROSS_COMPILE = "0"
Date: Tue, 16 Dec 2025 08:26:43 +0000	[thread overview]
Message-ID: <39c46a7db30b04df0c5acb24f5feff3e8bf0f11c.camel@siemens.com> (raw)
In-Reply-To: <54b747f1-f8a9-4196-916b-7ec346dd40ba@ilbers.de>

On Tue, 2025-12-16 at 09:29 +0200, Anton Mikanovich wrote:
> 11/12/2025 05:51, srinuvasan.a via isar-users wrote:
> > 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>
> Applied to next, thanks.

Thanks for addressing this. This also was one of my findings regarding
inconsistencies in the testsuite (kselftests where part of the cross
test, but they were not cross). That's now consistent again.

Felix

-- 
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/39c46a7db30b04df0c5acb24f5feff3e8bf0f11c.camel%40siemens.com.

      reply	other threads:[~2025-12-16  8:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11  3:51 srinuvasan.a via isar-users
2025-12-16  7:29 ` Anton Mikanovich
2025-12-16  8:26   ` 'MOESSBAUER, Felix' via isar-users [this message]

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=39c46a7db30b04df0c5acb24f5feff3e8bf0f11c.camel@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.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