linux-kernel - A set of "standard" virtual devices?

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 02 Apr 2007 13:18:55 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
CC:	mathiasen@...il.com
Subject: A set of "standard" virtual devices?

On the subject of virtualization; there are a number of devices which 
keep being invented and reinvented by just about every virtualization 
vendor for no really good reason.

I personally recently pointed out that a proper virtualization solution 
should handle entropy collection at the lowest level (where the physical 
hardware drivers are) and present a hw_rng interface to the guests. 
Unfortunately, none of the hardware-based hw_rng interfaces is sane 
enough to do that with, which calls for a virtual driver.

It would be nice if there was one, and not a dozen, such drivers.

I would therefore like to propose that the Linux Foundation register a 
PCI ID for use by LANANA ($3000/year), and we set up a LANANA registry 
for these device IDs, together with a description of the device 
interface each of them expect.  Similarly, a Subsystem ID registry can 
be used (for virtualization vendors which don't have their own VID 
already) to distinguish different implementations.

Obviously, anyone who adheres to the published interface can use one of 
these VID:DIDs -- as far as I'm concerned, even hardware vendors; we'll 
use the SID to distinguish between implementations.

	-hpa
-
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/