Re: [kvm-devel] [RFC] Stable kvm userspace interface

2007-01-10 Thread Arnd Bergmann
On Tuesday 09 January 2007 14:37, Avi Kivity wrote: struct kvm_vcpu_area {     u32 vcpu_area_size;     u32 exit_reason;     sigset_t sigmask;  // for use during vcpu execution Since Jeff brought up the point of 32 bit compatibility: When this structure is shared between 64 bit kernel and 32

[kvm-devel] [RFC] Stable kvm userspace interface

2007-01-09 Thread Avi Kivity
I had originally hoped to get this in for 2.6.20. It now looks like .20 will have a shorter cycle than usual, and the mmu took a bit longer than expected, so it's more realistic to aim for 2.6.21. The current kvm userspace interface has several deficiencies: - open(/dev/kvm) returns a

Re: [kvm-devel] [RFC] Stable kvm userspace interface

2007-01-09 Thread Jeff Garzik
Can we please avoid adding a ton of new ioctls? ioctls inevitably require 64-bit compat code for certain architectures, whereas sysfs/procfs does not. Jeff - Take Surveys. Earn Cash. Influence the Future of IT

Re: [kvm-devel] [RFC] Stable kvm userspace interface

2007-01-09 Thread James Morris
On Tue, 9 Jan 2007, Jeff Garzik wrote: Can we please avoid adding a ton of new ioctls? ioctls inevitably require 64-bit compat code for certain architectures, whereas sysfs/procfs does not. I guess ioctl is not as important now if the API is now always talking to one VM. - James --