fix build when NR_CPUS == 1

[PATCH 0/2][4.15?] fix build when NR_CPUS == 1

Jan Beulich posted 2 patches 3 years, 1 month ago

Download series mbox

Test gitlab-ci passed

Patches applied successfully (tree, apply log)
git fetch https://gitlab.com/xen-project/patchew/xen tags/patchew/ad59eaf9-747c-f60e-16b7-121c9f86a1e0@suse.com

Expand all Fold all

[PATCH 0/2][4.15?] fix build when NR_CPUS == 1

Posted by Jan Beulich 3 years, 1 month ago

While we've long done away with CONFIG_SMP, we still allow
CONFIG_NR_CPUS to be set to 1. Hence at least randconfig builds
may fail, and the first of the two issues addressed was actually
observed in the RISC-V bring-up work. I didn't check whether Arm
would also have issues like these.

1: sched: fix build when NR_CPUS == 1
2: x86: fix build when NR_CPUS == 1

Jan

Re: [PATCH 0/2][4.15?] fix build when NR_CPUS == 1

Posted by Jan Beulich 3 years, 1 month ago

On 01.03.2021 09:27, Jan Beulich wrote:
> While we've long done away with CONFIG_SMP, we still allow
> CONFIG_NR_CPUS to be set to 1. Hence at least randconfig builds
> may fail, and the first of the two issues addressed was actually
> observed in the RISC-V bring-up work. I didn't check whether Arm
> would also have issues like these.
> 
> 1: sched: fix build when NR_CPUS == 1
> 2: x86: fix build when NR_CPUS == 1

I've tagged this with a question mark because on one hand such
configurations are unusual and hence unlikely to be overly
relevant for the release. Otoh randconfig failures would better
be avoided.

Jan