On Thu, Feb 2, 2012 at 8:09 AM, Avi Kivity <avi@xxxxxxxxxx> wrote: [...] > > Moving to syscalls avoids these problems, but introduces new ones: > > - adding new syscalls is generally frowned upon, and kvm will need several > - syscalls into modules are harder and rarer than into core kernel code > - will need to add a vcpu pointer to task_struct, and a kvm pointer to > mm_struct - Lost a good place to put access control (permissions on /dev/kvm) for which user-mode processes can use KVM. How would the ability to use sys_kvm_* be regulated? -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
