All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Sturm <cyclonic2k@yahoo.com.au>
To: kvm@vger.kernel.org
Subject: Shared IRQ with PCI Passthrough?
Date: Sat, 13 Aug 2011 15:04:34 +1000	[thread overview]
Message-ID: <j250l3$u5m$1@dough.gmane.org> (raw)

Hi,

back in Dec 2010 Jan Kiszka posted a number of patches that deal with 
IRQ sharing.

[PATCH 0/5] pci-assign: Host IRQ sharing suppport + some fixes and cleanups
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/64601

[PATCH v3 0/4] KVM & genirq: Enable adaptive IRQ sharing for 
passed-through devices
http://thread.gmane.org/gmane.linux.kernel/1076440

[PATCH 0/2] Small KVM device assignment cleanups
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/64515

What do I need to do to apply these patches to my system?

The server I'm working on is running Proxmox 1.8 with upgraded 
2.6.35-1-pve kernel (previously 2.6.32-4-pve) and qemu-kvm 0.14.1.

Do I need to upgrade to a newer kernel, or upgrade qemu-kvm (e.g. 
0.15.0), or both?

The problem that I'm hoping to solve is an IRQ conflict. The Intel 
DQ67SW motherboard only has 1 PCI slot and no BIOS support for assigning 
IRQs. KVM PCI passthrough only works with the nousb kernel parameter, 
otherwise the ehci_hcd:usb1 conflicts with the PCI's assigned IRQ 16. 
This is a problem because I also need to USB passthrough a dongle 
required by the software (in WinXP guest).

Thanks for any pointers,

Mick


             reply	other threads:[~2011-08-13  5:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-13  5:04 Michael Sturm [this message]
2011-08-18 14:02 ` Shared IRQ with PCI Passthrough? Gardziejczyk, Kamil
2011-08-23 12:52   ` Michael Sturm
2011-08-23 13:07     ` Jan Kiszka
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='j250l3$u5m$1@dough.gmane.org' \
    --to=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 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.