| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
This enables re-use for other purposes, e.g. replacement for
SMP_MESSAGE_TEST.
|
|
|
|
|
|
| |
Move resposibility to disable thread dispatching to the caller of
_SMP_Multicast_action(). Using an interrupt disable for this purpose is
questionable.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
If the caller already disabled interrupts, then do not disable thread
dispatching. Calling _SMP_Multicast_action() with interrupts disabled
is a questionable use case.
|
|
|
|
| |
Use _SMP_Multicast_action() instead.
|
|
|
|
| |
Let it work during system initialization.
|
|
|
|
|
| |
Use a FIFO list of jobs per processor to carry out the SMP multicast
action. Use a done indicator per job to reduce the bus traffic a bit.
|
|
|
|
| |
Processor_mask is the internal data type to deal with processor sets.
|
|
|
|
|
|
| |
The use of a hand crafted lock for Per_CPU_Control::Lock was necessary
at some point in the SMP support development, but it is no longer
justified.
|
|
|
|
|
| |
Add _ISR_lock_Set_name() to optimize the initialization of
zero-initialized locks.
|
|
|
|
|
|
|
| |
Rename _SMP_Get_processor_count() in _SMP_Get_processor_maximum() to be
in line with the API level rtems_scheduler_get_processor_maximum().
Update #3732.
|
|
|
|
|
|
|
| |
Rename _SMP_Processor_count in _SMP_Processor_maximum to be in line with
the API level rtems_scheduler_get_processor_maximum().
Update #3732.
|
|
|
|
|
| |
The _Objects_Information_table[ the_api ] is never NULL for a valid API
index.
|
|
|
|
| |
Update #3706
|
|
|
|
| |
Update #3706.
|
| |
|
| |
|
|
|
|
| |
Remove the priority node only in case it is active.
|
|
|
|
|
|
| |
This makes the @file documentation independent of the actual file name.
Update #3707.
|
|
|
|
|
|
|
|
| |
Recursive usage of the same pthread_once_t results now in a deadlock.
Previously, an error of EINVAL was returned. This usage scenario is
invalid according to the POSIX pthread_once() specification.
Close #3334.
|
|
|
|
| |
We must add/remove the priority queue to the FIFO of priority queues.
|
| |
|
|
|
|
|
|
|
| |
In case the robust thread dispatch is enabled by the CPU port, then the
interrupt level must not be changed through the task mode.
Update #3000.
|
|
|
|
| |
Update #3000.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Allocate the per-CPU data for secondary processors directly from the
heap areas before heap initialization and not via
_Workspace_Allocate_aligned(). This avoids dependency on the workspace
allocator. It fixes also a problem on some platforms (e.g. QorIQ) where
at this early point in the system initialization the top of the RAM is
used by low-level startup code on secondary processors (boot pages).
Update #3507.
|
|
|
|
|
|
|
|
|
|
|
| |
Statically allocate the objects information together with the initial
set of objects either via <rtems/confdefs.h>. Provide default object
informations with zero objects via librtemscpu.a. This greatly
simplifies the workspace size estimate. RTEMS applications which do not
use the unlimited objects option are easier to debug since all objects
reside now in statically allocated objects of the right types.
Close #3621.
|
|
|
|
|
|
|
| |
Use Objects_Information::objects_per_block to provide this information.
Add and use _Objects_Is_auto_extend().
Update #3621.
|
|
|
|
|
|
|
| |
Remove Objects_Information::the_class. This information is already
contained in Objects_Information::maximum_id.
Update #3621.
|
|
|
|
|
|
|
| |
This information is already present in Objects_Information::maximum_id.
Add and use _Objects_Get_maximum_index().
Update #3621.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the maximum ID for the ID to object translation. Using the maximum
ID gets rid of an additional load from the object information in
_Objects_Get(). In addition, object lookups fail for every ID in case
the object information is cleared to zero. This makes it a bit more
robust during system startup (see new tests in spconfig02).
The local table no longer needs a NULL pointer entry at array index
zero. Adjust all the object iteration loops accordingly.
Remove Objects_Information::minimum_id since it contains only redundant
information. Add _Objects_Get_minimum_id() to get the minimum ID.
Update #3621.
|
|
|
|
|
|
|
|
| |
Rename Objects_Information::allocation_size in
Objects_Information::objects_per_block. Adjust integer types in
_Objects_Shrink_information() and _Objects_Free().
Update #3621.
|
|
|
|
|
|
|
|
| |
Rename Objects_Information::size to Objects_Information::object_size.
Change its type from size_t to uint16_t and move it to reduce the size
of Objects_Information.
Update #3621.
|
|
|
|
|
|
| |
Use Objects_Information::name_length to store this information.
Update #3621.
|
|
|
|
| |
Update #3621.
|
|
|
|
|
|
|
| |
Remove <rtems/score/chainimpl.h> include from
<rtems/score/smplockstats.h>.
Close #3598.
|
| |
|
|
|
|
| |
Close #3602.
|
|
|
|
|
|
|
| |
Separate the definitions related to watchdog ticks from the watchdog
structures.
Update #3598.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename
* _Configuration_Interrupt_stack_area_begin in _ISR_Stack_area_begin,
* _Configuration_Interrupt_stack_area_end in _ISR_Stack_area_end, and
* _Configuration_Interrupt_stack_size in _ISR_Stack_size.
Move definitions to <rtems/score/isr.h>. The new names are considerable
shorter and in the right namespace.
Update #3459.
|
|
|
|
|
|
|
| |
Reduce structure internal padding. Group members used by _Objects_Get()
together. Reduce size of some members.
Format and simplify _Objects_Extend_information().
|
|
|
|
| |
Update #2514.
|
|
|
|
|
|
| |
Use separate configuration variables to avoid false dependencies.
Update #2514.
|
|
|
|
|
|
|
|
|
| |
Enable support for string objects names unconditionally. Add const
qualifier throughout. Split _Objects_Namespace_remove() into
_Objects_Namespace_remove_u32() and _Objects_Namespace_remove_string()
to avoid an unnecessary dependency on _Workspace_Free().
Update #2514.
|
|
|
|
| |
Update #2514.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The configured interrupt stack size (CONFIGURE_INTERRUPT_STACK_SIZE) is
checked against the minimum task stack size. The minium tasks task
stack size is also a configuration option
(CONFIGURE_MINIMUM_TASK_STACK_SIZE). So, this check does not really
help in case of configuration errors. In addition, the interrupt stack
is also re-used as the initialization stack in most BSPs. It is
probably better to use a stack checker to detect problems.
Update #3459.
|