linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Henri Roosen <henriroosen@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: rt-test not available for arm in buildroot
Date: Fri, 9 Apr 2021 12:11:25 -0400 (EDT)	[thread overview]
Message-ID: <d946ec97-1794-924d-bd37-1c131ebcdfeb@redhat.com> (raw)
In-Reply-To: <CANKLDmuMdmjrHHqkPs01Xg14u-m4GrXfLFBpXdniegCg=xLn2g@mail.gmail.com>



On Fri, 9 Apr 2021, Henri Roosen wrote:

> Hi John,
> I was using buildroot for creating the rootfs for armv7 based systems. Previously I was able to select and include the rt-tests, however, the current buildroot-lts (2021.02.x) doesn't
> allow this anymore.
> 
> Buildroot doesn't build any NUMA stuff for arm. The rt-tests build seems to require NUMA, even though not needed for arm.
> 
> What is your suggestion / strategy to fix rt-test build without any NUMA stuff available at compile time?
> 
> Thanks,
> Henri
> 
> 

Previously numalibs (numactl-devel) was required at build time but
it was not required at runtime for the kind of situation you were describing.

There were some patches that were recently integrated that made the 
assumption that numa libs were always available. The patches had some
nice clean-ups of the numalib calls but unfortunately deleted
the equivalent routines for when numa was not available.

I tried to revert the minimum number of patches possible to go back
to the old situation, but some more work is needed to put back this old 
functionality.

I am aware of this siutation and am working on it. If you want to take a 
look at the old code before these changes and help with some patches
to fix this, that would be appreciated.

If you decide to look at this, I don't just want the old versions
of the functions, placed in the new location, but would like to retain
the improvements in the numa code as well.

Thanks

John

           reply	other threads:[~2021-04-09 16:11 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CANKLDmuMdmjrHHqkPs01Xg14u-m4GrXfLFBpXdniegCg=xLn2g@mail.gmail.com>]

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=d946ec97-1794-924d-bd37-1c131ebcdfeb@redhat.com \
    --to=jkacur@redhat.com \
    --cc=henriroosen@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).