From: Anthony Liguori <aliguori@us.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Avi Kivity <avi@qumranet.com>, Dor Laor <dor.laor@qumranet.com>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: Use of virtio device IDs
Date: Tue, 06 Nov 2007 12:49:55 -0600 [thread overview]
Message-ID: <4730B753.2000901@us.ibm.com> (raw)
In-Reply-To: <4730A15A.6070001@us.ibm.com>
Anthony Liguori wrote:
> Hi Rusty,
>
> I've written a PCI virtio transport and noticed something strange.
> All current in-tree virtio devices register ID tables that match a
> specific device ID, but any vendor ID.
>
> This is incompatible with using PCI vendor/device IDs for virtio
> vendor/device IDs since vendors control what device IDs mean. A
> simple solution would be to assign a fixed vendor ID to all current
> virtio devices. This doesn't solve the problem completely though
> since you would create a conflict between the PCI vendor ID space and
> the virtio vendor ID space.
>
> The only solutions seem to be virtualizing the virtio vendor/device
> IDs (which is what I'm currently doing) or to mandate that the virtio
> vendor ID be within the PCI vendor ID space. It's probably not
> necessary to make the same requirement for device IDs though.
There's another ugly bit in the current implementation.
Right now, we would have to have every PCI vendor/device ID pair in the
virtio PCI driver ID table for every virtio device.
This means every time a virtio device is added to Linux, the virtio PCI
driver has to be modified (assuming that each virtio device uses a
unique PCI vendor/device ID) :-/
Regards,
Anthony Liguori
> What are your thoughts?
>
> Regards,
>
> Anthony Liguori
>
next prev parent reply other threads:[~2007-11-06 18:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 17:16 Use of virtio device IDs Anthony Liguori
2007-11-06 18:49 ` Anthony Liguori [this message]
2007-11-07 3:38 ` Gregory Haskins
2007-11-07 5:40 ` Avi Kivity
2007-11-07 6:09 ` Rusty Russell
2007-11-07 6:29 ` Anthony Liguori
2007-11-07 17:33 ` Anthony Liguori
2007-11-07 20:38 ` Gregory Haskins
2007-11-08 6:37 ` Avi Kivity
2007-11-08 9:17 ` Gerd Hoffmann
2007-11-08 16:40 ` Anthony Liguori
2007-11-13 13:18 ` Gregory Haskins
2007-11-13 13:59 ` Zachary Amsden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4730B753.2000901@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@qumranet.com \
--cc=dor.laor@qumranet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox