From: Bjorn Helgaas <helgaas@kernel.org>
To: jakeo@microsoft.com
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
gregkh@linuxfoundation.org, kys@microsoft.com,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com,
tglx@linutronix.de, haiyangz@microsoft.com, marc.zyngier@arm.com,
haddenh@microsoft.com
Subject: Re: [PATCH RESEND v3 0/3] PCI: hv: New paravirtual PCI front-end driver
Date: Wed, 17 Feb 2016 11:26:34 -0600 [thread overview]
Message-ID: <20160217172634.GA26372@localhost> (raw)
In-Reply-To: <1455659783-20036-1-git-send-email-jakeo@microsoft.com>
On Tue, Feb 16, 2016 at 09:56:20PM +0000, jakeo@microsoft.com wrote:
> From: Jake Oshins <jakeo@microsoft.com>
>
> This version incorporates more feedback from Bjorn Helgaas. Most notably,
> I removed some debugging code and I consistently used architectural
> means for getting the PCI domain instead of just reaching into the sysdata.
>
> This is a resend of patches that enable PCI pass-through within Hyper-V
> VMs. This patch series only includes those which were deemed appropriate
> for being incorportated via the PCI tree. All other patches in previous
> patch series have gone through other trees and are now in mainline.
>
> The first two patches modify PCI so that new root PCI buses can be marked with
> an associated fwnode_handle, and so that root PCI buses can look up their
> associated IRQ domain by that handle.
>
> The last patch, introduces a new driver, hv_pcifront, which exposes root PCI
> buses in a Hyper-V VM. These root PCI buses expose real PCIe devices, or PCI
> Virtual Functions.
>
> Jake Oshins (3):
> PCI: Add fwnode_handle to pci_sysdata
> PCI: irqdomain: Look up IRQ domain by fwnode_handle
> PCI: hv: New paravirtual PCI front-end for Hyper-V VMs
>
> MAINTAINERS | 1 +
> arch/x86/include/asm/pci.h | 15 +
> drivers/pci/Kconfig | 7 +
> drivers/pci/host/Makefile | 1 +
> drivers/pci/host/pci-hyperv.c | 2359 +++++++++++++++++++++++++++++++++++++++++
> drivers/pci/probe.c | 15 +
> include/linux/pci.h | 4 +
> 7 files changed, 2402 insertions(+)
> create mode 100644 drivers/pci/host/pci-hyperv.c
Applied to pci/host-hv, thanks, Jake!
This is a new driver, and I don't think there's any risk of breaking
anything, so I think we should still be able to merge this for v4.5.
Bjorn
prev parent reply other threads:[~2016-02-17 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 21:56 [PATCH RESEND v3 0/3] PCI: hv: New paravirtual PCI front-end driver jakeo
2016-02-16 21:56 ` [PATCH RESEND v3 1/3] PCI: Add fwnode_handle to pci_sysdata jakeo
2016-02-16 21:56 ` [PATCH RESEND v3 2/3] PCI: irqdomain: Look up IRQ domain by fwnode_handle jakeo
2016-02-16 21:56 ` [PATCH RESEND v3 3/3] PCI: hv: New paravirtual PCI front-end for Hyper-V VMs jakeo
2016-02-17 17:26 ` Bjorn Helgaas [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=20160217172634.GA26372@localhost \
--to=helgaas@kernel.org \
--cc=apw@canonical.com \
--cc=bhelgaas@google.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haddenh@microsoft.com \
--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=marc.zyngier@arm.com \
--cc=olaf@aepfle.de \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).