minix/lib/libsys/sys_newmap.c

#include "syslib.h"

int sys_newmap(
endpoint_t proc_ep,		/* process whose map is to be changed */
struct mem_map *ptr		/* pointer to new map */
)
{
/* A process has been assigned a new memory map.  Tell the kernel. */

  message m;

  m.PR_ENDPT = proc_ep;
  m.PR_MEM_PTR = (char *) ptr;
  return(_kernel_call(SYS_NEWMAP, &m));
}
Initial revision 2005-04-21 16:53:53 +02:00			`#include "syslib.h"`

retire PUBLIC, PRIVATE and FORWARD 2012-03-25 20:25:53 +02:00			`int sys_newmap(`
VM and kernel support for ELF 2011-02-27 00:00:55 +01:00			`endpoint_t proc_ep, /* process whose map is to be changed */`
			`struct mem_map ptr / pointer to new map */`
			`)`
Initial revision 2005-04-21 16:53:53 +02:00			`{`
			`/* A process has been assigned a new memory map. Tell the kernel. */`

			`message m;`

endpoint_t in syslib - headers use the endpoint_t in syslib.h and the implmentation was using int instead. Both uses endpoint_t now - every variable named like proc, proc_nr or proc_nr_e of type endpoint_t has name proc_ep now - endpoint_t defined as u32_t not int 2009-09-22 23:42:02 +02:00			`m.PR_ENDPT = proc_ep;`
Initial revision 2005-04-21 16:53:53 +02:00			`m.PR_MEM_PTR = (char *) ptr;`
Removal of the system task * Userspace change to use the new kernel calls - _taskcall(SYSTASK...) changed to _kernel_call(...) - int 32 reused for the kernel calls - _do_kernel_call() to make the trap to kernel - kernel_call() to make the actuall kernel call from C using _do_kernel_call() - unlike ipc call the kernel call always succeeds as kernel is always available, however, kernel may return an error * Kernel side implementation of kernel calls - the SYSTEm task does not run, only the proc table entry is preserved - every data_copy(SYSTEM is no data_copy(KERNEL - "locking" is an empty operation now as everything runs in kernel - sys_task() is replaced by kernel_call() which copies the message into kernel, dispatches the call to its handler and finishes by either copying the results back to userspace (if need be) or by suspending the process because of VM - suspended processes are later made runnable once the memory issue is resolved, picked up by the scheduler and only at this time the call is resumed (in fact restarted) which does not need to copy the message from userspace as the message is already saved in the process structure. - no ned for the vmrestart queue, the scheduler will restart the system calls - no special case in do_vmctl(), all requests remove the RTS_VMREQUEST flag 2010-02-09 16:20:09 +01:00			`return(_kernel_call(SYS_NEWMAP, &m));`
Initial revision 2005-04-21 16:53:53 +02:00			`}`