From: Avi Kivity <avi@redhat.com>
To: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
Cc: kvm@vger.kernel.org, Chris Wright <chrisw@redhat.com>
Subject: Re: Prevent IRQ sharing for PCI passthrough
Date: Thu, 13 May 2010 20:21:56 +0300 [thread overview]
Message-ID: <4BEC3534.7060707@redhat.com> (raw)
In-Reply-To: <giljbnhh8c.fsf@mx10.gouders.net>
On 05/13/2010 07:57 PM, Dirk Gouders wrote:
> Hello List,
>
> please don't shout at me if the answer to my question is too obvious,
>
We won't shout at you.
> but in the German Linux Magazine I read an article about passing PCI
> devices to KVM guests and the authors said that "shared interrupt
> funcionality has to be disabled" which I read as "it is possible to
> disable shared interrupt functionality".
>
It would be more correct to say "no go with shared host interrupts".
> I currently have the problem with a PCI ISDN card that is not MSI
> capable and even if I change the PCI slot and disable all other slots,
> USB etc. in the BIOS, that card still shares its interrupt with three
> other devices.
>
> Even after extensive searching/reading, I am not sure if it possible to
> prevent a PCI card from sharing an interrupt with other devices or
> probably manually assign a free interrupt to that card via some kernel
> parameter and would be glad if someone could give me an answer to that
> question.
>
There is an ACPI _SRS method which can be used to move interrupts
around. However Linux doesn't appear to expose it. Even if it did, the
interrupt may be shared on the motherboard, in which case nothing would
help (though you might be able to share it with unused devices).
Chris?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-05-13 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 16:57 Prevent IRQ sharing for PCI passthrough Dirk Gouders
2010-05-13 17:21 ` Avi Kivity [this message]
2010-05-13 17:26 ` Chris Wright
2010-05-14 9:49 ` Dirk Gouders
2010-05-14 9:37 ` Dirk Gouders
2010-05-14 17:14 ` Avi Kivity
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=4BEC3534.7060707@redhat.com \
--to=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=gouders@et.bocholt.fh-gelsenkirchen.de \
--cc=kvm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).