RISC-V: hwprobe: Explicity check for -1 in vdso init

id_bitsmash is unsigned. We need to explicitly check for -1, rather
than use > 0.

Fixes: aa5af0aa90 ("RISC-V: Add hwprobe vDSO function and data")
Signed-off-by: Andrew Jones <ajones@ventanamicro.com>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Reviewed-by: Evan Green <evan@rivosinc.com>
Link: https://lore.kernel.org/r/20230426141333.10063-3-ajones@ventanamicro.com
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
This commit is contained in:
Andrew Jones 2023-04-26 16:13:33 +02:00 committed by Palmer Dabbelt
parent 08dc107594
commit b09313dd2e
No known key found for this signature in database
GPG key ID: 2E1319F35FBB1889

View file

@ -282,7 +282,7 @@ static int __init init_hwprobe_vdso_data(void)
* populated) or any value returns -1 (varies across CPUs), then the
* vDSO should defer to the kernel for exotic cpu masks.
*/
avd->homogeneous_cpus = (id_bitsmash > 0);
avd->homogeneous_cpus = id_bitsmash != 0 && id_bitsmash != -1;
return 0;
}