[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZBiF6/AkznbXHWbx@nvidia.com>
Date: Mon, 20 Mar 2023 13:12:27 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Alex Williamson <alex.williamson@...hat.com>
Cc: Reinette Chatre <reinette.chatre@...el.com>, yishaih@...dia.com,
shameerali.kolothum.thodi@...wei.com, kevin.tian@...el.com,
tglx@...utronix.de, darwi@...utronix.de, kvm@...r.kernel.org,
dave.jiang@...el.com, jing2.liu@...el.com, ashok.raj@...el.com,
fenghua.yu@...el.com, tom.zanussi@...ux.intel.com,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 8/8] vfio/pci: Clear VFIO_IRQ_INFO_NORESIZE for MSI-X
On Fri, Mar 17, 2023 at 05:01:49PM -0600, Alex Williamson wrote:
> pci_setup_msix_device_domain() says it returns true if:
>
> * True when:
> * - The device does not have a MSI parent irq domain associated,
> * which keeps the legacy architecture specific and the global
> * PCI/MSI domain models working
> * - The MSI-X domain exists already
> * - The MSI-X domain was successfully allocated
>
> That first one seems concerning, dynamic allocation only works on irq
> domain configurations. What does that exclude and do we care about any
> of them for vfio-pci?
Several archs and other weird things override the MSI-X programming. Eg
by turning it into a hypervisor call or something. These were not
converted to dynamic mode.
So at the VFIO level you can get end up with MSI support but done
through legacy paths that don't support dynamic allocation. Eg on
POWER, xen, etc.
Jason
Powered by blists - more mailing lists