linux-kernel - RE: [Lguest] [kvm-devel] [RFC] 9p: add KVM/QEMU pci transport

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 28 Aug 2007 16:59:53 -0700
From:	"Dor Laor" <dor.laor@...ranet.com>
To:	"Latchesar Ionkov" <lucho@...kov.net>,
	"Arnd Bergmann" <arnd@...db.de>
Cc:	<kvm-devel@...ts.sourceforge.net>,
	<v9fs-developer@...ts.sourceforge.net>, <lguest@...abs.org>,
	<linux-kernel@...r.kernel.org>
Subject: RE: [Lguest] [kvm-devel] [RFC] 9p: add KVM/QEMU pci transport

>>
>> Nice driver. I'm hoping we can do a virtio driver using a similar
>> concept.
>>
>> > +#define PCI_VENDOR_ID_9P     0x5002
>> > +#define PCI_DEVICE_ID_9P     0x000D
>>
>> Where do these numbers come from? Can we be sure they don't conflict
>with
>> actual hardware?
>
>I stole the VENDOR_ID from kvm's hypercall driver. There are no any
>guarantees that it doesn't conflict with actual hardware. As it was
>discussed before, there is still no ID assigned for the virtual
>devices.


Currently 5002 does not registered to Qumranet nor KVM.
We will do something about it pretty soon.
-
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/