public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jon Mason <jdmason@kudzu.us>
Cc: Christoph Hellwig <hch@lst.de>, Muli Ben-Yehuda <mulix@mulix.org>,
	x86@kernel.org, iommu@lists.linux-foundation.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: status of the calgary iommu driver
Date: Wed, 8 May 2019 19:52:19 +0200	[thread overview]
Message-ID: <20190508175219.GA32030@lst.de> (raw)
In-Reply-To: <CAPoiz9wwMCRkzM5FWm18kecC1=kt+5qPNHmQ7eUFhH=3ZNAqYw@mail.gmail.com>

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.

  reply	other threads:[~2019-05-08 17:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 14:03 status of the calgary iommu driver Christoph Hellwig
2019-05-08 17:42 ` Jon Mason
2019-05-08 17:52   ` Christoph Hellwig [this message]
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=20190508175219.GA32030@lst.de \
    --to=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jdmason@kudzu.us \
    --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