2005-04-21 16:53:53 +02:00
|
|
|
#include "syslib.h"
|
|
|
|
|
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
|
|
|
int sys_physcopy(src_proc, src_vir, dst_proc, dst_vir, bytes, flags)
|
2009-09-22 23:42:02 +02:00
|
|
|
endpoint_t src_proc; /* source process */
|
2005-04-29 17:36:43 +02:00
|
|
|
vir_bytes src_vir; /* source virtual address */
|
2009-09-22 23:42:02 +02:00
|
|
|
endpoint_t dst_proc; /* destination process */
|
2005-04-29 17:36:43 +02:00
|
|
|
vir_bytes dst_vir; /* destination virtual address */
|
2005-04-21 16:53:53 +02:00
|
|
|
phys_bytes bytes; /* how many bytes */
|
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
|
|
|
int flags; /* copy flags */
|
2005-04-21 16:53:53 +02:00
|
|
|
{
|
2005-04-29 17:36:43 +02:00
|
|
|
/* Transfer a block of data. The source and destination can each either be a
|
|
|
|
* process number or SELF (to indicate own process number). Virtual addresses
|
2011-04-26 23:28:23 +02:00
|
|
|
* are offsets within LOCAL_SEG (text, stack, data), or BIOS_SEG.
|
2005-04-29 17:36:43 +02:00
|
|
|
* Physicall addressing is also possible with PHYS_SEG.
|
2005-04-21 16:53:53 +02:00
|
|
|
*/
|
2005-04-29 17:36:43 +02:00
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
message copy_mess;
|
|
|
|
|
|
|
|
if (bytes == 0L) return(OK);
|
2014-05-21 17:21:26 +02:00
|
|
|
copy_mess.m_lsys_krn_sys_copy.src_endpt = src_proc;
|
|
|
|
copy_mess.m_lsys_krn_sys_copy.src_addr = src_vir;
|
|
|
|
copy_mess.m_lsys_krn_sys_copy.dst_endpt = dst_proc;
|
|
|
|
copy_mess.m_lsys_krn_sys_copy.dst_addr = dst_vir;
|
|
|
|
copy_mess.m_lsys_krn_sys_copy.nr_bytes = bytes;
|
|
|
|
copy_mess.m_lsys_krn_sys_copy.flags = flags;
|
2012-06-16 19:29:37 +02:00
|
|
|
|
2010-02-09 16:20:09 +01:00
|
|
|
return(_kernel_call(SYS_PHYSCOPY, ©_mess));
|
2005-04-21 16:53:53 +02:00
|
|
|
}
|