Not exactly. UML needs to be able to fiddle an address space that has no
process in it (swapout, COWing, maybe a few other things).
UML has two relevant processes, one which runs userspace, and one which runs
the kernel and ptraces the userspace process. The kernel process creates
an address space per UML process, and makes the userspace process switch
between them during a UML context switch. So, when there's swapping going
on, pages need to be unmapped from UML processes, and thus from the
corresponding host address spaces.
> Which really means that I _think_ the right approach would be to
> literally have a "indirect-system-call-using-this-mm" system call,
> which does something like
> asmlinkage sys_mm_indirect(int fd, struct syscall_descriptor_block
> struct mm_struct *old_mm;
> struct syscall_descriptor_block args;
> if (memcpy_from_user(&args, user_args, sizeof(args)))
> return -EFAULT;
> mm = get_fd_mm(fd);
> old_mm = current->mm;
> current->mm = mm;
> current->mm = old_mm;
Hmmm, I wasn't planning on going that far, but this certainly works for UML,
as long as there is also PTRACE_SWITCH_MM to make a child jump from one mm
The calls to switch_mm() are needed when the system call is going to modify
data within the address space, but not if it's going to change mappings,
If those will cause a noticable performance hit, would it be OK to special-case
syscalls which don't need it?
current->mm = old_mm;
Sorry about the double negative, but it seems easiest to sparsely populate
an array with system calls that really don't want the switch_mm().
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/