> > 45: 1 0 3377 11194 PCI-MSI-edge
> > FPGA_DEV> > RES: 14 20 21 3398 Rescheduling
> > interrupts---> Many RES Interrtups!!
>
> I don't know, but I'll fix the line wrap for anyone else that wants to
> have a look. The
On Mon, 2013-01-07 at 20:14 +, Krishna J wrote:
> Hi Alex,
> > MSI routing updates aren't currently handled by pci-assign or
> > vfio-pci (when using KVM acceleration), which means that trying to
> > set interrupt SMP affinity in the guest has no effect unless MSI is
> > completely disabled and
Hi Alex,
> MSI routing updates aren't currently handled by pci-assign or
> vfio-pci (when using KVM acceleration), which means that trying to
> set interrupt SMP affinity in the guest has no effect unless MSI is
> completely disabled and re-enabled. This series fixes this for both
> device assignm
On 2012-11-28 00:21, Alex Williamson wrote:
> On Wed, 2012-11-28 at 00:08 +0100, Jan Kiszka wrote:
>> On 2012-11-27 23:00, Alex Williamson wrote:
>>> This is post-1.3 material, so I'll just post it as an RFC for now.
>>>
>>> MSI routing updates aren't currently handled by pci-assign or
>>> vfio-pci
On Wed, 2012-11-28 at 00:08 +0100, Jan Kiszka wrote:
> On 2012-11-27 23:00, Alex Williamson wrote:
> > This is post-1.3 material, so I'll just post it as an RFC for now.
> >
> > MSI routing updates aren't currently handled by pci-assign or
> > vfio-pci (when using KVM acceleration), which means th
On 2012-11-27 23:00, Alex Williamson wrote:
> This is post-1.3 material, so I'll just post it as an RFC for now.
>
> MSI routing updates aren't currently handled by pci-assign or
> vfio-pci (when using KVM acceleration), which means that trying to
> set interrupt SMP affinity in the guest has no e
This is post-1.3 material, so I'll just post it as an RFC for now.
MSI routing updates aren't currently handled by pci-assign or
vfio-pci (when using KVM acceleration), which means that trying to
set interrupt SMP affinity in the guest has no effect unless MSI is
completely disabled and re-enabled
