On Fri, Sep 7, 2018 at 9:48 AM, Sebastian Huber <sebastian.hu...@embedded-brains.de> wrote: > 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_services.rst > +++ b/c-user/symmetric_multiprocessing_services.rst > @@ -791,3 +791,21 @@ from the executing to the heir thread neither the stack > of the executing nor > the heir thread must be used during interrupt processing. For this purpose a > temporary per-processor stack is set up which may be used by the interrupt > prologue before the stack is switched to the interrupt stack. > + > +Per-Processor Data > +------------------ > + > +RTMES provides two means for per-processor data: RTEMS
> + > +1. Per-processor data which used by RTEMS itself is contained in the "which used" -> "which is used" > + `Per_CPU_Control` structure. The application configuration via > + `<rtems/confdefs.h>` creates a table of these structures > + (`_Per_CPU_Information[]`). The table is dimensioned according to the > count > + of configured processors > + (:ref:`CONFIGURE_MAXIMUM_PROCESSORS <CONFIGURE_MAXIMUM_PROCESSORS>`). > + > +2. For low level support libraries an API for statically allocated > + per-processor data is available via > + `<rtems/score/percpudata.h> > <https://git.rtems.org/rtems/tree/cpukit/include/rtems/score/percpudata.h>`_. > + This API is not intended for general application use. Please ask on the > + development mailing list in case you want to use it. > -- > 2.13.7 > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
