From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 3 Aug 2015 21:43:32 +0200 (CEST) From: Thomas Gleixner To: Jake Oshins cc: "gregkh@linuxfoundation.org" , KY Srinivasan , LKML , "devel@linuxdriverproject.org" , "olaf@aepfle.de" , "apw@canonical.com" , "vkuznets@redhat.com" , "linux-pci@vger.kernel.org" , "bhelgaas@google.com" , "x86@kernel.org" , Jiang Liu Subject: RE: [PATCH 4/4] drivers:pci:hv: New paravirtual PCI front-end for Hyper-V VMs In-Reply-To: Message-ID: References: <1438476889-19220-1-git-send-email-jakeo@microsoft.com> <1438476889-19220-5-git-send-email-jakeo@microsoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: On Mon, 3 Aug 2015, Jake Oshins wrote: > I do have a question about your last point, though. If I build this > into the kernel, it will need to depend on sending and receiving > messages through the hv_vmbus driver, which isn't built in. It Fair enough. I missed that detail. > seemed like the indirection and glue code necessary to make that > work would be almost as big as this entire implementation (which > admittedly isn't very big.) If you prefer that, I'll do it. But it > would make more sense to me to refactor this a bit more so that > functions like the one above are exported rather than putting > hv_pcie_init_irq_domain and hv_pcie_free_irq_domain into the kernel > itself. Would that work? Yes. Thanks, tglx