Messages in this thread | | | Date | Fri, 03 Feb 2012 16:52:07 -0600 | From | Anthony Liguori <> | Subject | Re: [Qemu-devel] [RFC] Next gen kvm api |
| |
On 02/03/2012 12:07 PM, Eric Northup wrote: > On Thu, Feb 2, 2012 at 8:09 AM, Avi Kivity<avi@redhat.com> 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?
Why should it be regulated?
It's not a finite or privileged resource.
Regards,
Anthony Liguori
>
| |