From: "tip-bot2 for Alexey Dobriyan" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: smp/core] cpu: Mark cpu_possible_mask as __ro_after_init
Date: Mon, 19 Feb 2024 17:16:04 -0000 [thread overview]
Message-ID: <170836296444.398.15393665833810225842.tip-bot2@tip-bot2> (raw)
In-Reply-To: <41cd78af-92a3-4f23-8c7a-4316a04a66d8@p183>
The following commit has been merged into the smp/core branch of tip:
Commit-ID: da92df490eeab7a97a3390ff32e0ae091e0dc2eb
Gitweb: https://git.kernel.org/tip/da92df490eeab7a97a3390ff32e0ae091e0dc2eb
Author: Alexey Dobriyan <adobriyan@gmail.com>
AuthorDate: Mon, 05 Feb 2024 13:01:19 +03:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Mon, 19 Feb 2024 18:05:47 +01:00
cpu: Mark cpu_possible_mask as __ro_after_init
cpu_possible_mask is by definition "cpus which could be hotplugged without
reboot". It's a property which is fixed after kernel enumerates the
hardware configuration.
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/41cd78af-92a3-4f23-8c7a-4316a04a66d8@p183
---
kernel/cpu.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
index ad7d0b0..7b36b3a 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -3106,10 +3106,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};
#else
-struct cpumask __cpu_possible_mask __read_mostly;
+struct cpumask __cpu_possible_mask __ro_after_init;
#endif
EXPORT_SYMBOL(__cpu_possible_mask);
next prev parent reply other threads:[~2024-02-19 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 10:01 [PATCH] cpu: mark " Alexey Dobriyan
2024-02-19 17:16 ` tip-bot2 for Alexey Dobriyan [this message]
2024-02-22 6:00 ` Guenter Roeck
2024-02-22 10:26 ` Alexey Dobriyan
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=170836296444.398.15393665833810225842.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 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®