[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4612C077.60502@goop.org>
Date: Tue, 03 Apr 2007 14:00:39 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: "H. Peter Anvin" <hpa@...or.com>
CC: Arnd Bergmann <arnd@...db.de>,
Cornelia Huck <cornelia.huck@...ibm.com>,
Andi Kleen <ak@...e.de>,
Christian Borntraeger <borntrae@...ibm.com>,
virtualization@...ts.linux-foundation.org,
Virtualization Mailing List <virtualization@...ts.osdl.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
mathiasen@...il.com
Subject: Re: A set of "standard" virtual devices?
H. Peter Anvin wrote:
> However, there are other things; console is some, or my original
> example, which was random number generation. For those, the benefit
> of unification is proportionally greater, simply because the win of
> anything hypervisor-specific is much smaller.
So, what you're saying is:
1. assuming there's going to be a vast number of miscellaneous devices
2. it would be best if there were one per device rather than one per
hypervisor per device
3. so we'd have one linux device driver
But this implies that the work is just pushed off into all the
hypervisors to support this new device over the generic interface;
there's no overall reduction of code or complexity, other than making
"wc" on the kernel source smaller.
That said, something like USB is probably the best bet for this kind of
low-performance device. I think. Not that I really know anything about
USB.
J
-
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