| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Update #3117.
Update #3182.
|
|
|
|
|
|
|
|
|
| |
Rename _Thread_queue_Context_set_do_nothing_enqueue_callout() into
_Thread_queue_Context_set_enqueue_do_nothing_extra(). More
_Thread_queue_Context_set_enqueue_*() functions will follow.
Update #3117.
Update #3182.
|
|
|
|
|
| |
Update #3117.
Update #3182.
|
|
|
|
|
| |
Update #3117.
Update #3182.
|
|
|
|
|
| |
Update #3117.
Update #3182.
|
|
|
|
|
|
|
| |
Move it from the configuration to a separate variable.
Update #3117.
Update #3182.
|
|
|
|
|
| |
Update #3117.
Update #3182.
|
|
|
|
|
| |
Update #3117.
Update #3182.
|
|
|
|
|
| |
Update #3117.
Update #3182.
|
|
|
|
|
|
|
|
|
|
| |
Rename _Watchdog_Ticks_from_*() to _Watchdog_Realtime_from_*().
This highlights that these routines are used for the CLOCK_REALTIME
watchdogs (in contrast to CLOCK_MONOTONIC).
Update #3117.
Update #3182.
|
|
|
|
|
|
|
|
| |
A non-integer clock ticks per second value may lead to inaccurate time
format conversions.
Update #3117.
Update #3182.
|
|
|
|
|
|
|
| |
Remove the cast so that it can be used in C pre-processor directives.
Update #3117.
Update #3182.
|
|
|
|
|
|
|
|
| |
This value is frequently used. Avoid the function call overhead and the
integer division at run-time.
Update #3117.
Update #3182.
|
|
|
|
|
|
|
|
| |
Replace _Thread_Timer_insert_monotonic() with
_Thread_Add_timeout_ticks().
Update #3117.
Update #3182.
|
|
|
|
| |
Update #3182.
|
| |
|
|
|
|
|
|
| |
Reduce test context size in non-SMP configurations.
Close #3200.
|
|
|
|
| |
Updates #3170.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Remove the printf support leaving the direct printk support configured
with TESTS_USE_PRINTK and all other output goes via a buffered vsniprintf
call to printk.
- Control the test's single init for functions and global data with
TEST_INIT and not CONFIGURE_INIT. They are now separate.
Updates #3170.
|
|
|
|
| |
Update #2514.
|
| |
|
| |
|
|
|
|
| |
Update #2514.
|
|
|
|
|
|
|
|
|
|
|
| |
It seems that the DWT CYCCNT does not advance when the CPU waits on a
WFI instruction.
That leads to the effect that for example on the atsamv BSP a sleep(1)
needs something in the range of a few minutes (depending on the
configured systick). A debugger might disables some deep sleep modes so
that the problem only appears if the application is executed without a
debugger.
|
|
|
|
|
| |
Ensure that the time flow of CLOCK_REALTIME and CLOCK_MONOTONIC is close to
the clock driver ticks time flow.
|
|
|
|
|
|
|
|
| |
Update #2674.
Update #3112.
Update #3113.
Update #3114.
Update #3115.
|
|
|
|
|
|
|
|
| |
Updates of the line control and baud divisor while transfers are in
progress may lead to unpredictable behaviour on some chips. Perform the
updates only if necessary.
Close #3198.
|
|
|
|
|
|
| |
Move unblocked signals initialization to pthread_create().
Update #2514.
|
|
|
|
|
|
|
|
| |
Move sporadic server scheduler parameters to
POSIX_API_Control::Sporadic. Remove redundant scheduler priority
parameter.
Update #2514.
|
|
|
|
|
|
| |
This member is only used by the sporadic server support.
Update #2514.
|
|
|
|
|
|
| |
The thread POSIX API control must be fully initialized in
_POSIX_Threads_Create_extension(), otherwise a pthread_setschedparam()
is broken for all threads not created with pthread_create().
|
|
|
|
|
|
|
|
| |
Rename _Watchdog_Per_CPU_insert_monotonic() in
_Watchdog_Per_CPU_insert_ticks().
Update #3117.
Update #3182.
|
|
|
|
|
|
|
|
|
|
|
| |
Rename PER_CPU_WATCHDOG_RELATIVE in PER_CPU_WATCHDOG_MONOTONIC to
highlight the corresponding POSIX CLOCK_MONOTONIC.
Rename PER_CPU_WATCHDOG_ABSOLUTE in PER_CPU_WATCHDOG_REALTIME to
highlight the corresponding POSIX CLOCK_REALTIME.
Update #3117.
Update #3182.
|
|
|
|
|
|
|
|
| |
Initial idea has been that check for both, TMS570_SCI_FLR_TX_EMPTY
and TMS570_SCI_FLR_TXRDY is required before console driver parameters
update.
closes #2883.
|
| |
|
| |
|
|
|
|
| |
Closes #3130.
|
| |
|
|
|
|
|
|
|
| |
This solves a build dependency issue, e.g. building tests before
librtemsbsp.a exists.
Close #3079.
|
|
|
|
| |
Update #3079.
|
|
|
|
| |
Allow to overwrite the optimization settings during configuration.
|
| |
|
|
|
|
|
| |
Update #2740.
Close #3179.
|
|
|
|
|
| |
Update #2514.
Update #3179.
|
|
|
|
|
|
|
|
|
| |
Update #2674.
Close #3112.
Close #3113.
Close #3114.
Close #3115.
Close #3116.
|
|
|
|
| |
Update #3175.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The th_bintime, th_microtime and th_nanotime members of the timehand all cache the last system time (uptime + boottime). Only the format differs. Do not re-calculate the bintime and simply use the value used to calculate the microtime and nanotime.
Group all the updates under the relevant comment. Remove obsoleted
XXX part.
Submitted by: Sebastian Huber <sebastian.huber@embedded-brains.de>
MFC after: 1 week
Update #3175.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add missing pieces of r315280
I moved this branch from github to a private server, and pulled from the
wrong one when committing r315280, so I failed to include two recent commits.
Thankfully, they were only cosmetic and were included in the review.
Specifically:
Add documentation, polish comments, and improve style(9).
Tested by: pho (r315280)
MFC after: 2 weeks
Sponsored by: Dell EMC
Differential Revision: https://reviews.freebsd.org/D9791
Update #3175.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the RTC is adjusted, reevaluate absolute sleep times based on the RTC
POSIX 2008 says this about clock_settime(2):
If the value of the CLOCK_REALTIME clock is set via clock_settime(),
the new value of the clock shall be used to determine the time
of expiration for absolute time services based upon the
CLOCK_REALTIME clock. This applies to the time at which armed
absolute timers expire. If the absolute time requested at the
invocation of such a time service is before the new value of
the clock, the time service shall expire immediately as if the
clock had reached the requested time normally.
Setting the value of the CLOCK_REALTIME clock via clock_settime()
shall have no effect on threads that are blocked waiting for
a relative time service based upon this clock, including the
nanosleep() function; nor on the expiration of relative timers
based upon this clock. Consequently, these time services shall
expire when the requested relative interval elapses, independently
of the new or old value of the clock.
When the real-time clock is adjusted, such as by clock_settime(3),
wake any threads sleeping until an absolute real-clock time.
Such a sleep is indicated by a non-zero td_rtcgen. The sleep functions
will set that field to zero and return zero to tell the caller
to reevaluate its sleep duration based on the new value of the clock.
At present, this affects the following functions:
pthread_cond_timedwait(3)
pthread_mutex_timedlock(3)
pthread_rwlock_timedrdlock(3)
pthread_rwlock_timedwrlock(3)
sem_timedwait(3)
sem_clockwait_np(3)
I'm working on adding clock_nanosleep(2), which will also be affected.
Reported by: Sebastian Huber <sebastian.huber@embedded-brains.de>
Reviewed by: jhb, kib
MFC after: 2 weeks
Relnotes: yes
Sponsored by: Dell EMC
Differential Revision: https://reviews.freebsd.org/D9791
Update #3175.
|