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
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
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
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
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
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
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
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 +-
>
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.
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.
>>> ---
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 +-
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. On some architectures, the
thread-local storage area of
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.
---
bsps/include/dev/irq/arm-gicv3.h | 30
13 matches
Mail list logo
