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: <CAPoiz9wwMCRkzM5FWm18kecC1=kt+5qPNHmQ7eUFhH=3ZNAqYw@mail.gmail.com>
Date:   Wed, 8 May 2019 18:42:39 +0100
From:   Jon Mason <jdmason@...zu.us>
To:     Christoph Hellwig <hch@....de>
Cc:     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 Tue, Apr 9, 2019 at 3:03 PM Christoph Hellwig <hch@....de> wrote:
>
> Hi Muli and Jon,
>
> do you know if there are user of systems with the Calgary iommu
> around still? It seems like the last non-drive by changes to it
> are from 2010 and I'm not sure how common these systems were.


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?

Thanks,
Jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