| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 11 Jan 2007 08:34:43 +0100 From: Arnd Bergmann <arnd@...db.de> To: kvm-devel@...ts.sourceforge.net Cc: Jeff Garzik <jeff@...zik.org>, Avi Kivity <avi@...ranet.com>, Andrew Morton <akpm@...l.org>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [kvm-devel] [RFC] Stable kvm userspace interface On Tuesday 09 January 2007 14:47, 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. For performance reasons, an ascii string based interface is not desireable here, some of these calls should be optimized to the point of counting cycles. Sysfs also does not fit the use case at all, and procfs only makes sense if you really want to keep all information about the guest as part of the process directory it belongs to. I still think that in the long term, we should migrate to new system calls and a special file system for kvm, which might be non-mountable. Those will of course have the same 32 bit compat problems as the ioctl approach, but so far, Avi has kept a good watch on avoiding these problems. As long as we think the interface is likely to change (which it certainly is right now), I believe that ioctl is the right interface. We can think about retiring it when the interface has stabilized enough to be converted to syscalls. Arnd <>< - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists