rt-thread.git/src, branch v1.2.0Unnamed repository; edit this file 'description' to name the repository.http://cgit.235523.xyz/rt-thread.git/atom/src?h=v1.2.02013-12-21T03:31:40Zkernel: let rt_thread_idle_excute loop until there is no dead thread2013-12-21T03:31:40ZGrissiomchaos.proton@gmail.com2013-12-21T03:31:40Zurn:sha1:04f432f47b906e129209daf8e505ac0f6b57ebd0
Out side world is difficult to tell whethere there is dead thread
remaining. If rt_thread_idle_excute only do one cleanup, it's hard to
finish cleanups outside the idle thread. So let is loop and do all the
cleanups in one call.
kernel: add rt_critical_level that return the lock count of scheduler2013-12-21T03:27:26ZGrissiomchaos.proton@gmail.com2013-12-21T03:24:37Zurn:sha1:408ac34bc2d762db7019a14cc5caf8af4df57b43
Out side world may be interested in whether the scheduler is locked or
not. Provide an API to tell that.
kernel: timer: fix compiling bug in d59aa279c37b72013-10-19T13:07:14ZGrissiomchaos.proton@gmail.com2013-10-19T13:07:14Zurn:sha1:6d9e793388cf078647fe7617266ad6efae5edb18Merge pull request #173 from grissiom/new-timer2013-10-17T22:44:20ZBernard Xiongbernard.xiong@gmail.com2013-10-17T22:44:20Zurn:sha1:3eac58ce8e71ea7993a1febb159c2b156f3835af
kernel: use skip list to implement timer listMerge pull request #161 from aozima/pulls2013-10-17T22:43:56ZBernard Xiongbernard.xiong@gmail.com2013-10-17T22:43:56Zurn:sha1:c29ff6b0ac0456f5275e6a35c8d8ba0ee8d743c1
make sure the device is in STREAM mode when used by rt_kprintf.kernel: mutex could only be released in thread context2013-10-14T01:50:18ZGrissiomchaos.proton@gmail.com2013-10-14T01:50:18Zurn:sha1:b72001fcac18d2c37c24e423cc7e15fe900dc172
Mutex has the idea of ownership, only the thread which owns the mutex
can release it. So rt_mutex_release could only be called in thread
context. Add a debug guard to it.
kernel: use skip list to implement timer list2013-10-12T14:48:29ZGrissiomchaos.proton@gmail.com2013-09-26T07:52:02Zurn:sha1:d59aa279c37b7aba07385a3a2cb3057bce6c5fea
Skip list is a "random" data structure that in high possibilities it
would get O(log(N)) time complexity in inserting while the old list get
O(N). Forthermore, when set RT_TIMER_SKIP_LIST_LEVEL to 1, it will just
the same as the old double linked list, both in time and space
complexity.
Benchmarks shows that when RT_TIMER_SKIP_LIST_LEVEL is 3, the average
time of random insertion of new timer is about 2 times faster than the
old timer when there are 100 timers and 3 times faster when there are
200 timers.
However, it restores the deprecated funcion rt_system_timer_init. BSPs
must invoke it upon system startup.
kernel: add RT_DEBUG_IN_THREAD_CONTEXT2013-10-11T14:51:38ZGrissiomchaos.proton@gmail.com2013-10-11T14:46:05Zurn:sha1:6f71308ef529bfcecd54daaa309d1336ef0c6366
In thread context means: 1) the scheduler has been started; 2) not in
interrupt context. It is more stronger than RT_DEBUG_NOT_IN_INTERRUPT.
With this commit, you will catch the error on situations like taking
mutex before scheduling instead of crashing on NULL pointer reference.
update rt_kprintf: make sure the device is in STREAM mode when used by rt_kprintf.2013-09-24T07:29:08Zaozimawuyangyong@gmail.com2013-09-24T07:25:24Zurn:sha1:cad12ee14e5b10721c04c4c26eabdfd3167bfc17kservice: export vsnprintf as rt_vsnprintf2013-09-23T03:34:13ZGrissiomchaos.proton@gmail.com2013-09-23T03:27:48Zurn:sha1:7b0a3afdf90e85cabe3e39f49a5c2aa22e3e3e8d
vsnprintf is a common string function that could be used in many places.
Using both vsnprintf in libc and vsnprintf in the RTT could make a
bigger image. Moreover, if newlib is not enabled when compiling with
GCC, referencing vsnprintf will lead to link error:
.../arm-none-eabi/lib/armv7-ar/thumb/softfp/libc.a(lib_a-sbrkr.o):
In function `_sbrk_r':
sbrkr.c:(.text._sbrk_r+0xc): undefined reference to `_sbrk'
collect2: error: ld returned 1 exit status
Using rt_vsnprintf could avoid such problem.