From: Matthew Rosato <mjrosato@linux.ibm.com>
To: Christoph Hellwig <hch@lst.de>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Niklas Schnelle <schnelle@linux.ibm.com>
Cc: linux-s390@vger.kernel.org
Subject: Re: s390 PCI dma ops
Date: Fri, 11 Sep 2020 10:39:02 -0400 [thread overview]
Message-ID: <73550e74-1fda-cc34-0e14-54e2b7e76e99@linux.ibm.com> (raw)
In-Reply-To: <20200911072734.GA23043@lst.de>
On 9/11/20 3:27 AM, Christoph Hellwig wrote:
> Hi S/390 PCI and IOMMU maintainers,
>
> We've recently tried to convert all implementations of the IOMMU API to
> use drivers/iommu/dma-iommu.c instead of their local IOMMU ops. I've
> looked at S/390 and while some comments mention things about the iommu
> API the implementation looks quite separate. Do arch/s390/pci/pci_dma.c
> and drivers/iommu/s390-iommu.c driver the same hardware? If so would a
Yes, these drivers are dealing with the same hardware.
> switch to drivers/iommu/dma-iommu.c be feasibel?
>
Hmm... s390 does some particular things that are arch-specific, largely
as forms of optimization. One such example is a case where we avoid
reusing IO TLB Page Table Entries until we have to do a global flush.
I'd need to take a closer look at what AMD did / what intel is doing.
Fundamentally we are open to the idea as the maintenance benefit is
clear, but I don't think it's a trivial swap - I think we would need
extensions to dma-iommu to accommodate some of our special cases /
optimizations.
prev parent reply other threads:[~2020-09-11 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 7:27 s390 PCI dma ops Christoph Hellwig
2020-09-11 14:39 ` Matthew Rosato [this message]
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=73550e74-1fda-cc34-0e14-54e2b7e76e99@linux.ibm.com \
--to=mjrosato@linux.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=hch@lst.de \
--cc=linux-s390@vger.kernel.org \
--cc=schnelle@linux.ibm.com \
/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