linux-kernel - Re: status of the calgary iommu driver

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]

Message-ID: <20190508175219.GA32030@lst.de>
Date:   Wed, 8 May 2019 19:52:19 +0200
From:   Christoph Hellwig <hch@....de>
To:     Jon Mason <jdmason@...zu.us>
Cc:     Christoph Hellwig <hch@....de>, Muli Ben-Yehuda <mulix@...ix.org>,
        x86@...nel.org, iommu@...ts.linux-foundation.org,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: status of the calgary iommu driver

On Wed, May 08, 2019 at 06:42:39PM +0100, Jon Mason wrote:
> These systems were plentiful for 2-4 years after the original series
> made it in.  After that, the Intel and AMD IOMMUs should were shipped
> and were superior to this chip.  So, even in systems where these might
> be present, the AMD/Intel ones should be used (unknown if they were
> shipped on the same ones, as both Muli and I have left IBM).
> 
> You thinking about removing the code?

I'm wondering if we could remove it.  I've been done lots of
maintainance on various dma mapping and iommu drivers, and the calgary
one seems like it didn't get a whole lot of love, and I've not seen
any recent users, so I mostly wonder if I should bother at all.