All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 42636] PCI passthrough does not work with AMD iommu for PCI device
Date: Fri, 30 Mar 2012 12:16:39 GMT	[thread overview]
Message-ID: <201203301216.q2UCGdbt025907@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42636-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=42636





--- Comment #7 from Klaus Mueller <kmueller@justmail.de>  2012-03-30 12:16:39 ---
Thanks,
with the "iommu=pt iommu=1" options applied it doesn't work at all - even the
"workaround" with first try to start with the bridge applied and afterwards
without the bridge added isn't working then.

BTW: I can pass through PCIe devices, as long as they have different PCI ids
and different modules, without any problem.

I'm using the option allow_unsafe_assigned_interrupts=1 already!

I think there is a problem with the handling of the device behind a PCI bridge,
which should be fixed (-> the Ralink device which should be passed through is a
PCI device and not a PCIe device)! Take a look at the qemu-kvm crash log
https://bugzilla.kernel.org/attachment.cgi?id=72753

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2012-03-30 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23  9:55 [Bug 42636] New: PCI passthrough does not work with AMD iommu for PCI device bugzilla-daemon
2012-01-23 14:56 ` [Bug 42636] " bugzilla-daemon
2012-01-23 16:26 ` bugzilla-daemon
2012-03-30  7:48 ` bugzilla-daemon
2012-03-30 11:07 ` bugzilla-daemon
2012-03-30 11:29 ` bugzilla-daemon
2012-03-30 11:35 ` bugzilla-daemon
2012-03-30 12:16 ` bugzilla-daemon [this message]
2012-04-04  8:22 ` bugzilla-daemon
2012-04-05  8:08 ` bugzilla-daemon

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=201203301216.q2UCGdbt025907@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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.