From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] package/rt-tests: add support to build without numactl
Date: Mon, 28 Dec 2020 22:38:38 +0100 [thread overview]
Message-ID: <20201228223838.4e4823cc@windsurf.home> (raw)
In-Reply-To: <20201227212832.GA18525@arbad>
On Sun, 27 Dec 2020 22:28:33 +0100
Andreas Klinger <ak@it-klinger.de> wrote:
> rt-tests don't show up in config menu and is not build if
> BR2_PACKAGE_NUMACTL_ARCH_SUPPORTS is not available on the target
> architecture. In such a case numactl is also not available what applies for
> most small embedded targets.
>
> This dependency was introduced with commit 7f50cbfb800e
> ("package/rt-tests: bump to version 1.8")
>
> But rt-tests can also be build without numactl when passing NUMA=0 to make.
> This possibility is documented on
> https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/rt-tests
>
> Change Config.in and makefile to build without numactl by passing NUMA=0.
>
> Changes in v4:
> - make numactl an optional dependency.
>
> Changes in v3:
> - make use of numactl dependency only if BR2_PACKAGE_NUMACTL_ARCH_SUPPORTS
> is set.
>
> Changes in v2:
> - Thanks to the review of Baruch patch is simplified and directly disabling
> NUMA by querying for !BR2_PACKAGE_NUMACTL_ARCH_SUPPORTS.
>
> Signed-off-by: Andreas Klinger <ak@it-klinger.de>
> ---
> package/rt-tests/Config.in | 3 ---
> package/rt-tests/rt-tests.mk | 8 +++++++-
> 2 files changed, 7 insertions(+), 4 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-12-28 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 21:28 [Buildroot] [PATCH v4] package/rt-tests: add support to build without numactl Andreas Klinger
2020-12-28 21:38 ` Thomas Petazzoni [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=20201228223838.4e4823cc@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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