From: Michael Tokarev <mjt@tls.msk.ru>
To: Amit Shah <amit.shah@redhat.com>
Cc: Wayne Feick <waf@brunz.org>, kvm@vger.kernel.org
Subject: Re: Does KVM PCI Device Assignment allow guests to access firewire?
Date: Thu, 29 Jan 2009 02:11:09 +0300 [thread overview]
Message-ID: <4980E60D.5080603@msgid.tls.msk.ru> (raw)
In-Reply-To: <20090128151555.GD1759@amit-x200.pnq.redhat.com>
Amit Shah wrote:
> Hello Wayne,
>
> On (Tue) Jan 27 2009 [21:15:22], Wayne Feick wrote:
>> I recently saw the following:
>>
>> https://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment
>>
>> This looks like it might allow guests to access a firewire device. Can
>> anyone confirm or deny whether that will be the case?
>
> Is the firewire port on a PCI card? If yes, it *might* work. We've only
> tested network device assignment so far; if you have a system with VT-d,
> you can give it a try yourself.
JFYI... I tried several simple devices here, all worked. But all were
without using DMA. Namely, an old wireless card (11Mbps), internal
PCI dialup modem (not softmodem, courier sportster 56k), a 6-serial-ports
PCI card, and an old USB-1.1 PCI card. Like this:
03:06.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01) (prog-if 02)
Subsystem: 3Com Corp, Modem Division Device 00a2
Flags: medium devsel, IRQ 20
I/O ports at ec00 [size=8]
Kernel driver in use: serial
Kernel modules: 8250_pci
With stock kernel-2.6.28 and kvm-83.
Sure thing it is less and less interesting since only very few devices
does not use DMA nowadays. But I don't have any hardware with IOMMU
or VT-D.
/mjt
prev parent reply other threads:[~2009-01-28 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 5:15 Does KVM PCI Device Assignment allow guests to access firewire? Wayne Feick
2009-01-28 15:15 ` Amit Shah
2009-01-28 17:05 ` Wayne Feick
2009-01-28 18:52 ` Nikola Ciprich
2009-01-28 18:58 ` Glauber Costa
2009-01-29 3:49 ` David S. Ahern
2009-01-28 23:11 ` Michael Tokarev [this message]
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=4980E60D.5080603@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=amit.shah@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=waf@brunz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.