This patch makes use of the new delayed mmu release notifier feature in
mm code. This is necessary because on the one hand amd_iommu_unbind_pasid
must be called explicitly during the tear-down of a process, but on the
other hand, it could be called from a function (e.g. in amdkfd)
which is a call-b
On Thu, Oct 16, 2014 at 10:23:07AM -0700, Olav Haugan wrote:
> On 10/15/2014 2:16 AM, Thierry Reding wrote:
> >Perhaps make the return value ssize_t so that we can propagate errors?
> >
>
> I am fine with that. Joerg?
I am not so sure this is a good idea. On error the function should
return the s
On Fri, Oct 17, 2014 at 10:22:13AM +0800, Daniel Kurtz wrote:
> Gentle ping.
>
> Any more feedback on the rockchip iommu driver?
I'll look at it in more detail when the merge window is over.
Joerg
___
iommu mailing list
iommu@lists.linux-foun
On 2014/10/17 15:23, Michael Ellerman wrote:
> On Wed, 2014-10-15 at 11:07 +0800, Yijing Wang wrote:
>> Use MSI chip framework instead of arch MSI functions to configure
>> MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
>>
>> Signed-off-by: Yijing Wang
>> ---
>> Hi Michael,
On Wed, 2014-10-15 at 11:07 +0800, Yijing Wang wrote:
> Use MSI chip framework instead of arch MSI functions to configure
> MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
>
> Signed-off-by: Yijing Wang
> ---
> Hi Michael,
>I dropped the Acked-by , because this version h
