On 05/30/2014 11:45 PM, Alexander Graf wrote:
On 30.05.14 15:36, Alexey Kardashevskiy wrote:
On 05/30/2014 08:08 PM, Alexander Graf wrote:
On 30.05.14 11:34, Alexey Kardashevskiy wrote:
Currently SPAPR PHB keeps track of all allocated MSI (here and below
MSI stands for both MSI and MSIX)
Currently SPAPR PHB keeps track of all allocated MSI (here and below
MSI stands for both MSI and MSIX) interrupt because
XICS used to be unable to reuse interrupts. This is a problem for
dynamic MSI reconfiguration which happens when guest reloads a driver
or performs PCI hotplug. Another problem
On 30.05.14 11:34, Alexey Kardashevskiy wrote:
Currently SPAPR PHB keeps track of all allocated MSI (here and below
MSI stands for both MSI and MSIX) interrupt because
XICS used to be unable to reuse interrupts. This is a problem for
dynamic MSI reconfiguration which happens when guest reloads
On 05/30/2014 08:08 PM, Alexander Graf wrote:
On 30.05.14 11:34, Alexey Kardashevskiy wrote:
Currently SPAPR PHB keeps track of all allocated MSI (here and below
MSI stands for both MSI and MSIX) interrupt because
XICS used to be unable to reuse interrupts. This is a problem for
dynamic MSI
On 30.05.14 15:36, Alexey Kardashevskiy wrote:
On 05/30/2014 08:08 PM, Alexander Graf wrote:
On 30.05.14 11:34, Alexey Kardashevskiy wrote:
Currently SPAPR PHB keeps track of all allocated MSI (here and below
MSI stands for both MSI and MSIX) interrupt because
XICS used to be unable to reuse
