[PATCH 1/3] score: Add flexible per-CPU data

Update #3507. --- cpukit/headers.am | 1 + cpukit/include/rtems/score/percpu.h| 9 +- cpukit/include/rtems/score/percpudata.h| 104 cpukit/score/src/wkspace.c | 128 +++-- testsuites/sptests/Makef

[PATCH 2/3] score: Modify _Scheduler_Unblock()

In SMP configurations, obtain the scheduler node for the block and unblock operations through the same way via Thread_Control::Scheduler::Scheduler_node. This symmetry is important in a follow up patch which introduces thread pinning. Update #3508. --- cpukit/include/rtems/score/schedulerimpl.h

[PATCH 3/3] score: Add thread pin/unpin support

Add support to temporarily pin a thread to its current processor. This may be used to access per-processor data structures in critical sections with enabled thread dispatching, e.g. a pinned thread is allowed to block. Update #3508. --- cpukit/include/rtems/score/scheduler.h | 48 ++

[PATCH 1/2] c-user: Mention per-processor data

Close #3507. --- c-user/symmetric_multiprocessing_services.rst | 18 ++ 1 file changed, 18 insertions(+) diff --git a/c-user/symmetric_multiprocessing_services.rst b/c-user/symmetric_multiprocessing_services.rst index 638292b..4204d3f 100644 --- a/c-user/symmetric_multiprocessing

[PATCH 2/2] c-user: Mention thread pinning

Close #3508. --- c-user/symmetric_multiprocessing_services.rst | 18 ++ 1 file changed, 18 insertions(+) diff --git a/c-user/symmetric_multiprocessing_services.rst b/c-user/symmetric_multiprocessing_services.rst index 4204d3f..4c80cb9 100644 --- a/c-user/symmetric_multiprocessing

Re: rtems-bsp-builder .ini file syntax question (for epiphany)

On Thu, Sep 6, 2018 at 9:07 PM Chris Johns wrote: > On 6/9/18 9:00 am, Joel Sherrill wrote: > > https://lists.rtems.org/pipermail/build/2018-September/000997.html > still has > > epiphany > > failures. Not sure what else is going on. Do you see the pattern? > > The 'debug' build is not adding '--

Re: rtems-bsp-builder .ini file syntax question (for epiphany)

On 8/9/18 12:59 am, Joel Sherrill wrote: > On Thu, Sep 6, 2018 at 9:07 PM Chris Johns > wrote: > On 6/9/18 9:00 am, Joel Sherrill wrote: > > https://lists.rtems.org/pipermail/build/2018-September/000997.html > still has > > epiphany > > failures. Not sure

Re: rtems-bsp-builder .ini file syntax question (for epiphany)

On Fri, Sep 7, 2018, 10:06 PM Chris Johns wrote: > On 8/9/18 12:59 am, Joel Sherrill wrote: > > On Thu, Sep 6, 2018 at 9:07 PM Chris Johns > > wrote: > > On 6/9/18 9:00 am, Joel Sherrill wrote: > > > https://lists.rtems.org/pipermail/build/2018-September/000997.h

Re: rtems-bsp-builder .ini file syntax question (for epiphany)

On 8/9/18 1:12 pm, Joel Sherrill wrote: > On Fri, Sep 7, 2018, 10:06 PM Chris Johns > wrote: > > The solution is add the excluded 'no-' variant of the 'config' to the > 'base' > flags. The code currently removes the excluded builds from the build > list, code >

Re: rtems-bsp-builder .ini file syntax question (for epiphany)

On 8/9/18 1:23 pm, Chris Johns wrote: > On 8/9/18 1:12 pm, Joel Sherrill wrote: >> On Fri, Sep 7, 2018, 10:06 PM Chris Johns > > wrote: >> >> The solution is add the excluded 'no-' variant of the 'config' to the >> 'base' >> flags. The code currently removes the ex