Changeset a0d2eee in rtems-docs


Ignore:
Timestamp:
Feb 1, 2017, 12:38:41 PM (3 years ago)
Author:
Sebastian Huber <sebastian.huber@…>
Branches:
master
Children:
0680bd2
Parents:
ba781f9
git-author:
Sebastian Huber <sebastian.huber@…> (02/01/17 12:38:41)
git-committer:
Sebastian Huber <sebastian.huber@…> (02/01/17 12:42:39)
Message:

Use "in X config..." instead of "on X config..."

Location:
c-user
Files:
6 edited

Legend:

Unmodified
Added
Removed
  • c-user/configuring_a_system.rst

    rba781f9 ra0d2eee  
    671671DESCRIPTION:
    672672    ``CONFIGURE_MAXIMUM_MRSP_SEMAPHORES`` is the maximum number of Classic API
    673     Semaphores using the Multiprocessor Resource Sharing Protocol (MrsP) that
    674     can be concurrently active.
    675 
    676 NOTES:
    677     This configuration option is only used on SMP configurations.  On
    678     uni-processor configurations the Priority Ceiling Protocol is used for MrsP
     673    Semaphores using the :ref:`MrsP` that can be concurrently active.
     674
     675NOTES:
     676    This configuration option is only used in SMP configurations.  In
     677    uni-processor configurations, the :ref:`PriorityCeiling` is used for MrsP
    679678    semaphores and thus no extra memory is necessary.
    680679
  • c-user/fatal_error.rst

    rba781f9 ra0d2eee  
    249249
    250250INTERNAL_ERROR_THREAD_QUEUE_ENQUEUE_STICKY_FROM_BAD_STATE (29)
    251     This fatal error can only happen on SMP configurations.  It is not allowed
     251    This fatal error can only happen in SMP configurations.  It is not allowed
    252252    to obtain MrsP semaphores in a context with thread dispatching disabled,
    253253    for example interrupt context.
     
    332332
    333333INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT (31)
    334     On SMP configurations, it is a fatal error to call blocking operating
     334    In SMP configurations, it is a fatal error to call blocking operating
    335335    system with interrupts disabled, since this prevents delivery of
    336336    inter-processor interrupts.  This could lead to executing threads which are
     
    410410
    411411For the initial extensions the read-write data (including .bss segment) is not
    412 required on single processor configurations.  On SMP configurations, however,
     412required on single processor configurations.  In SMP configurations, however,
    413413the read-write data must be initialized since this function must determine the
    414414state of the other processors and request them to shut-down if necessary.
  • c-user/glossary.rst

    rba781f9 ra0d2eee  
    172172:dfn:`executing task`
    173173    The task state entered by a task after it has been given control of the
    174     processor.  On SMP configurations a task may be registered as executing on
     174    processor.  In SMP configurations, a task may be registered as executing on
    175175    more than one processor for short time frames during task migration.
    176176    Blocked tasks can be executing until they issue a thread dispatch.
  • c-user/interrupt_manager.rst

    rba781f9 ra0d2eee  
    447447    This directive will not cause the calling task to be preempted.
    448448
    449     On SMP configurations this will not ensure system wide mutual exclusion.
     449    In SMP configurations, this will not ensure system wide mutual exclusion.
    450450    Use interrupt locks instead.
    451451
     
    529529
    530530DESCRIPTION:
    531     Interrupts will be disabled.  On SMP configurations this directive acquires
    532     a SMP lock.
     531    Interrupts will be disabled.  In SMP configurations, this directive
     532    acquires an SMP lock.
    533533
    534534NOTES:
     
    558558
    559559DESCRIPTION:
    560     The interrupt status will be restored.  On SMP configurations this
    561     directive releases a SMP lock.
     560    The interrupt status will be restored.  In SMP configurations, this
     561    directive releases an SMP lock.
    562562
    563563NOTES:
     
    587587
    588588DESCRIPTION:
    589     The interrupt status will remain unchanged.  On SMP configurations this
    590     directive acquires a SMP lock.
     589    The interrupt status will remain unchanged.  In SMP configurations, this
     590    directive acquires an SMP lock.
    591591
    592592    In case the corresponding interrupt service routine can be interrupted by
     
    621621DESCRIPTION:
    622622
    623     The interrupt status will remain unchanged.  On SMP configurations this
    624     directive releases a SMP lock.
     623    The interrupt status will remain unchanged.  In SMP configurations, this
     624    directive releases an SMP lock.
    625625
    626626NOTES:
  • c-user/semaphore_manager.rst

    rba781f9 ra0d2eee  
    429429
    430430    It is not allowed to create an initially locked MrsP semaphore and the
    431     ``RTEMS_INVALID_NUMBER`` status code will be returned on SMP configurations
     431    ``RTEMS_INVALID_NUMBER`` status code will be returned in SMP configurations
    432432    in this case.  This prevents lock order reversal problems with the
    433433    allocator mutex.
     
    613613
    614614    Deadlock situations are detected for MrsP semaphores and the
    615     ``RTEMS_UNSATISFIED`` status code will be returned on SMP configurations in
     615    ``RTEMS_UNSATISFIED`` status code will be returned in SMP configurations in
    616616    this case.
    617617
     
    639639    It is not allowed to obtain a MrsP semaphore more than once by one task at
    640640    a time (nested access) and the ``RTEMS_UNSATISFIED`` status code will be
    641     returned on SMP configurations in this case.
     641    returned in SMP configurations in this case.
    642642
    643643.. raw:: latex
     
    699699
    700700    The MrsP semaphores must be released in the reversed obtain order,
    701     otherwise the ``RTEMS_INCORRECT_STATE`` status code will be returned on SMP
     701    otherwise the ``RTEMS_INCORRECT_STATE`` status code will be returned in SMP
    702702    configurations in this case.
    703703
     
    756756
    757757    It is not allowed to flush a MrsP semaphore and the ``RTEMS_NOT_DEFINED``
    758     status code will be returned on SMP configurations in this case.
     758    status code will be returned in SMP configurations in this case.
    759759
    760760.. raw:: latex
  • c-user/symmetric_multiprocessing_services.rst

    rba781f9 ra0d2eee  
    266266A low overhead means to ensure mutual exclusion in uni-processor configurations
    267267is to disable interrupts around a critical section.  This is commonly used in
    268 device driver code and throughout the operating system core.  On SMP
     268device driver code and throughout the operating system core.  In SMP
    269269configurations, however, disabling the interrupts on one processor has no
    270270effect on other processors.  So, this is insufficient to ensure system wide
     
    277277- ``rtems_interrupt_flush()``
    278278
    279 are disabled on SMP configurations and its use will lead to compiler warnings
     279are disabled in SMP configurations and its use will lead to compiler warnings
    280280and linker errors.  In the unlikely case that interrupts must be disabled on
    281281the current processor, then the
     
    523523
    524524DESCRIPTION:
    525     On uni-processor configurations a value of one will be returned.
    526 
    527     On SMP configurations this returns the value of a global variable set
     525    In uni-processor configurations, a value of one will be returned.
     526
     527    In SMP configurations, this returns the value of a global variable set
    528528    during system initialization to indicate the count of utilized processors.
    529529    The processor count depends on the physically or virtually available
     
    552552
    553553DESCRIPTION:
    554     On uni-processor configurations a value of zero will be returned.
    555 
    556     On SMP configurations an architecture specific method is used to obtain the
     554    In uni-processor configurations, a value of zero will be returned.
     555
     556    In SMP configurations, an architecture specific method is used to obtain the
    557557    index of the current processor in the system.  The set of processor indices
    558558    is the range of integers starting with zero up to the processor count minus
Note: See TracChangeset for help on using the changeset viewer.