From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC] Stable kvm userspace interface Date: Tue, 09 Jan 2007 16:11:23 +0200 Message-ID: <45A3A28B.5000201@qumranet.com> References: <45A39A97.5060807@qumranet.com> <45A39D0D.7090007@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , Andrew Morton , linux-kernel Return-path: To: Jeff Garzik In-Reply-To: <45A39D0D.7090007-o2qLIJkoznsdnm+yROfE0A@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org 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 don't see how the procfs or sysfs models fit kvm. wrt compat code, the current kvm abi (also ioctl based) is 32/64 bit safe without compat code, and I certainly don't intend to break it. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV