RE: [PATCH RFC v1 2/3] vfio/pci: enable vector on dynamic MSI-X allocation

Hi Alex, > On July 28, 2023 1:25 AM, Alex Williamson wrote: > > On Thu, 27 Jul 2023 03:24:09 -0400 > Jing Liu wrote: > > > The vector_use callback is used to enable vector that is unmasked in > > guest. The kernel used to only support static MSI-X allocation. When > > allocating a new interru

Re: [PATCH RFC v1 2/3] vfio/pci: enable vector on dynamic MSI-X allocation

On 7/27/23 09:24, Jing Liu wrote: The vector_use callback is used to enable vector that is unmasked in guest. The kernel used to only support static MSI-X allocation. When allocating a new interrupt using "static MSI-X allocation" kernels, Qemu first disables all previously allocated vectors and

Re: [PATCH RFC v1 2/3] vfio/pci: enable vector on dynamic MSI-X allocation

On Thu, 27 Jul 2023 03:24:09 -0400 Jing Liu wrote: > The vector_use callback is used to enable vector that is unmasked in > guest. The kernel used to only support static MSI-X allocation. When > allocating a new interrupt using "static MSI-X allocation" kernels, > Qemu first disables all previous

[PATCH RFC v1 2/3] vfio/pci: enable vector on dynamic MSI-X allocation

The vector_use callback is used to enable vector that is unmasked in guest. The kernel used to only support static MSI-X allocation. When allocating a new interrupt using "static MSI-X allocation" kernels, Qemu first disables all previously allocated vectors and then re-allocates all including the