| 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
| ||
|
Message-ID: <51642442.7090908@amd.com> Date: Tue, 9 Apr 2013 09:22:58 -0500 From: Suravee Suthikulanit <suravee.suthikulpanit@....com> To: Joerg Roedel <joro@...tes.org> CC: <iommu@...ts.linux-foundation.org>, <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] iommu/amd: Add workaround to propery clearing IOMMU status register On 4/9/2013 4:49 AM, Joerg Roedel wrote: > On Wed, Apr 03, 2013 at 06:19:04PM -0500, Suthikulpanit, Suravee wrote: >> In the system with multiple IOMMU,this handling scheme complicates the >> synchronization of the IOMMU data structures and status registers as >> there could be multiple threads competing for the same IOMMU while >> the other IOMMU could be left unhandled. > I really like that change in the interrupt handling code to pull the > different IOMMUs independently. But its problematic to change that in > the same patch that adds an erratum workaround. > > Please move that erratum fix into a seperate small patch that we can > backport to -stable and resend. > > > Joerg Joerg, The reason I implemented the "per-thread IOMMU handling" and the "workaround" together in one patch is because it simplifies the synchronization of clearing and checking the interrupt enabling bits. In the previous implementation, we could end up having multiple threads trying to access the status register at the same time. Suravee > > -- 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/
Powered by blists - more mailing lists