040362e379
. make exec() callers (i.e. vfs and rs) determine the memory layout by explicitly reserving regions using mmap() calls on behalf of the exec()ing process, i.e. handling all of the exec logic, thereby eliminating all special exec() knowledge from VM. . the new procedure is: clear the exec()ing process first, then call third-party mmap()s to reserve memory, then copy the executable file section contents in, all using callbacks tailored to the caller's way of starting an executable . i.e. no more explicit EXEC_NEWMEM-style calls in PM or VM as with rigid 2-section arguments . this naturally allows generalizing exec() by simply loading all ELF sections . drop/merge of lots of duplicate exec() code into libexec . not copying the code sections to vfs and into the executable again is a measurable performance improvement (about 3.3% faster for 'make' in src/servers/)
24 lines
885 B
C
24 lines
885 B
C
#include <machine/vm.h>
|
|
|
|
/* And what is the highest addressable piece of memory, when in paged
|
|
* mode? Some data for kernel and stack are subtracted from this, the
|
|
* final results stored in bytes in arch.vm_data_top.
|
|
*/
|
|
#define VM_DATATOP 0xFFFFF000
|
|
|
|
#define SLAB_PAGESIZE I386_PAGE_SIZE
|
|
#define VM_PAGE_SIZE I386_PAGE_SIZE
|
|
|
|
/* Where do processes start in linear (i.e. page table) memory? */
|
|
#define VM_PROCSTART (I386_BIG_PAGE_SIZE*100)
|
|
|
|
#define CLICKSPERPAGE (I386_PAGE_SIZE/CLICK_SIZE)
|
|
|
|
/* Where is the kernel? */
|
|
#define KERNEL_TEXT CLICK2ABS(vmproc[VMP_SYSTEM].vm_arch.vm_seg[T].mem_phys)
|
|
#define KERNEL_TEXT_LEN CLICK2ABS(vmproc[VMP_SYSTEM].vm_arch.vm_seg[T].mem_len)
|
|
#define KERNEL_DATA CLICK2ABS(vmproc[VMP_SYSTEM].vm_arch.vm_seg[D].mem_phys)
|
|
#define KERNEL_DATA_LEN CLICK2ABS(vmproc[VMP_SYSTEM].vm_arch.vm_seg[D].mem_len \
|
|
+ vmproc[VMP_SYSTEM].vm_arch.vm_seg[S].mem_len)
|
|
|