2012-03-21 23:51:18 +01:00
|
|
|
/* The kernel call implemented in this file:
|
|
|
|
|
* m_type: SYS_VUMAP
|
|
|
|
|
*
|
|
|
|
|
* The parameters for this kernel call are:
|
2014-05-22 10:05:44 +02:00
|
|
|
* m_lsys_krn_sys_vumap.endpt (grant owner, or SELF for local addresses)
|
|
|
|
|
* m_lsys_krn_sys_vumap.vaddr (address of virtual (input) vector)
|
|
|
|
|
* m_lsys_krn_sys_vumap.vcount (number of elements in virtual vector)
|
|
|
|
|
* m_lsys_krn_sys_vumap.offset (offset into first entry of input vector)
|
|
|
|
|
* m_lsys_krn_sys_vumap.access (safecopy access requested for input)
|
|
|
|
|
* m_lsys_krn_sys_vumap.paddr (address of physical (output) vector)
|
|
|
|
|
* m_lsys_krn_sys_vumap.pmax (maximum number of physical vector elements)
|
|
|
|
|
* m_krn_lsys_sys_vumap.pcount (upon return: number of elements filled)
|
2012-03-21 23:51:18 +01:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include "kernel/system.h"
|
|
|
|
|
|
|
|
|
|
#include <assert.h>
|
|
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
|
* do_vumap *
|
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
int do_vumap(struct proc *caller, message *m_ptr)
|
2012-03-21 23:51:18 +01:00
|
|
|
{
|
|
|
|
|
/* Map a vector of grants or local virtual addresses to physical addresses.
|
|
|
|
|
* Designed to be used by drivers to perform an efficient lookup of physical
|
|
|
|
|
* addresses for the purpose of direct DMA from/to a remote process.
|
|
|
|
|
*/
|
|
|
|
|
endpoint_t endpt, source, granter;
|
|
|
|
|
struct proc *procp;
|
|
|
|
|
struct vumap_vir vvec[MAPVEC_NR];
|
|
|
|
|
struct vumap_phys pvec[MAPVEC_NR];
|
No more intel/minix segments.
This commit removes all traces of Minix segments (the text/data/stack
memory map abstraction in the kernel) and significance of Intel segments
(hardware segments like CS, DS that add offsets to all addressing before
page table translation). This ultimately simplifies the memory layout
and addressing and makes the same layout possible on non-Intel
architectures.
There are only two types of addresses in the world now: virtual
and physical; even the kernel and processes have the same virtual
address space. Kernel and user processes can be distinguished at a
glance as processes won't use 0xF0000000 and above.
No static pre-allocated memory sizes exist any more.
Changes to booting:
. The pre_init.c leaves the kernel and modules exactly as
they were left by the bootloader in physical memory
. The kernel starts running using physical addressing,
loaded at a fixed location given in its linker script by the
bootloader. All code and data in this phase are linked to
this fixed low location.
. It makes a bootstrap pagetable to map itself to a
fixed high location (also in linker script) and jumps to
the high address. All code and data then use this high addressing.
. All code/data symbols linked at the low addresses is prefixed by
an objcopy step with __k_unpaged_*, so that that code cannot
reference highly-linked symbols (which aren't valid yet) or vice
versa (symbols that aren't valid any more).
. The two addressing modes are separated in the linker script by
collecting the unpaged_*.o objects and linking them with low
addresses, and linking the rest high. Some objects are linked
twice, once low and once high.
. The bootstrap phase passes a lot of information (e.g. free memory
list, physical location of the modules, etc.) using the kinfo
struct.
. After this bootstrap the low-linked part is freed.
. The kernel maps in VM into the bootstrap page table so that VM can
begin executing. Its first job is to make page tables for all other
boot processes. So VM runs before RS, and RS gets a fully dynamic,
VM-managed address space. VM gets its privilege info from RS as usual
but that happens after RS starts running.
. Both the kernel loading VM and VM organizing boot processes happen
using the libexec logic. This removes the last reason for VM to
still know much about exec() and vm/exec.c is gone.
Further Implementation:
. All segments are based at 0 and have a 4 GB limit.
. The kernel is mapped in at the top of the virtual address
space so as not to constrain the user processes.
. Processes do not use segments from the LDT at all; there are
no segments in the LDT any more, so no LLDT is needed.
. The Minix segments T/D/S are gone and so none of the
user-space or in-kernel copy functions use them. The copy
functions use a process endpoint of NONE to realize it's
a physical address, virtual otherwise.
. The umap call only makes sense to translate a virtual address
to a physical address now.
. Segments-related calls like newmap and alloc_segments are gone.
. All segments-related translation in VM is gone (vir2map etc).
. Initialization in VM is simpler as no moving around is necessary.
. VM and all other boot processes can be linked wherever they wish
and will be mapped in at the right location by the kernel and VM
respectively.
Other changes:
. The multiboot code is less special: it does not use mb_print
for its diagnostics any more but uses printf() as normal, saving
the output into the diagnostics buffer, only printing to the
screen using the direct print functions if a panic() occurs.
. The multiboot code uses the flexible 'free memory map list'
style to receive the list of free memory if available.
. The kernel determines the memory layout of the processes to
a degree: it tells VM where the kernel starts and ends and
where the kernel wants the top of the process to be. VM then
uses this entire range, i.e. the stack is right at the top,
and mmap()ped bits of memory are placed below that downwards,
and the break grows upwards.
Other Consequences:
. Every process gets its own page table as address spaces
can't be separated any more by segments.
. As all segments are 0-based, there is no distinction between
virtual and linear addresses, nor between userspace and
kernel addresses.
. Less work is done when context switching, leading to a net
performance increase. (8% faster on my machine for 'make servers'.)
. The layout and configuration of the GDT makes sysenter and syscall
possible.
2012-05-07 16:03:35 +02:00
|
|
|
vir_bytes vaddr, paddr, vir_addr;
|
2012-03-21 23:51:18 +01:00
|
|
|
phys_bytes phys_addr;
|
|
|
|
|
int i, r, proc_nr, vcount, pcount, pmax, access;
|
|
|
|
|
size_t size, chunk, offset;
|
|
|
|
|
|
|
|
|
|
endpt = caller->p_endpoint;
|
|
|
|
|
|
|
|
|
|
/* Retrieve and check input parameters. */
|
2014-05-22 10:05:44 +02:00
|
|
|
source = m_ptr->m_lsys_krn_sys_vumap.endpt;
|
|
|
|
|
vaddr = m_ptr->m_lsys_krn_sys_vumap.vaddr;
|
|
|
|
|
vcount = m_ptr->m_lsys_krn_sys_vumap.vcount;
|
|
|
|
|
offset = m_ptr->m_lsys_krn_sys_vumap.offset;
|
|
|
|
|
access = m_ptr->m_lsys_krn_sys_vumap.access;
|
|
|
|
|
paddr = m_ptr->m_lsys_krn_sys_vumap.paddr;
|
|
|
|
|
pmax = m_ptr->m_lsys_krn_sys_vumap.pmax;
|
2012-03-21 23:51:18 +01:00
|
|
|
|
|
|
|
|
if (vcount <= 0 || pmax <= 0)
|
|
|
|
|
return EINVAL;
|
|
|
|
|
|
|
|
|
|
if (vcount > MAPVEC_NR) vcount = MAPVEC_NR;
|
|
|
|
|
if (pmax > MAPVEC_NR) pmax = MAPVEC_NR;
|
|
|
|
|
|
|
|
|
|
/* Convert access to safecopy access flags. */
|
|
|
|
|
switch (access) {
|
|
|
|
|
case VUA_READ: access = CPF_READ; break;
|
|
|
|
|
case VUA_WRITE: access = CPF_WRITE; break;
|
|
|
|
|
case VUA_READ|VUA_WRITE: access = CPF_READ|CPF_WRITE; break;
|
|
|
|
|
default: return EINVAL;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Copy in the vector of virtual addresses. */
|
|
|
|
|
size = vcount * sizeof(vvec[0]);
|
|
|
|
|
|
|
|
|
|
if (data_copy(endpt, vaddr, KERNEL, (vir_bytes) vvec, size) != OK)
|
|
|
|
|
return EFAULT;
|
|
|
|
|
|
|
|
|
|
pcount = 0;
|
|
|
|
|
|
|
|
|
|
/* Go through the input entries, one at a time. Stop early in case the output
|
|
|
|
|
* vector has filled up.
|
|
|
|
|
*/
|
|
|
|
|
for (i = 0; i < vcount && pcount < pmax; i++) {
|
|
|
|
|
size = vvec[i].vv_size;
|
|
|
|
|
if (size <= offset)
|
|
|
|
|
return EINVAL;
|
|
|
|
|
size -= offset;
|
|
|
|
|
|
|
|
|
|
if (source != SELF) {
|
|
|
|
|
r = verify_grant(source, endpt, vvec[i].vv_grant, size, access,
|
make vfs & filesystems use failable copying
Change the kernel to add features to vircopy and safecopies so that
transparent copy fixing won't happen to avoid deadlocks, and such copies
fail with EFAULT.
Transparently making copying work from filesystems (as normally done by
the kernel & VM when copying fails because of missing/readonly memory)
is problematic as it can happen that, for file-mapped ranges, that that
same filesystem that is blocked on the copy request is needed to satisfy
the memory range, leading to deadlock. Dito for VFS itself, if done with
a blocking call.
This change makes the copying done from a filesystem fail in such cases
with EFAULT by VFS adding the CPF_TRY flag to the grants. If a FS call
fails with EFAULT, VFS will then request the range to be made available
to VM after the FS is unblocked, allowing it to be used to satisfy the
range if need be in another VFS thread.
Similarly, for datacopies that VFS itself does, it uses the failable
vircopy variant and callers use a wrapper that talk to VM if necessary
to get the copy to work.
. kernel: add CPF_TRY flag to safecopies
. kernel: only request writable ranges to VM for the
target buffer when copying fails
. do copying in VFS TRY-first
. some fixes in VM to build SANITYCHECK mode
. add regression test for the cases where
- a FS system call needs memory mapped in a process that the
FS itself must map.
- such a range covers more than one file-mapped region.
. add 'try' mode to vircopy, physcopy
. add flags field to copy kernel call messages
. if CP_FLAG_TRY is set, do not transparently try
to fix memory ranges
. for use by VFS when accessing user buffers to avoid
deadlock
. remove some obsolete backwards compatability assignments
. VFS: let thread scheduling work for VM requests too
Allows VFS to make calls to VM while suspending and resuming
the currently running thread. Does currently not work for the
main thread.
. VM: add fix memory range call for use by VFS
Change-Id: I295794269cea51a3163519a9cfe5901301d90b32
2014-01-16 14:22:13 +01:00
|
|
|
offset, &vir_addr, &granter, NULL);
|
2012-03-21 23:51:18 +01:00
|
|
|
if (r != OK)
|
|
|
|
|
return r;
|
|
|
|
|
} else {
|
|
|
|
|
vir_addr = vvec[i].vv_addr + offset;
|
|
|
|
|
granter = endpt;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
okendpt(granter, &proc_nr);
|
|
|
|
|
procp = proc_addr(proc_nr);
|
|
|
|
|
|
|
|
|
|
/* Each virtual range is made up of one or more physical ranges. */
|
|
|
|
|
while (size > 0 && pcount < pmax) {
|
No more intel/minix segments.
This commit removes all traces of Minix segments (the text/data/stack
memory map abstraction in the kernel) and significance of Intel segments
(hardware segments like CS, DS that add offsets to all addressing before
page table translation). This ultimately simplifies the memory layout
and addressing and makes the same layout possible on non-Intel
architectures.
There are only two types of addresses in the world now: virtual
and physical; even the kernel and processes have the same virtual
address space. Kernel and user processes can be distinguished at a
glance as processes won't use 0xF0000000 and above.
No static pre-allocated memory sizes exist any more.
Changes to booting:
. The pre_init.c leaves the kernel and modules exactly as
they were left by the bootloader in physical memory
. The kernel starts running using physical addressing,
loaded at a fixed location given in its linker script by the
bootloader. All code and data in this phase are linked to
this fixed low location.
. It makes a bootstrap pagetable to map itself to a
fixed high location (also in linker script) and jumps to
the high address. All code and data then use this high addressing.
. All code/data symbols linked at the low addresses is prefixed by
an objcopy step with __k_unpaged_*, so that that code cannot
reference highly-linked symbols (which aren't valid yet) or vice
versa (symbols that aren't valid any more).
. The two addressing modes are separated in the linker script by
collecting the unpaged_*.o objects and linking them with low
addresses, and linking the rest high. Some objects are linked
twice, once low and once high.
. The bootstrap phase passes a lot of information (e.g. free memory
list, physical location of the modules, etc.) using the kinfo
struct.
. After this bootstrap the low-linked part is freed.
. The kernel maps in VM into the bootstrap page table so that VM can
begin executing. Its first job is to make page tables for all other
boot processes. So VM runs before RS, and RS gets a fully dynamic,
VM-managed address space. VM gets its privilege info from RS as usual
but that happens after RS starts running.
. Both the kernel loading VM and VM organizing boot processes happen
using the libexec logic. This removes the last reason for VM to
still know much about exec() and vm/exec.c is gone.
Further Implementation:
. All segments are based at 0 and have a 4 GB limit.
. The kernel is mapped in at the top of the virtual address
space so as not to constrain the user processes.
. Processes do not use segments from the LDT at all; there are
no segments in the LDT any more, so no LLDT is needed.
. The Minix segments T/D/S are gone and so none of the
user-space or in-kernel copy functions use them. The copy
functions use a process endpoint of NONE to realize it's
a physical address, virtual otherwise.
. The umap call only makes sense to translate a virtual address
to a physical address now.
. Segments-related calls like newmap and alloc_segments are gone.
. All segments-related translation in VM is gone (vir2map etc).
. Initialization in VM is simpler as no moving around is necessary.
. VM and all other boot processes can be linked wherever they wish
and will be mapped in at the right location by the kernel and VM
respectively.
Other changes:
. The multiboot code is less special: it does not use mb_print
for its diagnostics any more but uses printf() as normal, saving
the output into the diagnostics buffer, only printing to the
screen using the direct print functions if a panic() occurs.
. The multiboot code uses the flexible 'free memory map list'
style to receive the list of free memory if available.
. The kernel determines the memory layout of the processes to
a degree: it tells VM where the kernel starts and ends and
where the kernel wants the top of the process to be. VM then
uses this entire range, i.e. the stack is right at the top,
and mmap()ped bits of memory are placed below that downwards,
and the break grows upwards.
Other Consequences:
. Every process gets its own page table as address spaces
can't be separated any more by segments.
. As all segments are 0-based, there is no distinction between
virtual and linear addresses, nor between userspace and
kernel addresses.
. Less work is done when context switching, leading to a net
performance increase. (8% faster on my machine for 'make servers'.)
. The layout and configuration of the GDT makes sysenter and syscall
possible.
2012-05-07 16:03:35 +02:00
|
|
|
chunk = vm_lookup_range(procp, vir_addr, &phys_addr, size);
|
2012-03-21 23:51:18 +01:00
|
|
|
|
|
|
|
|
if (!chunk) {
|
|
|
|
|
/* Try to get the memory allocated, unless the memory
|
|
|
|
|
* is supposed to be there to be read from.
|
|
|
|
|
*/
|
|
|
|
|
if (access & CPF_READ)
|
|
|
|
|
return EFAULT;
|
|
|
|
|
|
|
|
|
|
/* This call may suspend the current call, or return an
|
|
|
|
|
* error for a previous invocation.
|
|
|
|
|
*/
|
make vfs & filesystems use failable copying
Change the kernel to add features to vircopy and safecopies so that
transparent copy fixing won't happen to avoid deadlocks, and such copies
fail with EFAULT.
Transparently making copying work from filesystems (as normally done by
the kernel & VM when copying fails because of missing/readonly memory)
is problematic as it can happen that, for file-mapped ranges, that that
same filesystem that is blocked on the copy request is needed to satisfy
the memory range, leading to deadlock. Dito for VFS itself, if done with
a blocking call.
This change makes the copying done from a filesystem fail in such cases
with EFAULT by VFS adding the CPF_TRY flag to the grants. If a FS call
fails with EFAULT, VFS will then request the range to be made available
to VM after the FS is unblocked, allowing it to be used to satisfy the
range if need be in another VFS thread.
Similarly, for datacopies that VFS itself does, it uses the failable
vircopy variant and callers use a wrapper that talk to VM if necessary
to get the copy to work.
. kernel: add CPF_TRY flag to safecopies
. kernel: only request writable ranges to VM for the
target buffer when copying fails
. do copying in VFS TRY-first
. some fixes in VM to build SANITYCHECK mode
. add regression test for the cases where
- a FS system call needs memory mapped in a process that the
FS itself must map.
- such a range covers more than one file-mapped region.
. add 'try' mode to vircopy, physcopy
. add flags field to copy kernel call messages
. if CP_FLAG_TRY is set, do not transparently try
to fix memory ranges
. for use by VFS when accessing user buffers to avoid
deadlock
. remove some obsolete backwards compatability assignments
. VFS: let thread scheduling work for VM requests too
Allows VFS to make calls to VM while suspending and resuming
the currently running thread. Does currently not work for the
main thread.
. VM: add fix memory range call for use by VFS
Change-Id: I295794269cea51a3163519a9cfe5901301d90b32
2014-01-16 14:22:13 +01:00
|
|
|
return vm_check_range(caller, procp, vir_addr, size, 1);
|
2012-03-21 23:51:18 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
pvec[pcount].vp_addr = phys_addr;
|
|
|
|
|
pvec[pcount].vp_size = chunk;
|
|
|
|
|
pcount++;
|
|
|
|
|
|
No more intel/minix segments.
This commit removes all traces of Minix segments (the text/data/stack
memory map abstraction in the kernel) and significance of Intel segments
(hardware segments like CS, DS that add offsets to all addressing before
page table translation). This ultimately simplifies the memory layout
and addressing and makes the same layout possible on non-Intel
architectures.
There are only two types of addresses in the world now: virtual
and physical; even the kernel and processes have the same virtual
address space. Kernel and user processes can be distinguished at a
glance as processes won't use 0xF0000000 and above.
No static pre-allocated memory sizes exist any more.
Changes to booting:
. The pre_init.c leaves the kernel and modules exactly as
they were left by the bootloader in physical memory
. The kernel starts running using physical addressing,
loaded at a fixed location given in its linker script by the
bootloader. All code and data in this phase are linked to
this fixed low location.
. It makes a bootstrap pagetable to map itself to a
fixed high location (also in linker script) and jumps to
the high address. All code and data then use this high addressing.
. All code/data symbols linked at the low addresses is prefixed by
an objcopy step with __k_unpaged_*, so that that code cannot
reference highly-linked symbols (which aren't valid yet) or vice
versa (symbols that aren't valid any more).
. The two addressing modes are separated in the linker script by
collecting the unpaged_*.o objects and linking them with low
addresses, and linking the rest high. Some objects are linked
twice, once low and once high.
. The bootstrap phase passes a lot of information (e.g. free memory
list, physical location of the modules, etc.) using the kinfo
struct.
. After this bootstrap the low-linked part is freed.
. The kernel maps in VM into the bootstrap page table so that VM can
begin executing. Its first job is to make page tables for all other
boot processes. So VM runs before RS, and RS gets a fully dynamic,
VM-managed address space. VM gets its privilege info from RS as usual
but that happens after RS starts running.
. Both the kernel loading VM and VM organizing boot processes happen
using the libexec logic. This removes the last reason for VM to
still know much about exec() and vm/exec.c is gone.
Further Implementation:
. All segments are based at 0 and have a 4 GB limit.
. The kernel is mapped in at the top of the virtual address
space so as not to constrain the user processes.
. Processes do not use segments from the LDT at all; there are
no segments in the LDT any more, so no LLDT is needed.
. The Minix segments T/D/S are gone and so none of the
user-space or in-kernel copy functions use them. The copy
functions use a process endpoint of NONE to realize it's
a physical address, virtual otherwise.
. The umap call only makes sense to translate a virtual address
to a physical address now.
. Segments-related calls like newmap and alloc_segments are gone.
. All segments-related translation in VM is gone (vir2map etc).
. Initialization in VM is simpler as no moving around is necessary.
. VM and all other boot processes can be linked wherever they wish
and will be mapped in at the right location by the kernel and VM
respectively.
Other changes:
. The multiboot code is less special: it does not use mb_print
for its diagnostics any more but uses printf() as normal, saving
the output into the diagnostics buffer, only printing to the
screen using the direct print functions if a panic() occurs.
. The multiboot code uses the flexible 'free memory map list'
style to receive the list of free memory if available.
. The kernel determines the memory layout of the processes to
a degree: it tells VM where the kernel starts and ends and
where the kernel wants the top of the process to be. VM then
uses this entire range, i.e. the stack is right at the top,
and mmap()ped bits of memory are placed below that downwards,
and the break grows upwards.
Other Consequences:
. Every process gets its own page table as address spaces
can't be separated any more by segments.
. As all segments are 0-based, there is no distinction between
virtual and linear addresses, nor between userspace and
kernel addresses.
. Less work is done when context switching, leading to a net
performance increase. (8% faster on my machine for 'make servers'.)
. The layout and configuration of the GDT makes sysenter and syscall
possible.
2012-05-07 16:03:35 +02:00
|
|
|
vir_addr += chunk;
|
2012-03-21 23:51:18 +01:00
|
|
|
size -= chunk;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
offset = 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Copy out the resulting vector of physical addresses. */
|
|
|
|
|
assert(pcount > 0);
|
|
|
|
|
|
|
|
|
|
size = pcount * sizeof(pvec[0]);
|
|
|
|
|
|
|
|
|
|
r = data_copy_vmcheck(caller, KERNEL, (vir_bytes) pvec, endpt, paddr, size);
|
|
|
|
|
|
|
|
|
|
if (r == OK)
|
2014-05-22 10:05:44 +02:00
|
|
|
m_ptr->m_krn_lsys_sys_vumap.pcount = pcount;
|
2012-03-21 23:51:18 +01:00
|
|
|
|
|
|
|
|
return r;
|
|
|
|
|
}
|
