[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC] Next gen kvm api
From: |
Eric Northup |
Subject: |
Re: [Qemu-devel] [RFC] Next gen kvm api |
Date: |
Fri, 3 Feb 2012 10:07:18 -0800 |
On Thu, Feb 2, 2012 at 8:09 AM, Avi Kivity <address@hidden> 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?
- Re: [Qemu-devel] [RFC] Next gen kvm api, (continued)
- Re: [Qemu-devel] [RFC] Next gen kvm api, Anthony Liguori, 2012/02/07
- Re: [Qemu-devel] [RFC] Next gen kvm api, Alexander Graf, 2012/02/07
- Re: [Qemu-devel] [RFC] Next gen kvm api, Alan Cox, 2012/02/08
- Re: [Qemu-devel] [RFC] Next gen kvm api, Avi Kivity, 2012/02/15
- Re: [Qemu-devel] [RFC] Next gen kvm api, Arnd Bergmann, 2012/02/16
Re: [Qemu-devel] [RFC] Next gen kvm api, Jamie Lokier, 2012/02/09
Re: [Qemu-devel] [RFC] Next gen kvm api,
Eric Northup <=
- Re: [Qemu-devel] [RFC] Next gen kvm api, Anthony Liguori, 2012/02/03
- Re: [Qemu-devel] [RFC] Next gen kvm api, Scott Wood, 2012/02/06
- Re: [Qemu-devel] [RFC] Next gen kvm api, Michael Ellerman, 2012/02/07
- Re: [Qemu-devel] [RFC] Next gen kvm api, Alexander Graf, 2012/02/07
- Re: [Qemu-devel] [RFC] Next gen kvm api, Arnd Bergmann, 2012/02/16
- Re: [Qemu-devel] [RFC] Next gen kvm api, Michael Ellerman, 2012/02/15
- Re: [Qemu-devel] [RFC] Next gen kvm api, Avi Kivity, 2012/02/16
- Re: [Qemu-devel] [RFC] Next gen kvm api, Michael Ellerman, 2012/02/16
- Re: [Qemu-devel] [RFC] Next gen kvm api, Avi Kivity, 2012/02/18
Re: [Qemu-devel] [RFC] Next gen kvm api, Avi Kivity, 2012/02/16