From: Greg KH <gregkh@linuxfoundation.org>
To: jakeo@microsoft.com
Cc: kys@microsoft.com, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
vkuznets@redhat.com, linux-pci@vger.kernel.org,
bhelgaas@google.com, mebersol@microsoft.com,
haiyangz@microsoft.com
Subject: Re: [PATCH 0/6] Front-end driver for PCIe Pass-through on Hyper-V
Date: Thu, 11 Jun 2015 10:47:26 -0700 [thread overview]
Message-ID: <20150611174726.GD22639@kroah.com> (raw)
In-Reply-To: <1434039747-44535-1-git-send-email-jakeo@microsoft.com>
On Thu, Jun 11, 2015 at 04:22:21PM +0000, jakeo@microsoft.com wrote:
> From: Jake Oshins <jakeo@microsoft.com>
>
> This patch does some slight refactoring on the hv_vmbus driver and its
> dependents and then introduces a new paravirtual front-end driver for PCI
> which supports PCI Express devices passed through to a Linux guest running
> in a Hyper-V VM.
>
> To support this front-end, several new mechanisms are introduced:
>
> 1 - A common way of finding free memory-mapped I/O space in a Hyper-V VM,
> available to all Hyper-V-related drivers.
>
> 2 - A way of handling PCI Message-Signaled Interrupt (MSI and MSI-X)
> creation and formatting when Hyper-V is running.
>
> 3 - A mapping function from Linux processor number to Hyper-V virtual
> processor number, available to drivers, which is necessary for MSI(-X)
> creation.
>
> The Hyper-V Frame Buffer driver is modified to use the MMIO space
> allocation function so that its allocations both don't collide with the
> PCI front end and so that the chosen range can come from any available
> part of MMIO space.
>
> Finally, the new PCI front-end driver is the last patch in the series.
All of this information needs to be in the patches themselves, they all
do not have any changelog information in them at all, making them not
acceptable at all.
Please fix all of this up and resend.
thanks,
greg k-h
prev parent reply other threads:[~2015-06-11 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 16:22 [PATCH 0/6] Front-end driver for PCIe Pass-through on Hyper-V jakeo
2015-06-11 16:22 ` [PATCH 1/6] drivers:hv: Modify vmbus to search for all MMIO ranges available jakeo
2015-06-11 16:22 ` [PATCH 2/6] drivers:hv: Move MMIO range picking from hyper_fb.mod to hv_vmbus.mod jakeo
2015-06-11 17:46 ` Greg KH
2015-06-11 16:22 ` [PATCH 3/6] arch:x86:hv: Add mechanism for Hyper-V paravirt drivers to hook msi message creation jakeo
2015-06-11 16:22 ` [PATCH 4/6] drivers:hv: Export a function that maps Linux proc num onto Hyper-V proc num jakeo
2015-06-11 16:22 ` [PATCH 5/6] drivers:hv: Define the channel type for Hyper-V PCI Express pass-through jakeo
2015-06-11 16:22 ` [PATCH 6/6] drivers:pci:hv: New paravirtual PCI front-end for Hyper-V VMs jakeo
2015-06-11 17:46 ` Greg KH
2015-06-12 8:44 ` Paul Bolle
2015-06-12 15:11 ` Jake Oshins
2015-06-12 16:14 ` gregkh
2015-06-11 17:47 ` Greg KH [this message]
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=20150611174726.GD22639@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=bhelgaas@google.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=jakeo@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mebersol@microsoft.com \
--cc=olaf@aepfle.de \
--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