| Rev |
Age |
Author |
Path |
Log message |
Diff |
| 2451 |
6177 d 1 h |
jermar |
/trunk/kernel/generic/ |
JoinMe -> Lingering |
|
| 2447 |
6180 d 5 h |
jermar |
/trunk/kernel/generic/src/main/ |
Split accidently joined lines. |
|
| 2446 |
6180 d 5 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. |
|
| 2445 |
6180 d 6 h |
decky |
/trunk/ |
initial merge of branches/fs
(not finished, huge cleanup is needed) |
|
| 2444 |
6180 d 21 h |
jermar |
/trunk/kernel/ |
First fixes for suncc support.
It is going to be a long way... |
|
| 2441 |
6180 d 23 h |
decky |
/trunk/kernel/ |
fix ICC compilation |
|
| 2440 |
6180 d 23 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 |
6182 d 1 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. |
|
| 2359 |
6194 d 10 h |
jermar |
/trunk/ |
Improve comments for the IPC subsystem.
Fix formatting and indentation. |
|
| 2319 |
6202 d 10 h |
decky |
/trunk/kernel/generic/src/console/ |
run mcall only on active CPUs |
|
| 2310 |
6205 d 2 h |
jermar |
/trunk/kernel/generic/ |
Cleanup the waitq_wakeup() interface.
Replace numeric constants (i.e. 0)
and boolean constants (i.e. false) with
more readable WAKEUP_FIRST. Also change the
type of the second argument of waitq_wakeup()
to a newly introduced type wakeup_mode_t.
Fix behaviour of waitq_wakeup() in case
that WAKEUP_ALL semantics is required
but no threads are sleeping in the wait
queue. This is a similar fix to that of
Jan Hudecek committed in the RCU branch,
but, IMHO, is more straightforward and
also doesn't eat up previous missed
wakeups. |
|
| 2285 |
6217 d 9 h |
jermar |
/trunk/kernel/generic/src/proc/ |
Formatting and indentation fixes. |
|
| 2275 |
6222 d 2 h |
decky |
/trunk/kernel/generic/ |
add fancy uptime kconsole command |
|
| 2272 |
6223 d 2 h |
jermar |
/trunk/kernel/ |
Indentation and formatting fixes. |
|
| 2268 |
6224 d 1 h |
jermar |
/trunk/kernel/generic/ |
Document and assert proper usage of THREAD_FLAG_WIRED.
Original patch by Jan Hudecek. |
|
| 2229 |
6233 d 7 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. |
|
| 2227 |
6233 d 14 h |
decky |
/trunk/kernel/ |
start shutdown infrastructure |
|
| 2224 |
6233 d 21 h |
decky |
/trunk/kernel/generic/src/console/ |
detach joined thread |
|
| 2223 |
6233 d 21 h |
decky |
/trunk/kernel/generic/src/ |
add mcall0 command (calling a function on each CPU) |
|
| 2222 |
6234 d 0 h |
decky |
/trunk/kernel/ |
map kernel pages explicitly as writable (this solves compatibility issues with Intel Core 2)
make VESA framebuffer initialization more robust |
|