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

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 12 Jan 2007 11:19:27 +0000
From:	Pavel Machek <pavel@....cz>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Arnd Bergmann <arnd@...db.de>, kvm-devel@...ts.sourceforge.net,
	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


Hi!

> >>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 does not require ASCII...

Yep, but at that point you have 32 vs. 64bit nightmare back... and
stronger, because sysfs does not have compat handling.

-- 
Thanks for all the (sleeping) penguins.
-
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/