[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1508032142500.3825@nanos>
Date: Mon, 3 Aug 2015 21:43:32 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Jake Oshins <jakeo@...rosoft.com>
cc: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
KY Srinivasan <kys@...rosoft.com>,
LKML <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"olaf@...fle.de" <olaf@...fle.de>,
"apw@...onical.com" <apw@...onical.com>,
"vkuznets@...hat.com" <vkuznets@...hat.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"x86@...nel.org" <x86@...nel.org>,
Jiang Liu <jiang.liu@...ux.intel.com>
Subject: RE: [PATCH 4/4] drivers:pci:hv: New paravirtual PCI front-end for
Hyper-V VMs
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists