From: joro@8bytes•org (Joerg Roedel)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC v2 8/8] iommu/arm-smmu: implement add_reserved_regions callback
Date: Mon, 14 Nov 2016 17:20:37 +0100 [thread overview]
Message-ID: <20161114162037.GC14829@8bytes.org> (raw)
In-Reply-To: <295feefe-014b-5669-7f5a-e04b09ba3454@redhat.com>
On Mon, Nov 14, 2016 at 05:08:16PM +0100, Auger Eric wrote:
> There are potentially several MSI doorbell physical pages in the SOC
> that are accessed through the IOMMU (translated). Each of those must
> have a corresponding IOVA and IOVA/PA mapping programmed in the IOMMU.
> Else MSI will fault.
>
> - step 1 was to define a usable IOVA range for MSI mapping. So now we
> decided the base address and size would be hardcoded for ARM. The
> get_dm_region can be used to retrieve that hardcoded region.
> - Step2 is to allocate IOVAs within that range and map then for each of
> those MSI doorbells. This is done in the MSI controller compose() callback.
>
> I hope I succeeded in clarifying this time.
>
> Robin sent today a new version of its cookie think using a dummy
> allocator. I am currently integrating it.
Okay, I understand. A simple bitmap-allocator would probably be
sufficient, and doesn't have the overhead the iova allocator has. About
how many pages are we talking here?
Joerg
next prev parent reply other threads:[~2016-11-14 16:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 11:23 [RFC v2 0/8] KVM PCIe/MSI passthrough on ARM/ARM64 - Alt II Eric Auger
[not found] ` <1478258646-3117-5-git-send-email-eric.auger@redhat.com>
2016-11-04 14:00 ` [RFC v2 4/8] iommu: Add a list of iommu_reserved_region in iommu_domain Robin Murphy
2016-11-10 11:22 ` Auger Eric
2016-11-10 11:54 ` Robin Murphy
2016-11-10 12:14 ` Auger Eric
2016-11-10 12:48 ` Robin Murphy
2016-11-10 15:37 ` Joerg Roedel
2016-11-10 15:42 ` Auger Eric
[not found] ` <1478258646-3117-9-git-send-email-eric.auger@redhat.com>
2016-11-04 14:16 ` [RFC v2 8/8] iommu/arm-smmu: implement add_reserved_regions callback Robin Murphy
2016-11-10 15:46 ` Joerg Roedel
2016-11-10 15:57 ` Auger Eric
2016-11-10 16:13 ` Joerg Roedel
2016-11-10 18:00 ` Auger Eric
2016-11-11 11:42 ` Joerg Roedel
2016-11-11 15:47 ` Auger Eric
2016-11-11 16:22 ` Joerg Roedel
2016-11-11 16:45 ` Auger Eric
2016-11-14 15:31 ` Joerg Roedel
2016-11-14 16:08 ` Auger Eric
2016-11-14 16:20 ` Joerg Roedel [this message]
2016-11-14 16:57 ` Auger Eric
2016-11-10 16:07 ` Robin Murphy
2016-11-10 16:16 ` Joerg Roedel
2016-11-11 14:34 ` Robin Murphy
2016-11-11 15:03 ` Joerg Roedel
[not found] ` <1478258646-3117-3-git-send-email-eric.auger@redhat.com>
2016-11-10 15:22 ` [RFC v2 2/8] iommu/iova: fix __alloc_and_insert_iova_range Joerg Roedel
2016-11-10 15:41 ` Auger Eric
[not found] ` <1478258646-3117-4-git-send-email-eric.auger@redhat.com>
2016-11-14 12:36 ` [RFC v2 3/8] iommu/dma: Allow MSI-only cookies Robin Murphy
2016-11-14 23:23 ` Auger Eric
2016-11-15 14:52 ` Robin Murphy
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=20161114162037.GC14829@8bytes.org \
--to=joro@8bytes$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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