From: Jan Kiszka <jan.kiszka@siemens.com>
To: Binarus <lists@binarus.de>
Cc: kvm@vger.kernel.org, Alex Williamson <alex.williamson@redhat.com>
Subject: Re: PCI passthrough (shared IRQ) not working / contradicting information
Date: Fri, 03 May 2013 10:35:33 +0200 [thread overview]
Message-ID: <518376D5.1050208@siemens.com> (raw)
In-Reply-To: <51836838.5080201@binarus.de>
On 2013-05-03 09:33, Binarus wrote:
> Hi all,
>
> a while ago, I have set up a KVM virtual machine with PCI passthrough.
> The device which is passed through is an AVM Fritz!card PCI v2.1.
>
> This works, but there is a drawback: At that time, KVM was not able to
> do PCI passthrough for PCI devices with shared interrupt. So I had to
> find out which other devices were using the same interrupt, and had to
> inactivate them by handling them over to the PCI stub driver.
>
> Then, one day, I have been very excited when I was reading that with
> kernel 3.4, KVM should be able to do PCI passthrough even if the
> respective device shares its IRQ with other devices. Thus, two day ago,
> I took the time, got vanilla kernel 3.9, configured, compiled and
> installed, and got qemu 1.4.1, configured, compiled and installed.
>
> Now, I am disappointed that the passthrough still doesn't work if I
> leave the other devices active, probably due to a silly error on my
> side. It still works if I inactivate the other devices which share their
> IRQ with the AVM card, but that actually was not the goal.
>
> Furthermore, the last two sentences on the following page suggest that
> PCI passthrough of devices with shared IRQs is still not possible:
> http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM. So
> there is a contradiction between what has been stated when kernel 3.4
> came out and what linux-kvm.org says.
>
> Could anybody please tell me if PCI passthrough with shared IRQs is
> possible or not? Does anybody know why the AVM Fritz!card won't work
> without inactivating other devices? What mistake could lead to the
> current situation (passthrough works if other devices are inactivated,
> and does not work if not)?
The Fritz!CARD is very old and likely not PCI 2.3 compliant. But that is
required to share legacy interrupts.
Alex, does VFIO provide any convenient diagnostics if INTx sharing is
possible or not? If not, maybe we should add it at least over there.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-05-03 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 7:33 PCI passthrough (shared IRQ) not working / contradicting information Binarus
2013-05-03 8:35 ` Jan Kiszka [this message]
2013-05-03 14:37 ` Alex Williamson
2013-05-03 15:04 ` Jan Kiszka
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=518376D5.1050208@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lists@binarus.de \
/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