[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <943b0907-f2ee-63c1-7134-997ffaf6f348@arm.com>
Date: Tue, 23 Apr 2019 10:26:11 +0100
From: Julien Grall <julien.grall@....com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
logang@...tatee.com, douliyangs@...il.com,
miquel.raynal@...tlin.com, marc.zyngier@....com,
jason@...edaemon.net, joro@...tes.org, robin.murphy@....com,
bigeasy@...utronix.de, linux-rt-users@...r.kernel.org
Subject: Re: [PATCH 1/7] genirq/msi: Add a new field in msi_desc to store an
IOMMU cookie
Hi Thomas,
On 4/18/19 8:28 PM, Thomas Gleixner wrote:
> On Thu, 18 Apr 2019, Julien Grall wrote:
>
>> When an MSI doorbell is located downstream of an IOMMU, it is required
>> to swizzle the physical address with an appropriately-mapped IOVA for any
>> device attached to one of our DMA ops domain.
>>
>> At the moment, the allocation of the mapping may be done when composing
>> the message. However, the composing may be done in non-preemtible
>> context while the allocation requires to be called from preemptible
>> context.
>>
>> A follow-up patch will split the current logic in two functions
>> requiring to keep an IOMMU cookie per MSI.
>>
>> This patch introduces a new field in msi_desc to store an IOMMU cookie
>> when CONFIG_IOMMU_DMA is selected.
>
> # git grep 'This patch' Documentation/process/
>
> Applied to the whole series.
Sorry for that. I will rework all the commit messages and resend the series.
Cheers,
--
Julien Grall
Powered by blists - more mailing lists