* [PATCH] riscv: Fix NR_CPUS range conditions
@ 2022-11-26 6:15 Samuel Holland
2022-11-26 15:32 ` Conor Dooley
` (2 more replies)
0 siblings, 3 replies; 7+ messages in thread
From: Samuel Holland @ 2022-11-26 6:15 UTC (permalink / raw)
To: Palmer Dabbelt
Cc: Samuel Holland, Albert Ou, Anup Patel, Heinrich Schuchardt,
Paul Walmsley, linux-kernel, linux-riscv
The conditions reference the symbol SBI_V01, which does not exist. The
correct symbol is RISCV_SBI_V01.
Fixes: e623715f3d67 ("RISC-V: Increase range and default value of NR_CPUS")
Signed-off-by: Samuel Holland <samuel@sholland.org>
---
arch/riscv/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index fec54872ab45..acbfe34c6a00 100644
--- a/arch/riscv/Kconfig
+++ b/arch/riscv/Kconfig
@@ -319,9 +319,9 @@ config SMP
config NR_CPUS
int "Maximum number of CPUs (2-512)"
depends on SMP
- range 2 512 if !SBI_V01
- range 2 32 if SBI_V01 && 32BIT
- range 2 64 if SBI_V01 && 64BIT
+ range 2 512 if !RISCV_SBI_V01
+ range 2 32 if RISCV_SBI_V01 && 32BIT
+ range 2 64 if RISCV_SBI_V01 && 64BIT
default "32" if 32BIT
default "64" if 64BIT
--
2.37.4
^ permalink raw reply related [flat|nested] 7+ messages in thread* Re: [PATCH] riscv: Fix NR_CPUS range conditions 2022-11-26 6:15 [PATCH] riscv: Fix NR_CPUS range conditions Samuel Holland @ 2022-11-26 15:32 ` Conor Dooley 2022-11-28 18:35 ` Andrew Jones 2022-11-28 23:36 ` Palmer Dabbelt 2022-11-28 23:40 ` patchwork-bot+linux-riscv 2 siblings, 1 reply; 7+ messages in thread From: Conor Dooley @ 2022-11-26 15:32 UTC (permalink / raw) To: Samuel Holland Cc: Palmer Dabbelt, Albert Ou, Anup Patel, Heinrich Schuchardt, Paul Walmsley, linux-kernel, linux-riscv On Sat, Nov 26, 2022 at 12:15:56AM -0600, Samuel Holland wrote: > The conditions reference the symbol SBI_V01, which does not exist. The > correct symbol is RISCV_SBI_V01. Huh, good spot. Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > > Fixes: e623715f3d67 ("RISC-V: Increase range and default value of NR_CPUS") > Signed-off-by: Samuel Holland <samuel@sholland.org> > --- > > arch/riscv/Kconfig | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig > index fec54872ab45..acbfe34c6a00 100644 > --- a/arch/riscv/Kconfig > +++ b/arch/riscv/Kconfig > @@ -319,9 +319,9 @@ config SMP > config NR_CPUS > int "Maximum number of CPUs (2-512)" > depends on SMP > - range 2 512 if !SBI_V01 > - range 2 32 if SBI_V01 && 32BIT > - range 2 64 if SBI_V01 && 64BIT > + range 2 512 if !RISCV_SBI_V01 > + range 2 32 if RISCV_SBI_V01 && 32BIT > + range 2 64 if RISCV_SBI_V01 && 64BIT > default "32" if 32BIT > default "64" if 64BIT > > -- > 2.37.4 > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] riscv: Fix NR_CPUS range conditions 2022-11-26 15:32 ` Conor Dooley @ 2022-11-28 18:35 ` Andrew Jones 2022-11-28 19:19 ` Conor Dooley 2022-11-28 23:38 ` Palmer Dabbelt 0 siblings, 2 replies; 7+ messages in thread From: Andrew Jones @ 2022-11-28 18:35 UTC (permalink / raw) To: Conor Dooley Cc: Samuel Holland, Palmer Dabbelt, Albert Ou, Anup Patel, Heinrich Schuchardt, Paul Walmsley, linux-kernel, linux-riscv On Sat, Nov 26, 2022 at 03:32:04PM +0000, Conor Dooley wrote: > On Sat, Nov 26, 2022 at 12:15:56AM -0600, Samuel Holland wrote: > > The conditions reference the symbol SBI_V01, which does not exist. The > > correct symbol is RISCV_SBI_V01. > > Huh, good spot. > Reviewed-by: Conor Dooley <conor.dooley@microchip.com> Yeah, huh. It never occurred to me that we don't have some sort of symbol referencing checking in kconfig. Or maybe we do and I just don't know how to enable it? Anyway, this issue made me wonder how many more dangling references we may have. I wrote a script to look for them and found 29, including this one. I'm not exactly sure how to report them since they touch so many different places. For now, I've opened this kernel BZ https://bugzilla.kernel.org/show_bug.cgi?id=216748 > > > > > Fixes: e623715f3d67 ("RISC-V: Increase range and default value of NR_CPUS") > > Signed-off-by: Samuel Holland <samuel@sholland.org> > > --- > > > > arch/riscv/Kconfig | 6 +++--- > > 1 file changed, 3 insertions(+), 3 deletions(-) > > > > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig > > index fec54872ab45..acbfe34c6a00 100644 > > --- a/arch/riscv/Kconfig > > +++ b/arch/riscv/Kconfig > > @@ -319,9 +319,9 @@ config SMP > > config NR_CPUS > > int "Maximum number of CPUs (2-512)" > > depends on SMP > > - range 2 512 if !SBI_V01 > > - range 2 32 if SBI_V01 && 32BIT > > - range 2 64 if SBI_V01 && 64BIT > > + range 2 512 if !RISCV_SBI_V01 > > + range 2 32 if RISCV_SBI_V01 && 32BIT > > + range 2 64 if RISCV_SBI_V01 && 64BIT And for this patch, Reviewed-by: Andrew Jones <ajones@ventanamicro.com> Thanks, drew ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] riscv: Fix NR_CPUS range conditions 2022-11-28 18:35 ` Andrew Jones @ 2022-11-28 19:19 ` Conor Dooley 2022-11-28 23:38 ` Palmer Dabbelt 1 sibling, 0 replies; 7+ messages in thread From: Conor Dooley @ 2022-11-28 19:19 UTC (permalink / raw) To: Andrew Jones Cc: Samuel Holland, Palmer Dabbelt, Albert Ou, Anup Patel, Heinrich Schuchardt, Paul Walmsley, linux-kernel, linux-riscv, Randy Dunlap On Mon, Nov 28, 2022 at 07:35:59PM +0100, Andrew Jones wrote: > On Sat, Nov 26, 2022 at 03:32:04PM +0000, Conor Dooley wrote: > > On Sat, Nov 26, 2022 at 12:15:56AM -0600, Samuel Holland wrote: > > > The conditions reference the symbol SBI_V01, which does not exist. The > > > correct symbol is RISCV_SBI_V01. > > > > Huh, good spot. > > Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > > Yeah, huh. It never occurred to me that we don't have some sort of symbol > referencing checking in kconfig. Or maybe we do and I just don't know how kismet, but that does the opposite. Randy Dunlap is the only person I see fiddling with that stuff usually, so perhaps he knows? +CC them either way. > to enable it? Anyway, this issue made me wonder how many more dangling > references we may have. I wrote a script to look for them and found 29, > including this one. I'm not exactly sure how to report them since they > touch so many different places. For now, I've opened this kernel BZ > > https://bugzilla.kernel.org/show_bug.cgi?id=216748 > > > > > > > > > Fixes: e623715f3d67 ("RISC-V: Increase range and default value of NR_CPUS") > > > Signed-off-by: Samuel Holland <samuel@sholland.org> > > > --- > > > > > > arch/riscv/Kconfig | 6 +++--- > > > 1 file changed, 3 insertions(+), 3 deletions(-) > > > > > > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig > > > index fec54872ab45..acbfe34c6a00 100644 > > > --- a/arch/riscv/Kconfig > > > +++ b/arch/riscv/Kconfig > > > @@ -319,9 +319,9 @@ config SMP > > > config NR_CPUS > > > int "Maximum number of CPUs (2-512)" > > > depends on SMP > > > - range 2 512 if !SBI_V01 > > > - range 2 32 if SBI_V01 && 32BIT > > > - range 2 64 if SBI_V01 && 64BIT > > > + range 2 512 if !RISCV_SBI_V01 > > > + range 2 32 if RISCV_SBI_V01 && 32BIT > > > + range 2 64 if RISCV_SBI_V01 && 64BIT > > And for this patch, > > Reviewed-by: Andrew Jones <ajones@ventanamicro.com> > > Thanks, > drew ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] riscv: Fix NR_CPUS range conditions 2022-11-28 18:35 ` Andrew Jones 2022-11-28 19:19 ` Conor Dooley @ 2022-11-28 23:38 ` Palmer Dabbelt 1 sibling, 0 replies; 7+ messages in thread From: Palmer Dabbelt @ 2022-11-28 23:38 UTC (permalink / raw) To: ajones Cc: Conor Dooley, samuel, aou, apatel, heinrich.schuchardt, Paul Walmsley, linux-kernel, linux-riscv On Mon, 28 Nov 2022 10:35:59 PST (-0800), ajones@ventanamicro.com wrote: > On Sat, Nov 26, 2022 at 03:32:04PM +0000, Conor Dooley wrote: >> On Sat, Nov 26, 2022 at 12:15:56AM -0600, Samuel Holland wrote: >> > The conditions reference the symbol SBI_V01, which does not exist. The >> > correct symbol is RISCV_SBI_V01. >> >> Huh, good spot. >> Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > > Yeah, huh. It never occurred to me that we don't have some sort of symbol > referencing checking in kconfig. Or maybe we do and I just don't know how > to enable it? Anyway, this issue made me wonder how many more dangling > references we may have. I wrote a script to look for them and found 29, > including this one. I'm not exactly sure how to report them since they > touch so many different places. For now, I've opened this kernel BZ > > https://bugzilla.kernel.org/show_bug.cgi?id=216748 Thanks. This is on fixes, it's sort of jumping the queue (I've got a bunch of stuff still staged from last week, but thanksgiving screwed up the flow) but it's small enough it doesn't seem worth waiting. > >> >> > >> > Fixes: e623715f3d67 ("RISC-V: Increase range and default value of NR_CPUS") >> > Signed-off-by: Samuel Holland <samuel@sholland.org> >> > --- >> > >> > arch/riscv/Kconfig | 6 +++--- >> > 1 file changed, 3 insertions(+), 3 deletions(-) >> > >> > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig >> > index fec54872ab45..acbfe34c6a00 100644 >> > --- a/arch/riscv/Kconfig >> > +++ b/arch/riscv/Kconfig >> > @@ -319,9 +319,9 @@ config SMP >> > config NR_CPUS >> > int "Maximum number of CPUs (2-512)" >> > depends on SMP >> > - range 2 512 if !SBI_V01 >> > - range 2 32 if SBI_V01 && 32BIT >> > - range 2 64 if SBI_V01 && 64BIT >> > + range 2 512 if !RISCV_SBI_V01 >> > + range 2 32 if RISCV_SBI_V01 && 32BIT >> > + range 2 64 if RISCV_SBI_V01 && 64BIT > > And for this patch, > > Reviewed-by: Andrew Jones <ajones@ventanamicro.com> > > Thanks, > drew ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] riscv: Fix NR_CPUS range conditions 2022-11-26 6:15 [PATCH] riscv: Fix NR_CPUS range conditions Samuel Holland 2022-11-26 15:32 ` Conor Dooley @ 2022-11-28 23:36 ` Palmer Dabbelt 2022-11-28 23:40 ` patchwork-bot+linux-riscv 2 siblings, 0 replies; 7+ messages in thread From: Palmer Dabbelt @ 2022-11-28 23:36 UTC (permalink / raw) To: Samuel Holland, Palmer Dabbelt Cc: Anup Patel, linux-riscv, Heinrich Schuchardt, linux-kernel, Paul Walmsley, Albert Ou On Sat, 26 Nov 2022 00:15:56 -0600, Samuel Holland wrote: > The conditions reference the symbol SBI_V01, which does not exist. The > correct symbol is RISCV_SBI_V01. > > Applied, thanks! [1/1] riscv: Fix NR_CPUS range conditions https://git.kernel.org/palmer/c/1d6b5ed41f8c Best regards, -- Palmer Dabbelt <palmer@rivosinc.com> ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] riscv: Fix NR_CPUS range conditions 2022-11-26 6:15 [PATCH] riscv: Fix NR_CPUS range conditions Samuel Holland 2022-11-26 15:32 ` Conor Dooley 2022-11-28 23:36 ` Palmer Dabbelt @ 2022-11-28 23:40 ` patchwork-bot+linux-riscv 2 siblings, 0 replies; 7+ messages in thread From: patchwork-bot+linux-riscv @ 2022-11-28 23:40 UTC (permalink / raw) To: Samuel Holland Cc: linux-riscv, palmer, aou, apatel, heinrich.schuchardt, paul.walmsley, linux-kernel Hello: This patch was applied to riscv/linux.git (fixes) by Palmer Dabbelt <palmer@rivosinc.com>: On Sat, 26 Nov 2022 00:15:56 -0600 you wrote: > The conditions reference the symbol SBI_V01, which does not exist. The > correct symbol is RISCV_SBI_V01. > > Fixes: e623715f3d67 ("RISC-V: Increase range and default value of NR_CPUS") > Signed-off-by: Samuel Holland <samuel@sholland.org> > --- > > [...] Here is the summary with links: - riscv: Fix NR_CPUS range conditions https://git.kernel.org/riscv/c/1d6b5ed41f8c You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2022-11-28 23:40 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2022-11-26 6:15 [PATCH] riscv: Fix NR_CPUS range conditions Samuel Holland 2022-11-26 15:32 ` Conor Dooley 2022-11-28 18:35 ` Andrew Jones 2022-11-28 19:19 ` Conor Dooley 2022-11-28 23:38 ` Palmer Dabbelt 2022-11-28 23:36 ` Palmer Dabbelt 2022-11-28 23:40 ` patchwork-bot+linux-riscv
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox