- Subject: AMD iommu: Difference between setting iommu=pt and not setting this option
- From: Andreas Hartmann <andihartmann@xxxxxxxxxxxxxxx>
- Date: Mon, 02 Apr 2012 09:56:24 +0200
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120312 Firefox/11.0 SeaMonkey/2.8
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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[KVM ARM]
[KVM ia64]
[KVM ppc]
[Spice Development]
[Libvirt]
[Libvirt Users]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Linux Kernel]
[Linux SCSI]
[XFree86]