linux-kernel - Re: 3.6.11 AMD-Vi: Completion-Wait loop timed out

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 22 Jan 2013 16:16:32 +0100
From:	Jörg Rödel <joro@...tes.org>
To:	Boris Ostrovsky <boris.ostrovsky@....com>
Cc:	Udo van den Heuvel <udovdh@...all.nl>,
	suravee.suthikulpanit@....com, Jacob Shin <jacob.shin@....com>,
	Borislav Petkov <bp@...en8.de>, linux-kernel@...r.kernel.org
Subject: Re: 3.6.11  AMD-Vi: Completion-Wait loop timed out

On Tue, Jan 22, 2013 at 09:36:34AM -0500, Boris Ostrovsky wrote:
> 
> 
> On 01/22/2013 09:13 AM, Udo van den Heuvel wrote:
> >Gigabyte demonstrate that using ESX 5i IOMMU works fine. (with pictures
> >attached).
> 
> There are no attachments to your message.
> 
> I am not sure that 5i supports IOMMU (but I may well be wrong).

Virtualization use-cases don't change the page-tables for the IOMMU very
often. So there is less need to flush the IO-TLB and IOMMU command
processing is utilized only from time to time.

In Linux however the page-tables change all the time and there is a much
higher load on the IOMMU command buffer which makes it much more likely
to trigger the hardware problem.


	Joerg


--
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/