Re: Coverage analysis update

On Thu, Jul 6, 2017 at 11:11 AM, Cillian O'Donnell wrote: > On 6 July 2017 at 15:34, Joel Sherrill wrote: > > > > > > On Thu, Jul 6, 2017 at 5:53 AM, Cillian O'Donnell > > > wrote: > >> > >> On 6 July 2017 at 08:05, Chris Johns

Re: Coverage analysis update

On 6 July 2017 at 19:14, Joel Sherrill wrote: > > > On Thu, Jul 6, 2017 at 11:11 AM, Cillian O'Donnell > wrote: >> >> On 6 July 2017 at 15:34, Joel Sherrill wrote: >> > >> > >> > On Thu, Jul 6, 2017 at 5:53 AM, Cillian O'Donnell >> >

Re: Coverage analysis update

On Thu, Jul 6, 2017 at 4:14 PM, Cillian O'Donnell wrote: > On 6 July 2017 at 19:14, Joel Sherrill wrote: > > > > > > On Thu, Jul 6, 2017 at 11:11 AM, Cillian O'Donnell < > cpodonne...@gmail.com> > > wrote: > >> > >> On 6 July 2017 at 15:34, Joel Sherrill

Re: [PATCH 1/2] Add FDT support for Beaglebone Black.

Ok, so we have to use a BSP option to avoid an include of from start.S. In this case, please just rename U_BOOT_USE_FDT to BSP_START_COPY_FDT_FROM_U_BOOT. On 06/07/17 10:00, Sichen Zhao wrote: Hi Sebastian, Hi all, How about i add BSP_START_COPY_FDT_FROM_U_BOOT in configure.ac, or just

Re: [PATCH 1/2] Add FDT support for Beaglebone Black.

Hi Sebastian, Hi all, How about i add BSP_START_COPY_FDT_FROM_U_BOOT in configure.ac, or just add the bsp prefix sush as BBB_U_BOOT_USE_FDT in configure.ac? Best Regards Sichen Zhao From: devel on behalf of Sichen Zhao

Re: Coverage analysis update

On 05/07/2017 22:46, Cillian O'Donnell wrote: > > Now the thing is, I might have to run RTEMS Tester about 3 times for > the full testsuite before I can get the report, as the covoar runs > will often hang on an arbitrary method and have to be manually exited > and re-run. How is covoar being

[PATCH 06/10] rtems: Fix rtems_scheduler_remove_processor()

Account for the thread processor affinity and make sure that it is possible to allocate a processor to each thread dedicated to a scheduler instance. Update #3059. --- cpukit/rtems/src/schedulerremoveprocessor.c | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git

[PATCH 07/10] score: Use Processor_mask for set affinity

Update #3059. --- cpukit/score/include/rtems/score/scheduler.h | 17 +--- cpukit/score/include/rtems/score/schedulerimpl.h | 31 -- .../rtems/score/schedulerpriorityaffinitysmp.h | 6 ++--- cpukit/score/src/schedulerdefaultsetaffinity.c | 6 ++---

[PATCH 04/10] score: Move processor affinity to Thread_Control

Update #3059. --- cpukit/score/Makefile.am | 1 - cpukit/score/include/rtems/score/processormask.h | 2 ++ cpukit/score/include/rtems/score/scheduler.h | 27 cpukit/score/include/rtems/score/schedulerimpl.h | 14

[PATCH 02/10] score: Add processor mask to/from cpu_set_t

Update #3059. --- cpukit/score/Makefile.am | 1 + cpukit/score/include/rtems/score/processormask.h | 52 +++- cpukit/score/src/processormaskcopy.c | 75 3 files changed, 126 insertions(+), 2 deletions(-) create mode 100644

[PATCH 03/10] score: Add some processor mask functions

Update #3059. --- cpukit/score/include/rtems/score/processormask.h | 99 1 file changed, 99 insertions(+) diff --git a/cpukit/score/include/rtems/score/processormask.h b/cpukit/score/include/rtems/score/processormask.h index 27c35d38f1..b550aa42a9 100644 ---

