Displaying 20 results from an estimated 231 matches for "smmu".
Did you mean:
mmu
2016 Dec 20
4
[RFC PATCH] vring: Force use of DMA API for ARM-based systems
Booting Linux on an ARM fastmodel containing an SMMU emulation results
in an unexpected I/O page fault from the legacy virtio-blk PCI device:
[ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
[ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010
[ 1.211880] arm-smmu-v3 2b400000.smmu: 0x0000020800000000
[ 1.211959] arm-smmu-...
2016 Dec 20
4
[RFC PATCH] vring: Force use of DMA API for ARM-based systems
Booting Linux on an ARM fastmodel containing an SMMU emulation results
in an unexpected I/O page fault from the legacy virtio-blk PCI device:
[ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
[ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010
[ 1.211880] arm-smmu-v3 2b400000.smmu: 0x0000020800000000
[ 1.211959] arm-smmu-...
2017 Jan 10
3
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote:
> From: Will Deacon <will.deacon at arm.com>
>
> Booting Linux on an ARM fastmodel containing an SMMU emulation results
> in an unexpected I/O page fault from the legacy virtio-blk PCI device:
>
> [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
> [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010
> [ 1.211880] arm-smmu-v3 2b400000.smmu: 0x0000020800000000...
2017 Jan 10
3
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote:
> From: Will Deacon <will.deacon at arm.com>
>
> Booting Linux on an ARM fastmodel containing an SMMU emulation results
> in an unexpected I/O page fault from the legacy virtio-blk PCI device:
>
> [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
> [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010
> [ 1.211880] arm-smmu-v3 2b400000.smmu: 0x0000020800000000...
2017 Jan 12
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...acon wrote:
> On Wed, Jan 11, 2017 at 01:33:31AM +0200, Michael S. Tsirkin wrote:
> > On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote:
> > > From: Will Deacon <will.deacon at arm.com>
> > >
> > > Booting Linux on an ARM fastmodel containing an SMMU emulation results
> > > in an unexpected I/O page fault from the legacy virtio-blk PCI device:
> > >
> > > [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
> > > [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010
> > > [ 1.211...
2017 Jan 12
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...acon wrote:
> On Wed, Jan 11, 2017 at 01:33:31AM +0200, Michael S. Tsirkin wrote:
> > On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote:
> > > From: Will Deacon <will.deacon at arm.com>
> > >
> > > Booting Linux on an ARM fastmodel containing an SMMU emulation results
> > > in an unexpected I/O page fault from the legacy virtio-blk PCI device:
> > >
> > > [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
> > > [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010
> > > [ 1.211...
2017 Jan 11
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...m.com> wrote:
> On Wed, Jan 11, 2017 at 01:33:31AM +0200, Michael S. Tsirkin wrote:
>> On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote:
>> > From: Will Deacon <will.deacon at arm.com>
>> >
>> > Booting Linux on an ARM fastmodel containing an SMMU emulation results
>> > in an unexpected I/O page fault from the legacy virtio-blk PCI device:
>> >
>> > [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
>> > [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010
>> > [ 1.211880]...
2017 Jan 11
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...m.com> wrote:
> On Wed, Jan 11, 2017 at 01:33:31AM +0200, Michael S. Tsirkin wrote:
>> On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote:
>> > From: Will Deacon <will.deacon at arm.com>
>> >
>> > Booting Linux on an ARM fastmodel containing an SMMU emulation results
>> > in an unexpected I/O page fault from the legacy virtio-blk PCI device:
>> >
>> > [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
>> > [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010
>> > [ 1.211880]...
2017 Jan 13
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...01:33:31AM +0200, Michael S. Tsirkin wrote:
> > > > On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote:
> > > > > From: Will Deacon <will.deacon at arm.com>
> > > > >
> > > > > Booting Linux on an ARM fastmodel containing an SMMU emulation results
> > > > > in an unexpected I/O page fault from the legacy virtio-blk PCI device:
> > > > >
> > > > > [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
> > > > > [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00...
2017 Jan 06
2
[RFC PATCH] vring: Force use of DMA API for ARM-based systems
On 06/01/17 17:48, Jean-Philippe Brucker wrote:
> Hi Will,
>
> On 20/12/16 15:14, Will Deacon wrote:
>> Booting Linux on an ARM fastmodel containing an SMMU emulation results
>> in an unexpected I/O page fault from the legacy virtio-blk PCI device:
>>
>> [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
>> [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010
>> [ 1.211880] arm-smmu-v3 2b400000.smmu:...
2017 Jan 13
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...01:33:31AM +0200, Michael S. Tsirkin wrote:
> > > > On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote:
> > > > > From: Will Deacon <will.deacon at arm.com>
> > > > >
> > > > > Booting Linux on an ARM fastmodel containing an SMMU emulation results
> > > > > in an unexpected I/O page fault from the legacy virtio-blk PCI device:
> > > > >
> > > > > [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
> > > > > [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00...
2017 Jan 06
2
[RFC PATCH] vring: Force use of DMA API for ARM-based systems
On 06/01/17 17:48, Jean-Philippe Brucker wrote:
> Hi Will,
>
> On 20/12/16 15:14, Will Deacon wrote:
>> Booting Linux on an ARM fastmodel containing an SMMU emulation results
>> in an unexpected I/O page fault from the legacy virtio-blk PCI device:
>>
>> [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
>> [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010
>> [ 1.211880] arm-smmu-v3 2b400000.smmu:...
2017 Jan 24
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...gt;>>>>>>>>> On Fri, Jan 13, 2017 at 09:25:22AM +0000, Will Deacon wrote:
>>>>>>>>>>> On Fri, Jan 13, 2017 at 12:12:56AM +0200, Michael S. Tsirkin wrote:
>>>>>>>>>>>> I'd rather people didn't use SMMU with legacy devices.
>>>>>>>>>>>
>>>>>>>>>>> I'm afraid we've been doing that for two years and the model already
>>>>>>>>>>> exists in a mature state, being actively used for development and...
2017 Jan 24
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...gt;>>>>>>>>> On Fri, Jan 13, 2017 at 09:25:22AM +0000, Will Deacon wrote:
>>>>>>>>>>> On Fri, Jan 13, 2017 at 12:12:56AM +0200, Michael S. Tsirkin wrote:
>>>>>>>>>>>> I'd rather people didn't use SMMU with legacy devices.
>>>>>>>>>>>
>>>>>>>>>>> I'm afraid we've been doing that for two years and the model already
>>>>>>>>>>> exists in a mature state, being actively used for development and...
2017 Jan 19
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...gt; > > > > > > > On Fri, Jan 13, 2017 at 09:25:22AM +0000, Will Deacon wrote:
> > > > > > > > > On Fri, Jan 13, 2017 at 12:12:56AM +0200, Michael S. Tsirkin wrote:
> > > > > > > > > > I'd rather people didn't use SMMU with legacy devices.
> > > > > > > > >
> > > > > > > > > I'm afraid we've been doing that for two years and the model already
> > > > > > > > > exists in a mature state, being actively used for development and...
2017 Jan 19
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...gt; > > > > > > > On Fri, Jan 13, 2017 at 09:25:22AM +0000, Will Deacon wrote:
> > > > > > > > > On Fri, Jan 13, 2017 at 12:12:56AM +0200, Michael S. Tsirkin wrote:
> > > > > > > > > > I'd rather people didn't use SMMU with legacy devices.
> > > > > > > > >
> > > > > > > > > I'm afraid we've been doing that for two years and the model already
> > > > > > > > > exists in a mature state, being actively used for development and...
2020 Apr 14
0
[PATCH v2 17/33] iommu/arm-smmu: Convert to probe/release_device() call-backs
From: Joerg Roedel <jroedel at suse.de>
Convert the arm-smmu and arm-smmu-v3 drivers to use the probe_device() and
release_device() call-backs of iommu_ops, so that the iommu core code does the
group and sysfs setup.
Signed-off-by: Joerg Roedel <jroedel at suse.de>
---
drivers/iommu/arm-smmu-v3.c | 38 ++++++++++--------------------------
drivers/iom...
2017 Jan 13
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...ote:
> > > > > > On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote:
> > > > > > > From: Will Deacon <will.deacon at arm.com>
> > > > > > >
> > > > > > > Booting Linux on an ARM fastmodel containing an SMMU emulation results
> > > > > > > in an unexpected I/O page fault from the legacy virtio-blk PCI device:
> > > > > > >
> > > > > > > [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
> > > > > > > [ 1...
2017 Jan 13
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...ote:
> > > > > > On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote:
> > > > > > > From: Will Deacon <will.deacon at arm.com>
> > > > > > >
> > > > > > > Booting Linux on an ARM fastmodel containing an SMMU emulation results
> > > > > > > in an unexpected I/O page fault from the legacy virtio-blk PCI device:
> > > > > > >
> > > > > > > [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received:
> > > > > > > [ 1...
2020 Apr 08
1
[RFC PATCH 17/34] iommu/arm-smmu: Store device instead of group in arm_smmu_s2cr
...use-after-free of A
>>
>> Preserving the logical behaviour here would probably look *something* like
>> the mangled diff below, but I haven't thought it through 100%.
>
> Yeah, I think you are right. How about just moving the loop which sets
> s2crs[idx].group to arm_smmu_device_group()? In that case I can drop
> this patch and leave the group pointer in place.
Isn't that exactly what I suggested? :)
I don't recall for sure, but knowing me, that bit of group bookkeeping
is only where it currently is because it cheekily saves iterating the
IDs a second...