From: Auger Eric <eric.auger@redhat.com>
To: Will Deacon <will.deacon@arm.com>
Cc: drjones@redhat.com, jason@lakedaemon.net, kvm@vger.kernel.org,
marc.zyngier@arm.com, joro@8bytes.org, punit.agrawal@arm.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
diana.craciun@nxp.com, alex.williamson@redhat.com,
pranav.sawargaonkar@gmail.com,
linux-arm-kernel@lists.infradead.org, tglx@linutronix.de,
robin.murphy@arm.com, christoffer.dall@linaro.org,
eric.auger.pro@gmail.com
Subject: Re: [RFC v3 00/10] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions
Date: Wed, 30 Nov 2016 15:08:17 +0100 [thread overview]
Message-ID: <1899e46c-7b06-01d6-6cff-eb0985a4f11d@redhat.com> (raw)
In-Reply-To: <20161130103713.GB2724@arm.com>
Hi Will,
On 30/11/2016 11:37, Will Deacon wrote:
> 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.
Well except if you have an MSI controller in-between the device and the
sMMU (typically embedded in the host bridge). Detecting this situation
is not straightforward; hence my proposal.
Thanks
Eric
>
> Will
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2016-11-30 14:08 UTC|newest]
Thread overview: 45+ 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-15 13:09 ` [RFC v3 01/10] iommu/dma: Allow MSI-only cookies Eric Auger
2016-11-15 13:09 ` [RFC v3 02/10] iommu: Rename iommu_dm_regions into iommu_resv_regions Eric Auger
2016-12-06 17:30 ` Robin Murphy
2016-11-15 13:09 ` [RFC v3 03/10] iommu: Add new reserved IOMMU attributes Eric Auger
2016-12-06 17:28 ` Robin Murphy
2016-11-15 13:09 ` [RFC v3 04/10] iommu: iommu_alloc_resv_region Eric Auger
2016-11-29 16:11 ` Joerg Roedel
2016-11-30 9:41 ` Auger Eric
2016-12-06 17:30 ` Robin Murphy
2016-11-15 13:09 ` [RFC v3 05/10] iommu: Do not map reserved regions Eric Auger
2016-12-06 17:36 ` Robin Murphy
2016-12-07 15:15 ` Auger Eric
2016-11-15 13:09 ` [RFC v3 06/10] iommu: iommu_get_group_resv_regions Eric Auger
2016-12-06 18:13 ` Robin Murphy
2016-12-07 15:13 ` Auger Eric
2016-11-15 13:09 ` [RFC v3 07/10] iommu: Implement reserved_regions iommu-group sysfs file Eric Auger
2016-11-15 13:09 ` [RFC v3 08/10] iommu/vt-d: Implement reserved region get/put callbacks Eric Auger
2016-11-15 13:09 ` [RFC v3 09/10] iommu/arm-smmu: " Eric Auger
2016-12-06 18:55 ` Robin Murphy
2016-12-07 15:02 ` Auger Eric
2016-12-07 18:24 ` Robin Murphy
2016-12-08 7:57 ` Auger Eric
2016-11-15 13:09 ` [RFC v3 10/10] vfio/type1: Get MSI cookie Eric Auger
2016-11-18 5:34 ` [RFC v3 00/10] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions 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
2016-11-30 14:08 ` Auger Eric [this message]
2016-11-30 14:41 ` Robin Murphy
2016-12-07 18:52 ` Shanker Donthineni
2016-12-08 7:34 ` Auger Eric
2016-12-08 3:56 ` 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=1899e46c-7b06-01d6-6cff-eb0985a4f11d@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=diana.craciun@nxp.com \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jason@lakedaemon.net \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=pranav.sawargaonkar@gmail.com \
--cc=punit.agrawal@arm.com \
--cc=robin.murphy@arm.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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).