All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: meta-virtualization@yoctoproject.org
Subject: Re: [PATCH] libvirt: fix Nothing PROVIDES 'numactl' on ARM
Date: Tue, 21 May 2019 10:39:44 -0400	[thread overview]
Message-ID: <CADkTA4MbPAADy96fnMMDFPwDfMWeQ9vO=PRUx=Qu8xZHccLuTw@mail.gmail.com> (raw)
In-Reply-To: <1557936398-36529-1-git-send-email-hongxu.jia@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 2447 bytes --]

On Wed, May 15, 2019 at 12:07 PM Hongxu Jia <hongxu.jia@windriver.com>
wrote:

> ARM does not currently support NUMA, and defines COMPATIBLE_HOST in recipe
> numactl
>
> Since commit [b5b5def libvirt: add hook support] applied, it failed with
> Nothing PROVIDES 'numactl' on ARM BSP, not all BSP define var-KARCH but
> define var-TARGET_ARCH
>
> So check var-TARGET_ARCH, and add numactl to PACKAGECONFIG conditionally


> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
>  recipes-extended/libvirt/libvirt_5.3.0.bb | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/recipes-extended/libvirt/libvirt_5.3.0.bb
> b/recipes-extended/libvirt/libvirt_5.3.0.bb
> index 30bb44c..a949e8f 100644
> --- a/recipes-extended/libvirt/libvirt_5.3.0.bb
> +++ b/recipes-extended/libvirt/libvirt_5.3.0.bb
> @@ -189,9 +189,17 @@ PACKAGECONFIG ??= "qemu yajl openvz vmware vbox esx
> iproute2 lxc test \
>                     ${@bb.utils.contains('DISTRO_FEATURES', 'selinux',
> 'selinux audit libcap-ng', '', d)} \
>                     ${@bb.utils.contains('DISTRO_FEATURES', 'xen',
> 'libxl', '', d)} \
>                     ${@bb.utils.contains('DISTRO_FEATURES', 'x11',
> 'polkit', '', d)} \
> -                   ${@bb.utils.contains('KARCH', 'arm', '', 'numactl',
> d)} \
> +                   ${@support_numactl(d)} \
>                    "
>
> +def support_numactl(d):
> +    targetarch = d.getVar("TARGET_ARCH")
> +    # ARM does not currently support NUMA
> +    if targetarch.startswith("arm"):
> +        return ""
> +
> +    return "numactl"
> +
>

Checking TARGET_ARCH is definitely the right thing to use for this.

But out of curiosity, why can't we change it to work the same as the qemu
PACKAGECONFIG setting ?

i.e. PACKAGECONFIG_remove_arm = "numactl"
PACKAGECONFIG_remove_arm64 = "numactl"

(or whatever the ARM64 target arch maps to).

Bruce



>  # qemu is NOT compatible with mips64
>  PACKAGECONFIG_remove_mipsarchn32 = "qemu"
>  PACKAGECONFIG_remove_mipsarchn64 = "qemu"
> --
> 2.7.4
>
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II

[-- Attachment #2: Type: text/html, Size: 4753 bytes --]

  reply	other threads:[~2019-05-21 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15 16:06 [PATCH] libvirt: fix Nothing PROVIDES 'numactl' on ARM Hongxu Jia
2019-05-21 14:39 ` Bruce Ashfield [this message]
2019-05-24 23:23   ` Mark Asselstine

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='CADkTA4MbPAADy96fnMMDFPwDfMWeQ9vO=PRUx=Qu8xZHccLuTw@mail.gmail.com' \
    --to=bruce.ashfield@gmail.com \
    --cc=hongxu.jia@windriver.com \
    --cc=meta-virtualization@yoctoproject.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 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.