| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This allows the linker garbage collection to perform its work.
Update #3835.
|
|
|
|
|
|
| |
Use the stack area to allocate the TLS area.
Update #3835.
|
|
|
|
|
|
|
|
|
|
|
| |
Use the stack area to allocate the FP context. This considerably
simplifies the application configuration since the task count no longer
influences the configured work space size. With this change the stack
space size is overestimated since an FP context for each thread is
accounted. Memory constraint applications can use the stack size for
fine tuning.
Update #3835.
|
|
|
|
|
|
| |
This call is superfluous since _Thread_Initialize() will do this also.
Update #3835.
|
|
|
|
| |
Update #3835.
|
|
|
|
|
|
| |
Remove superfluous Thread_Control::Start::stack member.
Update #3835.
|
|
|
|
| |
Update #3835.
|
|
|
|
|
|
|
|
| |
Canonical input processing was broken by
667501a314ba75f80f1c13c6b43dd35d0a00efd1 as shown by test case
termios09.
Update #3800.
|
|
|
|
|
|
|
| |
Replace the BSP_DIRTY_MEMORY BSP option with a CONFIGURE_DIRTY_MEMORY
configuration option.
Update #3843.
|
|
|
|
|
|
|
|
| |
Use a dedicate system initialization step to zero the memory used for
the workspace and C program heap.
This avoids dead code in case CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY is
not configured.
|
|
|
|
|
|
|
| |
Canonicalize CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY and use
defined/undefined instead of TRUE/FALSE.
Close #3862.
|
|
|
|
| |
Update #3863.
|
|
|
|
| |
Update #3865.
|
|
|
|
|
|
| |
Do not cast to unsigned int to avoid an unsigned long long enum type.
Use a multiplication/division instead to preserve the signedness of the
POSIX status.
|
|
|
|
| |
Update #3861.
|
|
|
|
|
|
|
|
| |
Use RTEMS_SYSINIT_ORDER_LAST_BUT_5 instead of RTEMS_SYSINIT_ORDER_LAST
to allow applications and support functions to place system
initialization handlers behind the standard handlers.
Update #3838.
|
|
|
|
| |
Update #3838.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The work area initialization was done by the BSP through
bsp_work_area_initialize(). This approach predated the system
initialization through the system initialization linker set. The
workspace and C program heap were unconditionally initialized. The aim
is to support RTEMS application configurations which do not need the
workspace and C program heap. In these configurations, the workspace
and C prgram heap should not get initialized.
Change all bsp_work_area_initialize() to implement _Memory_Get()
instead. Move the dirty memory, sbrk(), per-CPU data, workspace, and
malloc() heap initialization into separate system initialization steps.
This makes it also easier to test the individual initialization steps.
This change adds a dependency to _Heap_Extend() to all BSPs. This
dependency will be removed in a follow up change.
Update #3838.
|
|
|
|
|
|
|
| |
Use a dedicated system initialization step for the stack checker
interrupt stack support.
Update #3838.
|
|
|
|
|
|
|
| |
Add new BSP system initialization step for work to be performed before
the work areas are initialized.
Update #3838.
|
|
|
|
| |
Update #3838.
|
|
|
|
| |
Update #3838.
|
|
|
|
| |
Only align per-processor data in SMP configurations.
|
|
|
|
| |
Fix T_check_task_context() in RTEMS_SMP with RTEMS_DEBUG configurations.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Modify the status code returned by _CORE_message_queue_Submit() when it
detects a wait about to happen in an ISR (which would be deadly) to
return a status which translated to EAGAIN instead of ENOMEM.
This is only relevant for POSIX message queues, since Classic API message
queues cannot block on send.
The motivation is to match the "most related" errno value returned from
mq_send() and mq_timedsend() according to POSIX, via Open Group:
[EAGAIN]
The O_NONBLOCK flag is set in the message queue description
associated with mqdes, and the specified message queue is full.
or via the RTEMS POSIX users documentation
EAGAIN
The message queue is non-blocking, and there is no room on the queue
for another message as specified by the mq_maxmsg.
Neither of these matches the case ofi avoided ISR wait perfectly, but
they seem to be the closest equivalent, unless it is desirable to keep a
new non-standard error for this case. It is presumed that this is not
desirable.
The previously returned ENOMEM error value is not documented in either
the Open Group or the RTEMS POSIX uses documentation. A companion patch
corrects the documentation to include this error condition.
Based on the discussion in:
https://lists.rtems.org/pipermail/devel/2020-January/056891.html
closes #3857.
Message-Id: <CAF9ehCW5P12ZkZja4UPYTbdBFUyC1VKVL-tU7nyUtvK1Lz2Z3g@mail.gmail.com>
|
|
|
|
|
|
|
|
|
| |
The FACE Technical Standard, Edition 3.0 and later require the definition
of the subcommand SOCKCLOSE in <devctl.h>.
Reference: ​https://www.opengroup.org/face
closes #3856.
|
|
|
|
|
| |
Dead code identified by Coverity (CID 1456674). The value of ret
at line 358 is always 0.
|
|
|
|
|
| |
Dead code identified by Coverity (CID 1456678). The value of ret
at line 293 is always 0.
|
|
|
|
|
| |
Remove THREAD_STATUS_PROXY_BLOCKING and replace it with
STATUS_PROXY_BLOCKING.
|
|
|
|
| |
Update #2408.
|
|
|
|
|
|
|
| |
The objects node is statically initialized to one. Clear the node field
before it is set.
Update #3621.
|
| |
|
|
|
|
|
| |
Use the user provided now handler of the test configuration to get the
time in T_now().
|
| |
|
|
|
|
|
|
|
|
| |
Use CONFIGURE_MAXIMUM_PROCESSORS to configure the EDF SMP scheduler
context. This avoids hard to debug configuration errors resulting in
memory corruptions.
Close #3815.
|
|
|
|
|
|
|
| |
- This patch is based on the patch attached to #3552 submitted
by jameszxj.
Closes #3552
|
|
|
|
|
|
| |
Bug was introduced by previous commit.
Update #3845.
|
|
|
|
| |
Update #3845.
|
|
|
|
|
|
|
| |
Rename CONFIGURE_LIBIO_MAXIMUM_FILE_DESCRIPTORS into
CONFIGURE_MAXIMUM_FILE_DESCRIPTORS.
Update #3753.
|
|
|
|
|
|
| |
Remove CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE.
Update #3844.
|
| |
|
|
|
|
|
|
| |
This function is unused.
Update #3735.
|
|
|
|
| |
Update #3735.
|
|
|
|
| |
Update #3735.
|
|
|
|
|
|
|
| |
Replace the user MPCI configuration table with a system provided
_MPCI_Configuration.
Update #3735.
|
|
|
|
| |
Update #3841.
|
|
|
|
|
|
|
| |
Obsolete the CONFIGURE_HAS_OWN_MULTIPROCESSING_TABLE configuration
option.
Update #3735.
|
|
|
|
|
|
|
|
| |
Obsolete undocumented configuration options CONFIGURE_MAXIMUM_FIFOS and
CONFIGURE_MAXIMUM_PIPES. Replace these options with the new
CONFIGURE_IMFS_ENABLE_MKFIFO configuration option.
Update #3840.
|
| |
|