[PATCH v2 0/4] Reenable VFIO support on POWER systems

[Michael Ellerman]

Timothy Pearson <tpearson at raptorengineering.com> writes:
> ----- Original Message -----
>> From: "Michael Ellerman" <mpe at ellerman.id.au>
>> To: "Timothy Pearson" <tpearson at raptorengineering.com>, "Timothy Pearson" <tpearson at raptorengineering.com>
>> Cc: "kvm" <kvm at vger.kernel.org>, "linuxppc-dev" <linuxppc-dev at lists.ozlabs.org>
>> Sent: Tuesday, March 21, 2023 5:33:57 AM
>> Subject: Re: [PATCH v2 0/4] Reenable VFIO support on POWER systems
>
>> Timothy Pearson <tpearson at raptorengineering.com> writes:
>>> ----- Original Message -----
>>>> From: "Timothy Pearson" <tpearson at raptorengineering.com>
>>>> To: "Michael Ellerman" <mpe at ellerman.id.au>
>>>> Cc: "Timothy Pearson" <tpearson at raptorengineering.com>, "kvm"
>>>> <kvm at vger.kernel.org>, "linuxppc-dev"
>>>> <linuxppc-dev at lists.ozlabs.org>
>>>> Sent: Thursday, March 9, 2023 1:28:20 PM
>>>> Subject: Re: [PATCH v2 0/4] Reenable VFIO support on POWER systems
>>>
>>>> ----- Original Message -----
>>>>> From: "Michael Ellerman" <mpe at ellerman.id.au>
>>>>> To: "Timothy Pearson" <tpearson at raptorengineering.com>, "kvm"
>>>>> <kvm at vger.kernel.org>
>>>>> Cc: "linuxppc-dev" <linuxppc-dev at lists.ozlabs.org>
>>>>> Sent: Thursday, March 9, 2023 5:40:01 AM
>>>>> Subject: Re: [PATCH v2 0/4] Reenable VFIO support on POWER systems
>>>> 
>>>>> Timothy Pearson <tpearson at raptorengineering.com> writes:
>>>>>> This patch series reenables VFIO support on POWER systems.  It
>>>>>> is based on Alexey Kardashevskiys's patch series, rebased and
>>>>>> successfully tested under QEMU with a Marvell PCIe SATA controller
>>>>>> on a POWER9 Blackbird host.
>>>>>>
>>>>>> Alexey Kardashevskiy (3):
>>>>>>   powerpc/iommu: Add "borrowing" iommu_table_group_ops
>>>>>>   powerpc/pci_64: Init pcibios subsys a bit later
>>>>>>   powerpc/iommu: Add iommu_ops to report capabilities and allow blocking
>>>>>>     domains
>>>>> 
>>>>> As sent the patches had lost Alexey's authorship (no From: line), I
>>>>> fixed it up when applying so the first 3 are authored by Alexey.
>>>>> 
>>>>> cheers
>>>> 
>>>> Thanks for catching that, it wasn't intentional.  Probably used a wrong Git
>>>> command...
>>>
>>> Just wanted to touch base on the patches, since they're still listed as Under
>>> Review on patchwork.  Are we good to go for the 6.4 merge window?
>> 
>> They've been in my next (and so linux-next), since last week. I just
>> haven't updated patchwork yet.
>> 
>> So yeah they are on track to go into mainline during the v6.4 merge window.
>> 
>> cheers
>
> Sounds great, thanks!  Saw them in the next tree but wasn't sure if the patchwork status was more reflective of overall status.

Yeah I guess patchwork is more reflective.

I sometimes put things in next for a few days to see if any issues shake
out, before I update patchwork. Mainly because it's a pain to un-update
patchwork if the patch needs to be backed out, but also as a signal that
the patch isn't quite locked into next yet.

cheers