| Rev |
Age |
Author |
Path |
Log message |
Diff |
| 3569 |
5653 d 19 h |
svoboda |
/branches/dynload/ |
Merge latest trunk changes into dynload. |
|
| 3448 |
5704 d 21 h |
svoboda |
/branches/dynload/ |
Merge latest trunk changes into dynload |
|
| 3190 |
5784 d 17 h |
svoboda |
/branches/dynload/ |
Remove vestiges of loading code coming from trunk |
|
| 3153 |
5798 d 17 h |
svoboda |
/branches/dynload/ |
Merge latest trunk changes into dynload |
|
| 3150 |
5798 d 17 h |
svoboda |
/branches/dynload/ |
Merge trunk changes up to r3090 into dynload (still broken) |
|
| 3149 |
5798 d 17 h |
svoboda |
/branches/dynload/ |
Merge trunk changes up to r3071 into dynload (broken) |
|
| 2927 |
5830 d 20 h |
decky |
/branches/dynload/ |
added dynload branch |
|
| 2907 |
5833 d 15 h |
jermar |
/trunk/kernel/generic/src/proc/ |
Improve comment for thread_create(). |
|
| 2790 |
5876 d 20 h |
jermar |
/trunk/kernel/generic/src/proc/ |
Fix typo ALV tree vs. AVL tree. |
|
| 2712 |
5934 d 16 h |
decky |
/trunk/kernel/ |
prettyprint output |
|
| 2504 |
6121 d 11 h |
jermar |
/trunk/kernel/generic/ |
Give the AVL tree walkers the possibility to take an argument.
Each walker is now supposed to return a bool value to support walk termination.
Switch over from the tasks_btree B+tree to tasks_tree AVL tree.
This makes the fix for ticket #48 complete. |
|
| 2502 |
6121 d 17 h |
jermar |
/trunk/kernel/generic/ |
Replace the threads_btree B+tree with an AVL tree. The new variable is called
threads_tree. For printing list of threads, use the new AVL tree walker
mechanism.
This solves half of ticket #48. |
|
| 2487 |
6148 d 12 h |
jermar |
/trunk/kernel/generic/src/proc/ |
Kernel stack address was printed twice. |
|
| 2470 |
6167 d 9 h |
jermar |
/trunk/ |
Fix a double-free recently introduced in revision r2436.
Add a comment clarifying the life-cycle of the kernel_uarg structure.
Comment out the freeing of userspace thread stack while still running on it.
This should be fixed by implementing userspace version of thread_join(). |
|
| 2451 |
6176 d 11 h |
jermar |
/trunk/kernel/generic/ |
JoinMe -> Lingering |
|
| 2446 |
6179 d 15 h |
jermar |
/trunk/kernel/generic/ |
More efficient and simpler task termination.
Based on the assumption, that after its creation, only the task itself can create more threads for itself,
the last thread with userspace context to execute thread_exit() will perform futex and IPC cleanup. When
the task has no threads, it is destroyed. Both the cleanup and destruction is controlled by reference
counting.
As for userspace threads, even though there could be a global garbage collector for joining threads, it is
much simpler if the uinit thread detaches itself before switching to userspace.
task_kill() is now an idempotent operation. It just instructs the threads within a task to exit.
Change in the name of a thread state: Undead -> JoinMe. |
|
| 2440 |
6180 d 9 h |
jermar |
/trunk/kernel/generic/ |
Fix the problem with sys_thread_create() by splitting the create and attach functionality of
thread_create(). Now it is possible to specify a flag that will cause thread_create() to only allocate and
initialize the thread structure. A call to thread_attach() will make the thread visible to the system.
This arrangement makes it easier to undo creation of a thread in case of a failure in sys_thread_create(). |
|
| 2436 |
6181 d 11 h |
jermar |
/trunk/ |
Fix two memory leaks.
In kernel, kernel_uarg structure needs to be deallocated when a thread
with userspace context is destroyed.
In userspace, the return value of the SYS_THREAD_CREATE must be checked
for error conditions and in case of error, uarg and stack must be freed
up. |
|
| 2268 |
6223 d 11 h |
jermar |
/trunk/kernel/generic/ |
Document and assert proper usage of THREAD_FLAG_WIRED.
Original patch by Jan Hudecek. |
|
| 2229 |
6232 d 17 h |
jermar |
/trunk/ |
Revert some of the changes introduced in revision 2209.
I think it is not correct to remove serialization of pseudo threads in printf_core.c.
With thread-level futex serialization, several pseudo threads running in one thread could easily deadlock
the task.
Add a dedicated futex serialization to thread1.c test only. |
|