Re: Potential SIS or RTEMS/libbsd problem

2019-06-03 Thread Chris Johns
On 3/6/19 5:51 pm, Jiri Gaisler wrote: > > On 6/3/19 4:14 AM, Chris Johns wrote: >> On 1/6/19 6:58 am, Jiri Gaisler wrote: >>> I have pushed a small patch to fix some build problems on Cygwin and >>> FreeBSD. I don't know how fast we want to progress, but I could prepare a >>> patch for RSB to u

Re: Potential SIS or RTEMS/libbsd problem

2019-06-03 Thread Jiri Gaisler
On 6/3/19 4:14 AM, Chris Johns wrote: > On 1/6/19 6:58 am, Jiri Gaisler wrote: >> I have pushed a small patch to fix some build problems on Cygwin and >> FreeBSD. I don't know how fast we want to progress, but I could prepare a >> patch for RSB to use the new sis repository and skip the sis pat

Re: Potential SIS or RTEMS/libbsd problem

2019-06-02 Thread Chris Johns
On 1/6/19 6:58 am, Jiri Gaisler wrote: > I have pushed a small patch to fix some build problems on Cygwin and FreeBSD. > I don't know how fast we want to progress, but I could prepare a patch for > RSB to use the new sis repository and skip the sis patches for gdb. I guess > this would also have

Re: Potential SIS or RTEMS/libbsd problem

2019-05-31 Thread Jiri Gaisler
On 5/31/19 7:06 AM, Sebastian Huber wrote: > On 27/05/2019 11:03, Jiri Gaisler wrote: >> On 5/23/19 1:47 PM, Sebastian Huber wrote: >>> On 22/05/2019 22:34, Jiri Gaisler wrote: Adding a pseudo-random delay of 0 - 15 clocks to each trap/interrupt causes the test to pass on all cpu confi

Re: Potential SIS or RTEMS/libbsd problem

2019-05-30 Thread Sebastian Huber
On 27/05/2019 11:03, Jiri Gaisler wrote: On 5/23/19 1:47 PM, Sebastian Huber wrote: On 22/05/2019 22:34, Jiri Gaisler wrote: Adding a pseudo-random delay of 0 - 15 clocks to each trap/interrupt causes the test to pass on all cpu configurations with the default time slice (50)..! I am not sure

Re: Potential SIS or RTEMS/libbsd problem

2019-05-27 Thread Jiri Gaisler
On 5/23/19 1:47 PM, Sebastian Huber wrote: > On 22/05/2019 22:34, Jiri Gaisler wrote: >> Adding a pseudo-random delay of 0 - 15 clocks to each trap/interrupt causes >> the test to pass on all cpu configurations with the default time slice >> (50)..! I am not sure what this means - it could be a

Re: Potential SIS or RTEMS/libbsd problem

2019-05-23 Thread Jiri Gaisler
On 5/23/19 7:35 AM, Sebastian Huber wrote: > On 22/05/2019 22:34, Jiri Gaisler wrote: >> On 5/22/19 7:43 PM, Jiri Gaisler wrote: >>> On 5/22/19 9:49 AM, Sebastian Huber wrote: On 22/05/2019 09:39, Jiri Gaisler wrote: > On 5/22/19 8:03 AM, Sebastian Huber wrote: >> Hello, >> >>

Re: Potential SIS or RTEMS/libbsd problem

2019-05-23 Thread Jiri Gaisler
On 5/23/19 1:47 PM, Sebastian Huber wrote: > On 22/05/2019 22:34, Jiri Gaisler wrote: >> Adding a pseudo-random delay of 0 - 15 clocks to each trap/interrupt >> causes the test to pass on all cpu configurations with the default >> time slice (50)..! I am not sure what this means - it could be a >

Re: Potential SIS or RTEMS/libbsd problem

2019-05-23 Thread Sebastian Huber
On 22/05/2019 22:34, Jiri Gaisler wrote: Adding a pseudo-random delay of 0 - 15 clocks to each trap/interrupt causes the test to pass on all cpu configurations with the default time slice (50)..! I am not sure what this means - it could be a hidden race condition, the algorithm might need some

Re: Potential SIS or RTEMS/libbsd problem

2019-05-22 Thread Sebastian Huber
On 22/05/2019 22:34, Jiri Gaisler wrote: On 5/22/19 7:43 PM, Jiri Gaisler wrote: On 5/22/19 9:49 AM, Sebastian Huber wrote: On 22/05/2019 09:39, Jiri Gaisler wrote: On 5/22/19 8:03 AM, Sebastian Huber wrote: Hello, in the libbsd there is a test for the Epoch Based Reclamation: https://git.r

Re: Potential SIS or RTEMS/libbsd problem

2019-05-22 Thread Jiri Gaisler
On 5/22/19 7:43 PM, Jiri Gaisler wrote: > On 5/22/19 9:49 AM, Sebastian Huber wrote: >> On 22/05/2019 09:39, Jiri Gaisler wrote: >>> On 5/22/19 8:03 AM, Sebastian Huber wrote: Hello, in the libbsd there is a test for the Epoch Based Reclamation: https://git.rtems.org/rtems

Re: Potential SIS or RTEMS/libbsd problem

2019-05-22 Thread Jiri Gaisler
On 5/22/19 9:49 AM, Sebastian Huber wrote: > On 22/05/2019 09:39, Jiri Gaisler wrote: >> On 5/22/19 8:03 AM, Sebastian Huber wrote: >>> Hello, >>> >>> in the libbsd there is a test for the Epoch Based Reclamation: >>> >>> https://git.rtems.org/rtems-libbsd/tree/testsuite/epoch01/test_main.c >>> >>

Re: Potential SIS or RTEMS/libbsd problem

2019-05-22 Thread Sebastian Huber
On 22/05/2019 09:39, Jiri Gaisler wrote: On 5/22/19 8:03 AM, Sebastian Huber wrote: Hello, in the libbsd there is a test for the Epoch Based Reclamation: https://git.rtems.org/rtems-libbsd/tree/testsuite/epoch01/test_main.c When I run this test using the leon3 BSP on real hardware (150MHz NGM

Re: Potential SIS or RTEMS/libbsd problem

2019-05-22 Thread Jiri Gaisler
On 5/22/19 8:03 AM, Sebastian Huber wrote: > Hello, > > in the libbsd there is a test for the Epoch Based Reclamation: > > https://git.rtems.org/rtems-libbsd/tree/testsuite/epoch01/test_main.c > > When I run this test using the leon3 BSP on real hardware (150MHz NGMP FP) > the test completes succ

Potential SIS or RTEMS/libbsd problem

2019-05-21 Thread Sebastian Huber
Hello, in the libbsd there is a test for the Epoch Based Reclamation: https://git.rtems.org/rtems-libbsd/tree/testsuite/epoch01/test_main.c When I run this test using the leon3 BSP on real hardware (150MHz NGMP FP) the test completes successfully. If I run the test on the SIS, it is stuck at