[Bug 1840847] [NEW] cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

>From bug:

https://bugs.launchpad.net/bugs/1840511

clockhouse builds test started failing because of the presence of stderr
whenever using the function:

cpuinfo_linux_get_max_processors_count(void)

>From cpuid library.

This happens because:

----

#if defined(__ANDROID__) && !defined(CPU_SETSIZE)
    /*
     * Android NDK headers before platform 21 do not define CPU_SETSIZE,
     * so we hard-code its value, as defined in platform 21 headers
     */
    #if defined(__LP64__)
        static const uint32_t default_max_processors_count = 1024;
    #else
        static const uint32_t default_max_processors_count = 32;
    #endif
#else
    static const uint32_t default_max_processors_count = CPU_SETSIZE;
#endif

----

#if !defined(__ANDROID__)
    /*
     * sched.h is only used for CPU_SETSIZE constant.
     * Android NDK headers before platform 21 do have this constant in sched.h
     */
    #include <sched.h>
#endif

----

and resolving includes:

x86_64-linux-gnu/bits/cpu-set.h:

/* Size definition for CPU sets. */
#define __CPU_SETSIZE 1024

----

And the warning:

Warning in cpuinfo: kernel_max value of 8191 parsed from
/sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023

Will always be displayed in Ubuntu OS, when it should NOT (does not make
any sense to trigger a warning for something that can't be changed).

FOR THE KERNEL TEAM:

Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in
using 8192 max CPUs ?

** Affects: cpuinfo (Ubuntu)
     Importance: Medium
     Assignee: Rafael David Tinoco (rafaeldtinoco)
         Status: In Progress

** Affects: linux (Ubuntu)
     Importance: Low
         Status: Confirmed


** Tags: patch
-- 
cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
https://bugs.launchpad.net/bugs/1840847
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.