Re: [PATCH 1/3] bsps/riscv: Make SMP start more robust

2023-03-17 Thread Sebastian Huber
Hello Alan, On 16.03.23 22:33, Alan Cudmore wrote: I applied these three patches after my patches and ran them on my K210 board and simulator. I have a set of 12 tests including benchmarks, SMP01, SMP08, ticker, etc. Everything ran OK. Is there anything in particular I can try to test them

Re: [PATCH 1/3] bsps/riscv: Make SMP start more robust

2023-03-17 Thread Padmarao.Begari
> On Thu, 2023-03-16 at 09:59 +0100, Sebastian Huber wrote: > > In SMP configurations, check that we run on a configured > processor. If not, > then there is not much what can be done since we do not have a stack > available > for this processor. Just loop forever in this case. Do this in >

Re: [PATCH 1/3] bsps/riscv: Make SMP start more robust

2023-03-16 Thread Chris Johns
On 16/3/2023 5:59 pm, Sebastian Huber wrote: > In SMP configurations, check that we run on a configured processor. If not, > then there is not much what can be done since we do not have a stack available not much that can be done ? No comment on the actual patch as I do not know RISCV

Re: [PATCH 1/3] bsps/riscv: Make SMP start more robust

2023-03-16 Thread Alan Cudmore
Hi Sebastian, I applied these three patches after my patches and ran them on my K210 board and simulator. I have a set of 12 tests including benchmarks, SMP01, SMP08, ticker, etc. Everything ran OK. Is there anything in particular I can try to test them like setting the maximum CPUs to 1? (K210 is

[PATCH 1/3] bsps/riscv: Make SMP start more robust

2023-03-16 Thread Sebastian Huber
In SMP configurations, check that we run on a configured processor. If not, then there is not much what can be done since we do not have a stack available for this processor. Just loop forever in this case. Do this in assemlby to ensure that no stack memory is used. ---