[PATCH 10/10] score: Add simple affinity support to EDF SMP

Update #3059. df --- cpukit/sapi/include/confdefs.h | 3 +- cpukit/sapi/include/rtems/scheduler.h | 7 +- cpukit/score/include/rtems/score/scheduleredfsmp.h | 23 +- .../score/include/rtems/score/schedulersmpimpl.h | 92 +-

[PATCH 05/10] score: Add processor set to scheduler context

Replace the simple processor count with the processor set owned by the scheduler instance. Update #3059. --- cpukit/rtems/src/scheduleraddprocessor.c | 2 +- cpukit/rtems/src/schedulergetprocessorset.c | 12 +++- cpukit/rtems/src/schedulerremoveprocessor.c | 6 +++---

[PATCH 08/10] score: Add scheduler node to set affinity op

Update #3059. --- cpukit/score/include/rtems/score/scheduler.h | 3 +++ cpukit/score/include/rtems/score/schedulerimpl.h | 2 ++ .../include/rtems/score/schedulerpriorityaffinitysmp.h | 1 + cpukit/score/src/schedulerdefaultsetaffinity.c | 2 ++

Re: Coverage analysis update

On Thu, Jul 6, 2017 at 5:53 AM, Cillian O'Donnell wrote: > On 6 July 2017 at 08:05, Chris Johns wrote: > > On 05/07/2017 22:46, Cillian O'Donnell wrote: > >> > >> Now the thing is, I might have to run RTEMS Tester about 3 times for > >> the full

Re: Coverage analysis update

On 6 July 2017 at 15:34, Joel Sherrill wrote: > > > On Thu, Jul 6, 2017 at 5:53 AM, Cillian O'Donnell > wrote: >> >> On 6 July 2017 at 08:05, Chris Johns wrote: >> > On 05/07/2017 22:46, Cillian O'Donnell wrote: >> >> >> >> Now the thing

Re: Coverage analysis update

On 07/07/2017 12:10, Joel Sherrill wrote: > > > On Jul 6, 2017 8:52 PM, "Chris Johns" > wrote: > > On 07/07/2017 00:34, Joel Sherrill wrote: > > On Thu, Jul 6, 2017 at 5:53 AM, Cillian O'Donnell

Re: Coverage analysis update

On Jul 6, 2017 8:52 PM, "Chris Johns" wrote: On 07/07/2017 00:34, Joel Sherrill wrote: > On Thu, Jul 6, 2017 at 5:53 AM, Cillian O'Donnell > wrote: > It will ignore records when it thinks things are inconsistent. This can

Re: Coverage analysis update

On 07/07/2017 12:58, Joel Sherrill wrote: > On Jul 6, 2017 9:20 PM, "Chris Johns" > wrote: > > On 07/07/2017 12:10, Joel Sherrill wrote: > > > > > > On Jul 6, 2017 8:52 PM, "Chris Johns"

Re: Coverage analysis update

On 07/07/2017 00:34, Joel Sherrill wrote: > On Thu, Jul 6, 2017 at 5:53 AM, Cillian O'Donnell > wrote: > >> When a test run is successful it will also finish with a lot of these > messages: > Also I wanted to mention, there is quite a

Re: Coverage analysis update

On 07/07/2017 08:11, Joel Sherrill wrote: > > The rtems tester tries to run the tests in parallel. I wonder if this trips > some conflict which we are not aware of. Are the file generated cleanly separated? If you are rewriting files with qemu and running covoar at the same time on the same

Re: Coverage analysis update

On 07/07/2017 00:34, Joel Sherrill wrote: > On Thu, Jul 6, 2017 at 5:53 AM, Cillian O'Donnell > wrote: > It will ignore records when it thinks things are inconsistent. This can occur > when a method appears in two different executables and has