All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Mason <jdmason@kudzu.us>
To: Christoph Hellwig <hch@lst.de>
Cc: 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 18:56:46 +0100	[thread overview]
Message-ID: <CAPoiz9zQuJ0-9wJBNo=Wvi9qquyid9vjmHODy=VJad_PE=cgdA@mail.gmail.com> (raw)
In-Reply-To: <20190508175219.GA32030@lst.de>

On Wed, May 8, 2019 at 6:52 PM Christoph Hellwig <hch@lst.de> wrote:
>
> 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.


I do have a system.  So, it could be tested.  However given the age of
the HW, I would say it is not worth the effort to update and it would
be best to remove it from the kernel.

I can send a patch to do this, unless you would prefer to do it (or
already have something handy).

Thanks,
Jon

WARNING: multiple messages have this Message-ID (diff)
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:56:46 +0100	[thread overview]
Message-ID: <CAPoiz9zQuJ0-9wJBNo=Wvi9qquyid9vjmHODy=VJad_PE=cgdA@mail.gmail.com> (raw)
In-Reply-To: <20190508175219.GA32030@lst.de>

On Wed, May 8, 2019 at 6:52 PM Christoph Hellwig <hch@lst.de> wrote:
>
> 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.


I do have a system.  So, it could be tested.  However given the age of
the HW, I would say it is not worth the effort to update and it would
be best to remove it from the kernel.

I can send a patch to do this, unless you would prefer to do it (or
already have something handy).

Thanks,
Jon
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

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

Thread overview: 12+ 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
2019-05-08 17:42   ` Jon Mason
2019-05-08 17:52   ` Christoph Hellwig
2019-05-08 17:52     ` Christoph Hellwig
2019-05-08 17:56     ` Jon Mason [this message]
2019-05-08 17:56       ` Jon Mason
2019-05-08 17:59       ` Christoph Hellwig
2019-05-08 17:59         ` Christoph Hellwig
2019-06-14 13:03       ` 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='CAPoiz9zQuJ0-9wJBNo=Wvi9qquyid9vjmHODy=VJad_PE=cgdA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.