Re: [PATCH v6 13/19] riscv: Fix race conditions when initializing IPI

2020-03-17 Thread Sean Anderson
On 3/10/20 9:33 PM, Rick Chen wrote: > Hi Sean > >> On 3/10/20 4:20 AM, Rick Chen wrote: >>> Hi Sean >>> The IPI code could have race conditions in several places. * Several harts could race on the value of gd->arch->clint/plic * Non-boot harts could race with the main hart on the D

Re: [PATCH v6 13/19] riscv: Fix race conditions when initializing IPI

2020-03-10 Thread Rick Chen
Hi Sean > On 3/10/20 4:20 AM, Rick Chen wrote: > > Hi Sean > > > >> The IPI code could have race conditions in several places. > >> * Several harts could race on the value of gd->arch->clint/plic > >> * Non-boot harts could race with the main hart on the DM subsystem In > >> addition, if an IPI

Re: [PATCH v6 13/19] riscv: Fix race conditions when initializing IPI

2020-03-10 Thread Sean Anderson
On 3/10/20 4:20 AM, Rick Chen wrote: > Hi Sean > >> The IPI code could have race conditions in several places. >> * Several harts could race on the value of gd->arch->clint/plic >> * Non-boot harts could race with the main hart on the DM subsystem In >> addition, if an IPI was pending when U-Boo

Re: [PATCH v6 13/19] riscv: Fix race conditions when initializing IPI

2020-03-10 Thread Rick Chen
Hi Sean > The IPI code could have race conditions in several places. > * Several harts could race on the value of gd->arch->clint/plic > * Non-boot harts could race with the main hart on the DM subsystem In > addition, if an IPI was pending when U-Boot started, it would cause the > IPI handler

[PATCH v6 13/19] riscv: Fix race conditions when initializing IPI

2020-03-05 Thread Sean Anderson
The IPI code could have race conditions in several places. * Several harts could race on the value of gd->arch->clint/plic * Non-boot harts could race with the main hart on the DM subsystem In addition, if an IPI was pending when U-Boot started, it would cause the IPI handler to jump to address