From: Jan Beulich <jbeulich@suse.com>
To: Ian Jackson <iwj@xenproject.org>
Cc: "Connor Davis" <connojdavis@gmail.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"Dario Faggioli" <dfaggioli@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 0/2][4.15?] fix build when NR_CPUS == 1
Date: Mon, 1 Mar 2021 09:33:25 +0100 [thread overview]
Message-ID: <8a1adfcf-fb9b-ec44-5222-25016a031ad4@suse.com> (raw)
In-Reply-To: <ad59eaf9-747c-f60e-16b7-121c9f86a1e0@suse.com>
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
prev parent reply other threads:[~2021-03-01 8:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 8:27 [PATCH 0/2][4.15?] fix build when NR_CPUS == 1 Jan Beulich
2021-03-01 8:30 ` [PATCH 1/2][4.15?] sched: " Jan Beulich
2021-03-01 15:57 ` Ian Jackson
2021-03-01 17:50 ` Dario Faggioli
2021-03-01 8:31 ` [PATCH 2/2][4.15?] x86: " Jan Beulich
2021-03-01 14:01 ` Roger Pau Monné
2021-03-01 15:14 ` Jan Beulich
2021-03-01 18:00 ` Roger Pau Monné
2021-03-02 9:59 ` Jan Beulich
2021-03-02 10:57 ` Roger Pau Monné
2021-03-02 11:18 ` Jan Beulich
2021-03-01 16:03 ` Ian Jackson
2021-03-02 10:02 ` Jan Beulich
2021-03-02 12:28 ` Ian Jackson
2021-03-02 13:37 ` Jan Beulich
2021-03-01 8:33 ` Jan Beulich [this message]
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=8a1adfcf-fb9b-ec44-5222-25016a031ad4@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=connojdavis@gmail.com \
--cc=dfaggioli@suse.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.