This patch makes sense since VFs need to be assigned resources (especially
MSI-X interrupt count)
before making these VFs visible, so that the kernel PCI enumeration code reads
correct MSI-X
interrupt count for the VFs.
Regards,
Sergey
On 4/29/2024 5:49 AM, Ross Lagerwall wrote:
When the PCI functions are created, Xen is informed about them and
caches the number of MSI-X entries each function has. However, the
number of MSI-X entries is not set until after the hardware has been
configured and the VFs have been started.
On Mon, Apr 29, 2024 at 2:04 PM Paul Menzel wrote:
>
> Dear Ross,
>
>
> Thank you for your patch.
>
> Am 29.04.24 um 14:49 schrieb Ross Lagerwall:
> > When the PCI functions are created, Xen is informed about them and
> > caches the number of MSI-X entries each function has. However, the
> >
Dear Ross,
Thank you for your patch.
Am 29.04.24 um 14:49 schrieb Ross Lagerwall:
When the PCI functions are created, Xen is informed about them and
caches the number of MSI-X entries each function has. However, the
number of MSI-X entries is not set until after the hardware has been
When the PCI functions are created, Xen is informed about them and
caches the number of MSI-X entries each function has. However, the
number of MSI-X entries is not set until after the hardware has been
configured and the VFs have been started. This prevents
PCI-passthrough from working because
