From: will.deacon@arm•com (Will Deacon)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC v3 00/10] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions
Date: Wed, 30 Nov 2016 10:37:14 +0000 [thread overview]
Message-ID: <20161130103713.GB2724@arm.com> (raw)
In-Reply-To: <6c9012fd-070b-6218-48e7-69b37f2559dd@redhat.com>
On Wed, Nov 30, 2016 at 10:49:33AM +0100, Auger Eric wrote:
> On 15/11/2016 14:09, Eric Auger wrote:
> > Following LPC discussions, we now report reserved regions through
> > iommu-group sysfs reserved_regions attribute file.
> >
> > Reserved regions are populated through the IOMMU get_resv_region callback
> > (former get_dm_regions), now implemented by amd-iommu, intel-iommu and
> > arm-smmu.
> >
> > The intel-iommu reports the [FEE0_0000h - FEF0_000h] MSI window as an
> > IOMMU_RESV_NOMAP reserved region.
> >
> > arm-smmu reports the MSI window (arbitrarily located at 0x8000000 and
> > 1MB large) and the PCI host bridge windows.
> >
> > The series integrates a not officially posted patch from Robin:
> > "iommu/dma: Allow MSI-only cookies".
> >
> > This series currently does not address IRQ safety assessment.
>
> I will respin this series taking into account Joerg's comment. Does
> anyone have additional comments or want to put forward some conceptual
> issues with the current direction and with this implementation?
>
> As for the IRQ safety assessment, in a first step I would propose to
> remove the IOMMU_CAP_INTR_REMAP from arm-smmus and consider the
> assignment as unsafe. Any objection?
Well, yeah, because it's perfectly safe with GICv3.
Will
next prev parent reply other threads:[~2016-11-30 10:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 13:09 [RFC v3 00/10] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions Eric Auger
2016-11-18 5:34 ` Bharat Bhushan
2016-11-18 8:33 ` Auger Eric
2016-11-30 9:49 ` Auger Eric
2016-11-30 10:04 ` Ganapatrao Kulkarni
2016-11-30 10:14 ` Auger Eric
2016-11-30 10:52 ` Ganapatrao Kulkarni
2016-11-30 13:57 ` Robin Murphy
2016-11-30 10:37 ` Will Deacon [this message]
2016-11-30 14:08 ` Auger Eric
2016-11-30 14:41 ` Robin Murphy
2016-12-07 18:52 ` Shanker Donthineni
2016-12-08 7:34 ` Auger Eric
[not found] ` <1479215363-2898-4-git-send-email-eric.auger@redhat.com>
2016-12-06 17:28 ` [RFC v3 03/10] iommu: Add new reserved IOMMU attributes Robin Murphy
[not found] ` <1479215363-2898-3-git-send-email-eric.auger@redhat.com>
2016-12-06 17:30 ` [RFC v3 02/10] iommu: Rename iommu_dm_regions into iommu_resv_regions Robin Murphy
[not found] ` <1479215363-2898-5-git-send-email-eric.auger@redhat.com>
2016-11-29 16:11 ` [RFC v3 04/10] iommu: iommu_alloc_resv_region Joerg Roedel
2016-11-30 9:41 ` Auger Eric
2016-12-06 17:30 ` Robin Murphy
[not found] ` <1479215363-2898-6-git-send-email-eric.auger@redhat.com>
2016-12-06 17:36 ` [RFC v3 05/10] iommu: Do not map reserved regions Robin Murphy
2016-12-07 15:15 ` Auger Eric
[not found] ` <1479215363-2898-7-git-send-email-eric.auger@redhat.com>
2016-12-06 18:13 ` [RFC v3 06/10] iommu: iommu_get_group_resv_regions Robin Murphy
2016-12-07 15:13 ` Auger Eric
[not found] ` <1479215363-2898-10-git-send-email-eric.auger@redhat.com>
2016-12-06 18:55 ` [RFC v3 09/10] iommu/arm-smmu: Implement reserved region get/put callbacks Robin Murphy
2016-12-07 15:02 ` Auger Eric
2016-12-07 18:24 ` Robin Murphy
2016-12-08 7:57 ` Auger Eric
2016-12-08 3:56 ` [RFC v3 00/10] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions Bharat Bhushan
2016-12-08 9:36 ` Auger Eric
2016-12-08 13:14 ` Robin Murphy
2016-12-08 13:36 ` Auger Eric
2016-12-08 15:46 ` Robin Murphy
2016-12-08 17:01 ` Alex Williamson
2016-12-08 18:42 ` Robin Murphy
2016-12-11 2:05 ` Don Dutile
2016-12-12 8:12 ` Auger Eric
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=20161130103713.GB2724@arm.com \
--to=will.deacon@arm$(echo .)com \
--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