Opened on 06/16/20 at 05:07:49

Closed on 06/18/20 at 05:13:36

Last modified on 06/23/21 at 07:07:55

#4005 closed enhancement (fixed)

Remove RTEMS_MP_NOT_CONFIGURED error condition

Reported by: Sebastian Huber Owned by: Sebastian Huber
Priority: normal Milestone: 5.1
Component: rtems Version: 5
Severity: normal Keywords: qualification
Cc: Blocked By:
Blocking:

Description

Some objects can be created with a local or global scope in a multiprocessing network. In non-multiprocessing configurations setting the scope to local or global had no effect since such a system can be viewed as a multiprocessing system with just one node. One and all nodes is the same in such a system. However, if multiprocessing was configured, creation of a global object in a single node system resulted in an RTEMS_MP_NOT_CONFIGURED error. Remove this error condition for symmetry with the non-multiprocessing setup. This is in line with the task affinity behaviour in SMP systems.

Change History (3)

comment:1 Changed on 06/18/20 at 05:10:06 by Sebastian Huber <sebastian.huber@…>

In 46c23871/rtems:

rtems: Remove RTEMS_MP_NOT_CONFIGURED error

Some objects can be created with a local or global scope in a
multiprocessing network. In non-multiprocessing configurations setting
the scope to local or global had no effect since such a system can be
viewed as a multiprocessing network with just one node. One and all
nodes is the same in such a network. However, if multiprocessing was
configured, creation of a global object in a single node network
resulted in an RTEMS_MP_NOT_CONFIGURED error. Remove this error
condition for symmetry to the non-multiprocessing setup. This is in line
with the task affinity behaviour in SMP systems.

Update #4005.

comment:2 Changed on 06/18/20 at 05:13:36 by Sebastian Huber <sebastian.huber@…>

Resolution: → fixed
Status: assigned → closed

In 1b2468c/rtems-docs:

c-user: Remove RTEMS_MP_NOT_CONFIGURED error

Some objects can be created with a local or global scope in a
multiprocessing network. In non-multiprocessing configurations setting
the scope to local or global had no effect since such a system can be
viewed as a multiprocessing network with just one node. One and all
nodes is the same in such a network. However, if multiprocessing was
configured, creation of a global object in a single node network
resulted in an RTEMS_MP_NOT_CONFIGURED error. Remove this error
condition for symmetry to the non-multiprocessing setup. This is in line
with the task affinity behaviour in SMP systems.

Close #4005.

comment:3 Changed on 06/23/21 at 07:07:55 by Sebastian Huber

Keywords: qualification added
Note: See TracTickets for help on using tickets.