From: Andrew Jones <andrew.jones@linux.dev>
To: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org
Cc: atishp@rivosinc.com, jamestiotio@gmail.com
Subject: [kvm-unit-tests PATCH 1/4] riscv: Bump NR_CPUS to 256
Date: Wed, 23 Oct 2024 15:21:32 +0200 [thread overview]
Message-ID: <20241023132130.118073-7-andrew.jones@linux.dev> (raw)
In-Reply-To: <20241023132130.118073-6-andrew.jones@linux.dev>
Besides a bit more memory used for the .bss section, where there are
NR_CPUS sized arrays, and a tiny bit more stack used by functions
with cpumasks on their stacks, then there's no harm in bumping
NR_CPUS. Bump it to 256, which should cover us for quite a while.
Signed-off-by: Andrew Jones <andrew.jones@linux.dev>
---
lib/riscv/asm/setup.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/riscv/asm/setup.h b/lib/riscv/asm/setup.h
index a13159bfe395..a031ebe7d762 100644
--- a/lib/riscv/asm/setup.h
+++ b/lib/riscv/asm/setup.h
@@ -4,7 +4,7 @@
#include <libcflat.h>
#include <asm/processor.h>
-#define NR_CPUS 16
+#define NR_CPUS 256
extern struct thread_info cpus[NR_CPUS];
extern int nr_cpus;
extern uint64_t timebase_frequency;
--
2.47.0
next prev parent reply other threads:[~2024-10-23 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 13:21 [kvm-unit-tests PATCH 0/4] riscv: A few SMP fixes Andrew Jones
2024-10-23 13:21 ` Andrew Jones [this message]
2024-10-23 13:21 ` [kvm-unit-tests PATCH 2/4] riscv: Filter unmanaged harts from present mask Andrew Jones
2024-10-23 13:21 ` [kvm-unit-tests PATCH 3/4] riscv: Fix secondary_entry Andrew Jones
2024-10-23 13:21 ` [kvm-unit-tests PATCH 4/4] riscv: Rework smp_boot_secondary Andrew Jones
2024-11-11 14:37 ` [kvm-unit-tests PATCH 0/4] riscv: A few SMP fixes Andrew Jones
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=20241023132130.118073-7-andrew.jones@linux.dev \
--to=andrew.jones@linux.dev \
--cc=atishp@rivosinc.com \
--cc=jamestiotio@gmail.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.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