RISC-V: Do not use cpumask data structure for hartid bitmap
Currently, SBI APIs accept a hartmask that is generated from struct cpumask. Cpumask data structure can hold upto NR_CPUs value. Thus, it is not the correct data structure for hartids as it can be higher than NR_CPUs for platforms with sparse or discontguous hartids. Remove all association between hartid mask and struct cpumask. Reviewed-by: Anup Patel <anup@brainfault.org> (For Linux RISC-V changes) Acked-by: Anup Patel <anup@brainfault.org> (For KVM RISC-V changes) Signed-off-by:Atish Patra <atishp@rivosinc.com> Signed-off-by:
Palmer Dabbelt <palmer@rivosinc.com>
Showing
- arch/riscv/include/asm/sbi.h 10 additions, 9 deletionsarch/riscv/include/asm/sbi.h
- arch/riscv/include/asm/smp.h 0 additions, 2 deletionsarch/riscv/include/asm/smp.h
- arch/riscv/kernel/sbi.c 106 additions, 83 deletionsarch/riscv/kernel/sbi.c
- arch/riscv/kernel/setup.c 0 additions, 10 deletionsarch/riscv/kernel/setup.c
- arch/riscv/kernel/smpboot.c 1 addition, 1 deletionarch/riscv/kernel/smpboot.c
- arch/riscv/kvm/mmu.c 1 addition, 3 deletionsarch/riscv/kvm/mmu.c
- arch/riscv/kvm/vcpu_sbi_replace.c 4 additions, 7 deletionsarch/riscv/kvm/vcpu_sbi_replace.c
- arch/riscv/kvm/vcpu_sbi_v01.c 4 additions, 7 deletionsarch/riscv/kvm/vcpu_sbi_v01.c
- arch/riscv/kvm/vmid.c 1 addition, 3 deletionsarch/riscv/kvm/vmid.c
- arch/riscv/mm/cacheflush.c 1 addition, 4 deletionsarch/riscv/mm/cacheflush.c
- arch/riscv/mm/tlbflush.c 2 additions, 7 deletionsarch/riscv/mm/tlbflush.c
Please register or sign in to comment