From: Jork Loeser <Jork.Loeser@microsoft.com>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>,
KY Srinivasan <kys@microsoft.com>,
"bhelgaas@google.com" <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"Stephen Hemminger" <sthemmin@microsoft.com>
Subject: RE: [PATCH] hv: fix msi affinity when device requests all possible CPU's
Date: Thu, 29 Jun 2017 22:08:00 +0000 [thread overview]
Message-ID: <MWHPR21MB0639EC5C9B141D0591D1D957F1D20@MWHPR21MB0639.namprd21.prod.outlook.com> (raw)
In-Reply-To: <DM5PR21MB0476CFFA739B74FBB3B6F42DA0D20@DM5PR21MB0476.namprd21.prod.outlook.com>
> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Wednesday, June 28, 2017 4:22 PM
> To: KY Srinivasan <kys@microsoft.com>; bhelgaas@google.com
> Cc: linux-pci@vger.kernel.org; devel@linuxdriverproject.org; Stephen
> Hemminger <sthemmin@microsoft.com>
> Subject: [PATCH] hv: fix msi affinity when device requests all possible C=
PU's
>=20
> When Intel 10G (ixgbevf) is passed to a Hyper-V guest with SR-IOV, the dr=
iver
> requests affinity with all possible CPU's (0-239) even those CPU's are no=
t online
> (and will never be). Because of this the device is unable to correctly ge=
t MSI
> interrupt's setup.
>=20
> This was caused by the change in 4.12 that converted this affinity into a=
ll
> possible CPU's (0-31) but then host reports an error since this is larger=
than the
> number of online cpu's.
>=20
> Previously, this worked (up to 4.12-rc1) because only online cpu's would =
be put
> in mask passed to the host.
>=20
> This patch applies only to 4.12.
> The driver in linux-next needs a a different fix because of the changes t=
o PCI
> host protocol version.
The vPCI patch in linux-next has the issue fixed already.
Regards,
Jork
next prev parent reply other threads:[~2017-06-29 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 23:22 [PATCH] hv: fix msi affinity when device requests all possible CPU's Stephen Hemminger
[not found] ` <DM5PR21MB0476CFFA739B74FBB3B6F42DA0D20@DM5PR21MB0476.namprd21.prod.outlook.com>
2017-06-29 22:08 ` Jork Loeser [this message]
2017-06-29 23:57 ` Stephen Hemminger
2017-07-02 21:38 ` Bjorn Helgaas
2017-07-04 21:59 ` Stephen Hemminger
2017-07-05 19:49 ` Bjorn Helgaas
2017-07-05 20:07 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MWHPR21MB0639EC5C9B141D0591D1D957F1D20@MWHPR21MB0639.namprd21.prod.outlook.com \
--to=jork.loeser@microsoft.com \
--cc=bhelgaas@google.com \
--cc=devel@linuxdriverproject.org \
--cc=kys@microsoft.com \
--cc=linux-pci@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.