linux-kernel - AMD iommu: Difference between setting iommu=pt and not setting this option

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 02 Apr 2012 09:56:24 +0200
From:	Andreas Hartmann <andihartmann@...19freenet.de>
To:	KVM <kvm@...r.kernel.org>,
	Kernel-Mailingliste <linux-kernel@...r.kernel.org>
Subject: AMD iommu: Difference between setting iommu=pt and not setting this
 option

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 linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/