Re: [PATCH v3 00/15] Introducing per-device MSI domain

2015-07-10 Thread Marc Zyngier
On 10/07/15 14:34, Lorenzo Pieralisi wrote: > On Thu, Jul 09, 2015 at 03:35:05PM +0100, Marc Zyngier wrote: > > [...] > >>> BTW, is there a reason why _all_ arm host bridges rely on >>> pcibios_msi_controller (so pci_sys_data) instead of initializing >>> the struct pci_bus.msi pointer to carry ou

Re: [PATCH v3 00/15] Introducing per-device MSI domain

2015-07-10 Thread Lorenzo Pieralisi
On Thu, Jul 09, 2015 at 03:35:05PM +0100, Marc Zyngier wrote: [...] > > BTW, is there a reason why _all_ arm host bridges rely on > > pcibios_msi_controller (so pci_sys_data) instead of initializing > > the struct pci_bus.msi pointer to carry out the MSI controller look-up ? > > Probably an orde

Re: [PATCH v3 00/15] Introducing per-device MSI domain

2015-07-09 Thread Marc Zyngier
Hi Lorenzo, On 09/07/15 14:58, Lorenzo Pieralisi wrote: > On Tue, Jul 07, 2015 at 06:17:50PM +0100, Marc Zyngier wrote: >> [Picking up this series again after sleeping on it for too long, >> hopefully still relevant] >> >> MSI-like interrupts are starting to creep out of the PCI world, and >> can

Re: [PATCH v3 00/15] Introducing per-device MSI domain

2015-07-09 Thread Lorenzo Pieralisi
On Tue, Jul 07, 2015 at 06:17:50PM +0100, Marc Zyngier wrote: > [Picking up this series again after sleeping on it for too long, > hopefully still relevant] > > MSI-like interrupts are starting to creep out of the PCI world, and > can now be seen into a number of "platform"-type busses. The > int

[PATCH v3 00/15] Introducing per-device MSI domain

2015-07-07 Thread Marc Zyngier
[Picking up this series again after sleeping on it for too long, hopefully still relevant] MSI-like interrupts are starting to creep out of the PCI world, and can now be seen into a number of "platform"-type busses. The introduction of the MSI domains feature in v3.19 recognised that fact, and st