From: Joerg Roedel <joro@8bytes.org>
To: Frank Blaschka <blaschka@linux.vnet.ibm.com>
Cc: schwidefsky@de.ibm.com, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, iommu@lists.linux-foundation.org,
sebott@linux.vnet.ibm.com, gerald.schaefer@de.ibm.com
Subject: Re: [PATCH linux-next] iommu: add iommu for s390 platform
Date: Wed, 22 Oct 2014 16:17:29 +0200 [thread overview]
Message-ID: <20141022141728.GG10074@8bytes.org> (raw)
In-Reply-To: <1413892645-37657-1-git-send-email-blaschka@linux.vnet.ibm.com>
Hi Frank,
On Tue, Oct 21, 2014 at 01:57:25PM +0200, Frank Blaschka wrote:
> Add a basic iommu for the s390 platform. The code is pretty simple
> since on s390 each PCI device has its own virtual io address space
> starting at the same vio address.
Are there any limitations on IOVA address space for the devices or can
be really any system physical address mapped starting from 0 to 2^64?
> For this a domain could hold only one pci device.
This bothers me, as it is not compatible with the IOMMU-API. I looked a
little bit into how the mappings are created, and it seems there is a
per-device dma_table.
Is there any reason a dma_table can't be per IOMMU domain and assigned
to multiple devices at the same time?
Otherwise the code looks quite simple and straight forward.
Joerg
next prev parent reply other threads:[~2014-10-22 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 11:57 [PATCH linux-next] iommu: add iommu for s390 platform Frank Blaschka
2014-10-22 14:17 ` Joerg Roedel [this message]
2014-10-22 15:43 ` Frank Blaschka
2014-10-23 12:41 ` Joerg Roedel
2014-10-23 14:04 ` Frank Blaschka
2014-10-24 23:33 ` Joerg Roedel
2014-10-27 14:32 ` Gerald Schaefer
2014-10-27 16:25 ` Joerg Roedel
2014-10-27 17:02 ` Gerald Schaefer
2014-10-27 17:58 ` Joerg Roedel
2014-10-27 18:18 ` Gerald Schaefer
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=20141022141728.GG10074@8bytes.org \
--to=joro@8bytes.org \
--cc=blaschka@linux.vnet.ibm.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@linux.vnet.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;
as well as URLs for NNTP newsgroup(s).