From: Ajay Kaher <akaher@vmware.com>
To: <kys@microsoft.com>, <haiyangz@microsoft.com>
Cc: <devel@linuxdriverproject.org>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Ajay Kaher <akaher@vmware.com>
Subject: [PATCH 0/3] PCI: hv: Use vPCI protocol version 1.2 for v4.9
Date: Fri, 18 Jan 2019 02:17:15 +0530 [thread overview]
Message-ID: <1547758038-5255-1-git-send-email-akaher@vmware.com> (raw)
For now, please consider these patches for review and suggest if these can be merged to mainline kernel v4.9.
These patches add support for vPCI protocol version 1.2, by baqkpotring from v4.14 to v4.9. Individual patches are summarised below:
Patch 1: PCI: hv: Allocate physically contiguous hypercall params buffer
Backported as is.
Patch 2: PCI: hv: Add vPCI version protocol negotiation
Backported as is.
Patch 3: PCI: hv: Use vPCI protocol version 1.2 for v4.9
Change: Replaced hv_tmp_cpu_nr_to_vp_nr() with vmbus_cpu_number_to_vp_number()
to make this patch compatible for linux v4.9.
drivers/pci/host/pci-hyperv.c | 387 +++++++++++++++++++++++++++++++++---------
1 file changed, 311 insertions(+), 76 deletions(-)
--
2.7.4
next reply other threads:[~2019-01-17 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 20:47 Ajay Kaher [this message]
2019-01-17 13:21 ` [PATCH 0/3] PCI: hv: Use vPCI protocol version 1.2 for v4.9 Greg KH
2019-01-17 20:47 ` [PATCH 1/3] PCI: hv: Allocate physically contiguous hypercall params buffer Ajay Kaher
2019-01-17 14:57 ` Bjorn Helgaas
2019-01-21 13:19 ` Dan Carpenter
2019-01-21 13:36 ` Dan Carpenter
2019-01-17 20:47 ` [PATCH 2/3] PCI: hv: Add vPCI version protocol negotiation Ajay Kaher
2019-01-17 14:59 ` Bjorn Helgaas
2019-01-17 20:47 ` [PATCH 3/3] PCI: hv: Use vPCI protocol version 1.2 for v4.9 Ajay Kaher
2019-01-17 15:06 ` Bjorn Helgaas
2019-01-18 14:05 ` Ajay Kaher
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=1547758038-5255-1-git-send-email-akaher@vmware.com \
--to=akaher@vmware.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).