From: Alexey Dobriyan <adobriyan@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpu: mark cpu_possible_mask as __ro_after_init
Date: Thu, 22 Feb 2024 13:26:44 +0300 [thread overview]
Message-ID: <f076212f-9b2a-4eb5-980b-3043e6dd57aa@p183> (raw)
In-Reply-To: <a1fafb71-cbd9-4d0b-8c3c-2b69be97db3e@roeck-us.net>
On Wed, Feb 21, 2024 at 10:00:26PM -0800, Guenter Roeck wrote:
> On Mon, Feb 05, 2024 at 01:01:19PM +0300, Alexey Dobriyan wrote:
> > cpu_possible_mask is by definition "cpus which could be hotplugged
> > without reboot" -- property which is fixed after kernel enumerates
> > motheboard capabilities and hardware configuration.
> >
> > Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> > ---
> >
> > kernel/cpu.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > --- a/kernel/cpu.c
> > +++ b/kernel/cpu.c
> > @@ -3107,10 +3107,10 @@ const DECLARE_BITMAP(cpu_all_bits, NR_CPUS) = CPU_BITS_ALL;
> > EXPORT_SYMBOL(cpu_all_bits);
> >
> > #ifdef CONFIG_INIT_ALL_POSSIBLE
> > -struct cpumask __cpu_possible_mask __read_mostly
> > +struct cpumask __cpu_possible_mask __ro_after_init;
> > = {CPU_BITS_ALL};
>
> I guess you didn't compile test this code.
On parisc, no. Oh well.
> > #else
> > -struct cpumask __cpu_possible_mask __read_mostly;
> > +struct cpumask __cpu_possible_mask __ro_after_init;
next prev parent reply other threads:[~2024-02-22 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 10:01 Alexey Dobriyan
2024-02-19 17:16 ` [tip: smp/core] cpu: Mark " tip-bot2 for Alexey Dobriyan
2024-02-22 6:00 ` [PATCH] cpu: mark " Guenter Roeck
2024-02-22 10:26 ` Alexey Dobriyan [this message]
2024-02-22 11:19 ` [PATCH v2] " Alexey Dobriyan
2024-03-27 18:10 ` Jonathan Cameron
2024-03-27 18:36 ` Guenter Roeck
2024-04-03 13:43 ` Jonathan Cameron
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=f076212f-9b2a-4eb5-980b-3043e6dd57aa@p183 \
--to=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®