[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANBLGcyZ+wcBiZOyd8jC2-cUx_m+Zu6XZB6gyDOL_omQzEesPw@mail.gmail.com>
Date: Mon, 31 Jan 2022 18:52:43 +0100
From: Emil Renner Berthing <kernel@...il.dk>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Anup Patel <anup@...infault.org>,
Atish Patra <atishp@...osinc.com>,
Jessica Clarke <jrtc27@...c27.com>,
linux-riscv <linux-riscv@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] RISC-V: Fix cpumask rework falloout
On Mon, 31 Jan 2022 at 14:26, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>
> Hi all,
>
> This patch series intends to fix the fall-out from commit
> 26fb751ca37846c9 ("RISC-V: Do not use cpumask data structure for hartid
> bitmap"), cfr. the discussion in thread[1].
>
> Thanks for your comments!
>
> [1] "[PATCH v3 6/6] RISC-V: Do not use cpumask data structure for hartid
> bitmap"
> https://lore.kernel.org/r/20220120090918.2646626-7-atishp@rivosinc.com/
>
> Geert Uytterhoeven (3):
> RISC-V: Fix hartid mask handling for hartid 31 and up
> RISC-V: Fix handling of empty cpu masks
> RISC-V: Fix IPI/RFENCE hmask on non-monotonic hartid ordering
>
> arch/riscv/kernel/sbi.c | 72 +++++++++++++++++++++++++++--------------
> 1 file changed, 47 insertions(+), 25 deletions(-)
I built this and rebooted my Starlight board a number of times without
seeing any of the errors that usually shows up when [1] is not
reverted.
Tested-by: Emil Renner Berthing <kernel@...il.dk>
[1]: 26fb751ca37846c9 ("RISC-V: Do not use cpumask data structure for
hartid bitmap")
Powered by blists - more mailing lists