Subversion Repositories HelenOS

Rev

Go to most recent revision | Show changed files | Details | Compare with Previous | Blame | RSS feed

Filtering Options

Rev Age Author Path Log message Diff
2637 6040 d 18 h cejka /trunk/ Extended IPC_M_CONNECT_TO_ME to use 3 user defined parameters.
Phone identifier is passed in ARG5.
 
2636 6042 d 17 h jermar /trunk/ Update comments wrt the previous commit.
Minor formatting fixes.
 
2635 6042 d 18 h cejka /trunk/ Function ipc_connect_me_to sends 3 user defined arguments now.
One argument added also to ipc_forward_fast.
Fixed devmap and improved its test.
 
2632 6043 d 13 h decky /trunk/kernel/generic/src/proc/ try to kill the tasks fewer times by introducing a delay in iterations  
2626 6050 d 4 h jermar /trunk/kernel/generic/ Support for 5 payload arguments for IPC irq notifications and the pseudo code.  
2623 6050 d 23 h jermar /trunk/kernel/generic/ Introduce the IPC_FF_ROUTE_FROM_ME forwarding flag.  
2622 6051 d 0 h jermar /trunk/ Add mode argument to IPC forward.
This argument can be used to modify the way forward behaves.
 
2620 6053 d 5 h jermar /trunk/ Be more deterministic when a user accidently uses fast version of IPC
call/answer instead of the full one and passes fewer arguments than required by
the recipient of the call/response.

and the recipient interprets arguments that
were actually not passed by the sender.
 
2619 6054 d 16 h jermar /trunk/ Modify ipc_answer_*() to make use of all six syscall arguments. The recommended
means of answering calls is via the ipc_answer_m() macros (where m denotes the
number of return arguments) that automatically decide between the fast register
version or the slow universal version of ipc_answer().
 
2618 6055 d 5 h jermar /trunk/ Modify asynchronous IPC to make use of all six syscall arguments. The preferred
means of asynchronous communication is now via the set of ipc_call_async_m()
macros, where m is the number of payload arguments passed to the kernel. These
macros will automatically decide between the fast and the universal slow version
of ipc_call_async.
 
2617 6055 d 21 h jermar /trunk/kernel/generic/src/ipc/ STRUCT_TO_USPACE may fail in sys_ipc_call_sync_fast.  
2615 6056 d 2 h jermar /trunk/ Modify synchronous IPC to make use of all six syscall arguments. The preferred
means of synchronous communication is now via the set of ipc_call_sync_m_n()
macros, where m is the number of payload arguments passed to the kernel and n is
the number of return values. These macros will automatically decide between the
fast and the universal slow version of ipc_call_sync.
 
2614 6056 d 23 h jermar /trunk/kernel/generic/include/ipc/ Grow the IPC data structures from 3 to 5 payload arguments.
No IPC API changes so far.
 
2605 6058 d 22 h jermar /trunk/ Start support for six syscall arguments.
This breaks all architectures.
 
2601 6063 d 21 h jermar /trunk/kernel/generic/src/ipc/ Fix and improve two IPC related comments.  
2574 6079 d 18 h jermar /trunk/kernel/generic/src/lib/ Fix elf.c's formatting and add code that can be later enhanced and used to
remember task's TLS section alignment, address and size.
 
2573 6082 d 19 h jermar /trunk/kernel/generic/include/lib/ Add SHF_TLS ELF section header flag.
This will be needed for detecting alignment of TLS sections of userspace tasks
loaded at runtime.
 
2572 6101 d 9 h jermar /trunk/kernel/ Remove duplicit implementation of strlen() in kernel, rename is_digit(),
is_white() and co. to their standard names (e.g. isdigit(), isspace()) and
remove duplicit implementation of isdigit(). Fix cstyle in kernel printf()
implementation.
 
2571 6101 d 23 h jermar /trunk/kernel/generic/src/printf/ Fix the string printing precision bug also in the kernel.  
2557 6107 d 2 h jermar /trunk/kernel/generic/src/ipc/ Enable forwarding of IPC_M_AS_AREA_SEND, IPC_M_AS_AREA_RECV, IPC_M_DATA_SEND
calls. In order to prevent the forwarder from cloberring the call data (i.e.
source and destination address, and size) by treating these three methods as
immutable on forward. This feature is experimental, but has huge benefits in
that it can significantly reduce the amount of data sharing (the middle man need
not modify its address space mappings) or the amount of data copying (the middle
man need not receive the data from the sender and then resend them to the next
recipient). As a result, it can reduce N such calls for a communication channel
with N tasks along the way to 1 such call.
 

Show All