All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Ross Burton <ross@burtonini.com>
Cc: Randy Witt <randy.e.witt@linux.intel.com>,
	 Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	 Alexander Kanavin <alex.kanavin@gmail.com>
Subject: Re: [OE-core] RFC: Upgrading rt-tests requires numactl
Date: Wed, 23 Sep 2020 23:00:21 -0700	[thread overview]
Message-ID: <CAMKF1spFrLCVpwqeWkhys5K4r8vav6GFpFNobwkRZW3Mt=NOUA@mail.gmail.com> (raw)
In-Reply-To: <CAAnfSTsTXqEXVcoL+bdCU8wyRRSs_XL2HqQ0jiMCLrRNPOWEdg@mail.gmail.com>

On Wed, Sep 23, 2020 at 2:40 PM Ross Burton <ross@burtonini.com> wrote:
>
> On Wed, 23 Sep 2020 at 18:23, Randy Witt <randy.e.witt@linux.intel.com> wrote:
> > Another issue is that ARM is removed from COMPATIBLE_HOST in
> > http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/numactl/numactl_git.bb?h=master#n27.
> > This may be for legacy reasons, but libnuma can be installed on most
> > distributions running on an ARM host. Regardless, it would need to be changed to
> > allow for rt-tests on ARM.
>
> Yeah, that's probably very old.
>
> $ lscpu
> Architecture:                    aarch64
> CPU op-mode(s):                  64-bit
> Byte Order:                      Little Endian
> CPU(s):                          256
> On-line CPU(s) list:             0-255
> Thread(s) per core:              4
> Core(s) per socket:              32
> Socket(s):                       2
> NUMA node(s):                    2
>
> The recipe has done that since it was added, so I'd call this
> historical and just delete it.

question is not aarch64 but arm (32bit) and I think answer is still no for arm.

>
> Ross
>
> 
>

  reply	other threads:[~2020-09-24  6:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 17:22 RFC: Upgrading rt-tests requires numactl Randy Witt
2020-09-23 17:31 ` [OE-core] " Richard Purdie
2020-09-23 21:40 ` Ross Burton
2020-09-24  6:00   ` Khem Raj [this message]
2020-09-28 21:28     ` Randy Witt

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='CAMKF1spFrLCVpwqeWkhys5K4r8vav6GFpFNobwkRZW3Mt=NOUA@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.e.witt@linux.intel.com \
    --cc=ross@burtonini.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.