On Thu, 30 Nov 2006 16:44:25 +0100 Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > [...] Pretty similar to things like the msr or mtrr driver that expose > > cpu features as character drivers aswell. > > you can expose everything as character drivers and ioctls, but that > doesnt make it the right solution. It might /start out/ as a driver, > because that's an easy to hack model, but the moment something becomes > important enough (and virtualization certainly is such a model) it > demands a system call. Actually fourteen syscalls and counting, and some of those have `mode' arguments. It's a fat, complex, presumably arch-specific, presumably frequently-changing API. So whatever we do will be unpleasant - that's unavoidable in this case, I suspect. (hmm, the interface isn't versioned at present - should it be?) Maybe, perhaps, one day it _should_ be a syscall API. But right now if we did that it would become a versioned syscall API with obsolete slots and various other warts. I get the feeling we'd be best off if we were to revisit this in a year or so. ------------------------------------------------------------------------- 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 _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
