[tools] tester: Remove hard coded time limits for SIS

2022-07-04 Thread Sebastian Huber
Remove the hard coded time limits in the SIS configurations which would overrule the general tester settings (for example the--timeout command line option). --- tester/rtems/testing/bsps/erc32-sis.ini | 2 +- tester/rtems/testing/bsps/gr740-sis.ini | 2 +- tester/rtems/testing/bsps/grisc

Re: [PATCH v2] irq/arm-gicv3.h: Customize ICC_IGRPEN0/1 init

2022-07-04 Thread Chris Johns
On 4/7/2022 4:06 pm, Sebastian Huber wrote: > On 04/07/2022 03:43, Chris Johns wrote: >> On 1/7/2022 11:21 pm, Sebastian Huber wrote: >>> Use the existing WRITE_SR() abstraction to access the interrupt group 0 and >>> 1 >>> enable registers.  This fixes the build for the AArch32 target. >>> --- >>

Re: [PATCH] score: Add _CPU_Use_thread_local_storage()

2022-07-04 Thread Chris Johns
On 4/7/2022 4:08 pm, Sebastian Huber wrote: > On 29/06/2022 15:07, Sebastian Huber wrote: >> At some point during system initialization, the idle threads are created. >> Afterwards, the boot processor basically executes within the context of an >> idle >> thread with thread dispatching disabled. 

Re: [tools] tester: Remove hard coded time limits for SIS

2022-07-04 Thread Chris Johns
OK Chris On 4/7/2022 6:52 pm, Sebastian Huber wrote: > Remove the hard coded time limits in the SIS configurations which would > overrule the general tester settings (for example the--timeout command line > option). > --- > tester/rtems/testing/bsps/erc32-sis.ini | 2 +- > tester/rtems/test

Re: [tools] tester: Remove hard coded time limits for SIS

2022-07-04 Thread Joel Sherrill
The limit removed in sis and tsim is the simulated cpu time used. If not using that, the behavior of the tester is to let the simulator run for so much real processor time. Replacing these with a command line argument is probably good but just removing these mean these simulators will just run muc

Re: [tools] tester: Remove hard coded time limits for SIS

2022-07-04 Thread Chris Johns
On 5/7/2022 9:44 am, Joel Sherrill wrote: > The limit removed in sis and tsim is the simulated cpu time used. If not using > that, the behavior of the tester is to let the simulator run for so much real > processor time.  > > Replacing these with a command line argument is probably good but just

Re: [PATCH] score: Add _CPU_Use_thread_local_storage()

2022-07-04 Thread Sebastian Huber
On 05/07/2022 00:33, Chris Johns wrote: On 4/7/2022 4:08 pm, Sebastian Huber wrote: On 29/06/2022 15:07, Sebastian Huber wrote: At some point during system initialization, the idle threads are created. Afterwards, the boot processor basically executes within the context of an idle thread with

Re: [tools] tester: Remove hard coded time limits for SIS

2022-07-04 Thread Sebastian Huber
On 05/07/2022 03:08, Chris Johns wrote: On 5/7/2022 9:44 am, Joel Sherrill wrote: The limit removed in sis and tsim is the simulated cpu time used. If not using that, the behavior of the tester is to let the simulator run for so much real processor time. Replacing these with a command line argu

Re: [PATCH] score: Add _CPU_Use_thread_local_storage()

2022-07-04 Thread Chris Johns
On 5/7/2022 2:56 pm, Sebastian Huber wrote: > On 05/07/2022 00:33, Chris Johns wrote: >> On 4/7/2022 4:08 pm, Sebastian Huber wrote: >>> On 29/06/2022 15:07, Sebastian Huber wrote: At some point during system initialization, the idle threads are created. Afterwards, the boot processor bas

Re: [tools] tester: Remove hard coded time limits for SIS

2022-07-04 Thread Chris Johns
On 5/7/2022 2:58 pm, Sebastian Huber wrote: > On 05/07/2022 03:08, Chris Johns wrote: >> On 5/7/2022 9:44 am, Joel Sherrill wrote: >>> The limit removed in sis and tsim is the simulated cpu time used. If not >>> using >>> that, the behavior of the tester is to let the simulator run for so much >>

Re: [PATCH v2] irq/arm-gicv3.h: Customize ICC_IGRPEN0/1 init

2022-07-04 Thread Sebastian Huber
On 05/07/2022 00:28, Chris Johns wrote: On 4/7/2022 4:06 pm, Sebastian Huber wrote: On 04/07/2022 03:43, Chris Johns wrote: On 1/7/2022 11:21 pm, Sebastian Huber wrote: Use the existing WRITE_SR() abstraction to access the interrupt group 0 and 1 enable registers.  This fixes the build for the

Re: [tools] tester: Remove hard coded time limits for SIS

2022-07-04 Thread Sebastian Huber
On 05/07/2022 07:14, Chris Johns wrote: On 5/7/2022 2:58 pm, Sebastian Huber wrote: On 05/07/2022 03:08, Chris Johns wrote: On 5/7/2022 9:44 am, Joel Sherrill wrote: The limit removed in sis and tsim is the simulated cpu time used. If not using that, the behavior of the tester is to let the si

Re: [tools] tester: Remove hard coded time limits for SIS

2022-07-04 Thread Chris Johns
On 5/7/2022 4:02 pm, Sebastian Huber wrote: > On 05/07/2022 07:14, Chris Johns wrote: >> On 5/7/2022 2:58 pm, Sebastian Huber wrote: >>> On 05/07/2022 03:08, Chris Johns wrote: On 5/7/2022 9:44 am, Joel Sherrill wrote: > The limit removed in sis and tsim is the simulated cpu time used. If

Re: [tools] tester: Remove hard coded time limits for SIS

2022-07-04 Thread Sebastian Huber
On 05/07/2022 08:23, Chris Johns wrote: On 5/7/2022 4:02 pm, Sebastian Huber wrote: On 05/07/2022 07:14, Chris Johns wrote: On 5/7/2022 2:58 pm, Sebastian Huber wrote: On 05/07/2022 03:08, Chris Johns wrote: On 5/7/2022 9:44 am, Joel Sherrill wrote: The limit removed in sis and tsim is the s

[PATCH] validation: Test scheduler detail

2022-07-04 Thread Sebastian Huber
This particular state during a reconsider help request scheduler operation was only covered by the existing test suites under some timing conditions. --- testsuites/validation/tc-sched-smp.c | 137 ++- 1 file changed, 135 insertions(+), 2 deletions(-) diff --git a/testsuit