From: Jon Mason <jdmason@kudzu.us>
To: Christoph Hellwig <hch@lst.de>
Cc: iommu@lists.linux-foundation.org, x86@kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Muli Ben-Yehuda <mulix@mulix.org>
Subject: Re: status of the calgary iommu driver
Date: Wed, 8 May 2019 18:42:39 +0100 [thread overview]
Message-ID: <CAPoiz9wwMCRkzM5FWm18kecC1=kt+5qPNHmQ7eUFhH=3ZNAqYw@mail.gmail.com> (raw)
In-Reply-To: <20190409140347.GA11524@lst.de>
On Tue, Apr 9, 2019 at 3:03 PM Christoph Hellwig <hch@lst.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
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-05-08 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 14:03 status of the calgary iommu driver Christoph Hellwig
2019-04-09 14:03 ` Christoph Hellwig
2019-05-08 17:42 ` Jon Mason [this message]
2019-05-08 17:52 ` Christoph Hellwig
2019-05-08 17:56 ` Jon Mason
2019-05-08 17:59 ` Christoph Hellwig
2019-06-14 13:03 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPoiz9wwMCRkzM5FWm18kecC1=kt+5qPNHmQ7eUFhH=3ZNAqYw@mail.gmail.com' \
--to=jdmason@kudzu.us \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).