From: Andreas Hartmann <andihartmann@01019freenet.de>
To: KVM <kvm@vger.kernel.org>,
Kernel-Mailingliste <linux-kernel@vger.kernel.org>
Subject: AMD iommu: Difference between setting iommu=pt and not setting this option
Date: Mon, 02 Apr 2012 09:56:24 +0200 [thread overview]
Message-ID: <4F795BA8.7020404@01019freenet.de> (raw)
Hello,
please, could somebody explain the difference in behaviour between
setting the boot option iommu=pt and not setting it?
I can see the following differences:
w/ iommu=pt:
[ 0.832946] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40
[ 0.883983] AMD-Vi: Initialized for Passthrough Mode
w/o iommu=pt:
[ 0.834905] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40
[ 0.894172] AMD-Vi: Lazy IO/TLB flushing enabled
In both cases, I can pass through a PCIe device but not a PCI device (->
no problem with IRQ-sharing - the PCI device has its own exclusive IRQ).
If I use iommu=pt, the passed PCIe device is broken after the VM has
been shutdown and started again.
Thank you,
kind regards,
Andreas
reply other threads:[~2012-04-02 7:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F795BA8.7020404@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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