Re: [PATCH v2 0/4] Make the iommu driver no-snoop block feature consistent

Robin Murphy
2022-04-07T18:02:20Z

On 2022-04-07 18:43, Jason Gunthorpe wrote:
> On Thu, Apr 07, 2022 at 06:03:37PM +0100, Robin Murphy wrote:
>> At a glance, this all looks about the right shape to me now, thanks!
>
> Thanks!
>
>> Ideally I'd hope patch #4 could go straight to device_iommu_capable() from
>> my Thunderbolt series, but we can figure that out in a couple of weeks once
>
> Yes, this does helps that because now the only iommu_capable call is
> in a context where a device is available :)

Derp, of course I have *two* VFIO patches waiting, the other one
touching the iommu_capable() calls (there's still IOMMU_CAP_INTR_REMAP,
which, much as I hate it and would love to boot all that stuff over to
drivers/irqchip, it's not in my way so I'm leaving it be for now). I'll
have to rebase that anyway, so merging this as-is is absolutely fine!

Cheers,
Robin.