On Wed, 5 Jul 2017 14:49:33 -0500
Bjorn Helgaas wrote:
> On Tue, Jul 04, 2017 at 02:59:42PM -0700, Stephen Hemminger wrote:
> > On Sun, 2 Jul 2017 16:38:19 -0500
> > Bjorn Helgaas wrote:
> >
> > > On Wed, Jun 28, 2017 at 04:22:04PM -0700, Stephen Hemminger wrote:
> > > > When Intel 10G (ixg
On Tue, Jul 04, 2017 at 02:59:42PM -0700, Stephen Hemminger wrote:
> On Sun, 2 Jul 2017 16:38:19 -0500
> Bjorn Helgaas wrote:
>
> > On Wed, Jun 28, 2017 at 04:22:04PM -0700, Stephen Hemminger wrote:
> > > When Intel 10G (ixgbevf) is passed to a Hyper-V guest with SR-IOV,
> > > the driver requests
On Sun, 2 Jul 2017 16:38:19 -0500
Bjorn Helgaas wrote:
> On Wed, Jun 28, 2017 at 04:22:04PM -0700, Stephen Hemminger wrote:
> > When Intel 10G (ixgbevf) is passed to a Hyper-V guest with SR-IOV,
> > the driver requests affinity with all possible CPU's (0-239) even
> > those CPU's are not online (
On Wed, Jun 28, 2017 at 04:22:04PM -0700, Stephen Hemminger wrote:
> When Intel 10G (ixgbevf) is passed to a Hyper-V guest with SR-IOV,
> the driver requests affinity with all possible CPU's (0-239) even
> those CPU's are not online (and will never be). Because of this the device
> is unable to cor
project.org; Stephen
> Hemminger
> Subject: [PATCH] hv: fix msi affinity when device requests all possible CPU's
>
> When Intel 10G (ixgbevf) is passed to a Hyper-V guest with SR-IOV, the driver
> requests affinity with all possible CPU's (0-239) even those CPU's are not
&
hv: fix msi affinity when device requests all possible CPU's
>
> When Intel 10G (ixgbevf) is passed to a Hyper-V guest with SR-IOV, the driver
> requests affinity with all possible CPU's (0-239) even those CPU's are not
> online
> (and will never be). Becaus
When Intel 10G (ixgbevf) is passed to a Hyper-V guest with SR-IOV,
the driver requests affinity with all possible CPU's (0-239) even
those CPU's are not online (and will never be). Because of this the device
is unable to correctly get MSI interrupt's setup.
This was caused by the change in 4.12 th
