From: Jan Kiszka <jan.kiszka@siemens.com>
To: Michael Sturm <cyclonic2k@yahoo.com.au>
Cc: kvm@vger.kernel.org
Subject: Re: Shared IRQ with PCI Passthrough?
Date: Tue, 23 Aug 2011 15:07:19 +0200 [thread overview]
Message-ID: <4E53A607.4060903@siemens.com> (raw)
In-Reply-To: <4E53A2AB.7010500@yahoo.com.au>
On 2011-08-23 14:52, Michael Sturm wrote:
> On 19-08-11 0:02, Gardziejczyk, Kamil wrote:
>> Hi,
>>
>> Have you resolve your problem with shared IRQ lines? I have checked
>> out qemu-kvm 0.15.0 and found that Jan Kiszka patch was applied to
>> latest version of kvm.
>>
>> [PATCH 0/5] pci-assign: Host IRQ sharing suppport + some fixes and
>> cleanups
>> http://thread.gmane.org/gmane.comp.emulators.kvm.devel/64601
>>
>> Which version of linux kernel do you use? I have tried with 3.0.0. It
>> looks that Jan Kiszka`s patches were not added to that kernel version.
>> Maybe it is in 2.6.xxx?
>> Any ideas how to fix it? :)
>>
>>
>
> Hi Kamil,
>
> Thanks for your reply.
>
> For testing purposes, I've installed Ubuntu 11.04 Server (64-bit) on a
> separate physical disk. The default kernel of this setup is
> 2.6.38-8-server (slightly newer than the Proxmox kernel 2.6.35-1-pve I
> was using previously).
>
> As you suggested, I too have now tested qemu-kvm 0.15.0. (git clone
> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git and compiling the
> stable-0.15 branch).
>
> As before, using the nousb kernel option (with intel_iommu=on) my WinXP
> guest with pci-passthrough works fine, but without the nousb option, the
> guest cannot be started.
>
> My next attempt will be to try the KVM external module kit, compiling
> the latest code from the git clone
> git://git.kernel.org/pub/scm/virt/kvm/kvm-kmod.git. I think using the
> module kit rather than patching and compiling a custom kernel should
> work better in my case (if I'm moving back to Proxmox later), yet still
> update KVM to the latest code.
>
> Hopefully this will resolve the IRQ conflict.
Nope, there is no IRQ sharing support for assigned devices in any public
version so far. I'm on it, but some issues remain to be solved.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-08-23 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 5:04 Shared IRQ with PCI Passthrough? Michael Sturm
2011-08-18 14:02 ` Gardziejczyk, Kamil
2011-08-23 12:52 ` Michael Sturm
2011-08-23 13:07 ` Jan Kiszka [this message]
2012-10-15 9:07 ` Marco
2012-10-15 10:27 ` Jan Kiszka
2012-10-18 20:09 ` Marco
2012-10-19 7:12 ` Veruca Salt
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=4E53A607.4060903@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cyclonic2k@yahoo.com.au \
--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