From: Jork Loeser <jloeser@linuxonhyperv.com>
To: jloeser@microsoft.com, helgaas@kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
vkuznets@redhat.com, jasowang@redhat.com,
leann.ogasawara@canonical.com, marcelo.cerri@canonical.com,
sthemmin@microsoft.com
Subject: [PATCH-v2 0/5] Hyper-V vPCI: use vPCI protocol version 1.2
Date: Wed, 24 May 2017 13:41:23 -0700 [thread overview]
Message-ID: <1495658488-13199-1-git-send-email-jloeser@linuxonhyperv.com> (raw)
From: Jork Loeser <jloeser@microsoft.com>
Update the Hyper-V vPCI driver to use the Server-2016 version of the vPCI
protocol, fixing MSI creation and retargeting issues.
Changes since v1:
- reduced spew in protocol negotiation (Dan Carpenter)
- work-around work racing Hyper-V patch (Stephen Hemminger)
- formatting (Dan)
Jork Loeser (5):
Hyper-V vPCI: Minor format and semantic fix
Hyper-V vPCI: Use page allocation for hbus structure
PCI-HyperV vPCI: Temporary own CPU-number-to-vCPU-number infra
Hyper-V vPCI: Add vPCI version protocol negotiation
Hyper-V vPCI: use vPCI protocol version 1.2
arch/x86/include/uapi/asm/hyperv.h | 6 +
drivers/pci/host/pci-hyperv.c | 445 ++++++++++++++++++++++++++++++-------
2 files changed, 370 insertions(+), 81 deletions(-)
--
2.7.4
next reply other threads:[~2017-05-24 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 20:41 Jork Loeser [this message]
2017-05-24 20:41 ` [PATCH-v2 1/5] Hyper-V vPCI: Minor format and semantic fix Jork Loeser
2017-05-24 20:41 ` [PATCH-v2 2/5] Hyper-V vPCI: Use page allocation for hbus structure Jork Loeser
2017-05-24 20:41 ` [PATCH-v2 3/5] PCI-HyperV vPCI: Temporary own CPU-number-to-vCPU-number infra Jork Loeser
2017-05-24 20:41 ` [PATCH-v2 4/5] Hyper-V vPCI: Add vPCI version protocol negotiation Jork Loeser
2017-05-24 20:41 ` [PATCH-v2 5/5] Hyper-V vPCI: use vPCI protocol version 1.2 Jork Loeser
2017-05-30 19:45 ` [PATCH-v2 0/5] " Bjorn Helgaas
2017-05-30 22:13 ` KY Srinivasan
2017-05-30 22:34 ` Bjorn Helgaas
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=1495658488-13199-1-git-send-email-jloeser@linuxonhyperv.com \
--to=jloeser@linuxonhyperv.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=helgaas@kernel.org \
--cc=jasowang@redhat.com \
--cc=jloeser@microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=olaf@aepfle.de \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.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 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).