From: Thomas Gleixner <tglx@linutronix.de>
To: Jake Oshins <jakeo@microsoft.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
KY Srinivasan <kys@microsoft.com>,
LKML <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"x86@kernel.org" <x86@kernel.org>,
Jiang Liu <jiang.liu@linux.intel.com>
Subject: RE: [PATCH 4/4] drivers:pci:hv: New paravirtual PCI front-end for Hyper-V VMs
Date: Mon, 3 Aug 2015 21:43:32 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1508032142500.3825@nanos> (raw)
In-Reply-To: <DM2PR0301MB1232A1E50FA39BEAB5707FEDAB770@DM2PR0301MB1232.namprd03.prod.outlook.com>
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
next prev parent reply other threads:[~2015-08-03 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 0:54 [PATCH 0/4] New Paravirtual front-end for PCI in a Hyper-V VM jakeo
2015-08-02 0:54 ` [PATCH 1/4] drivers:hv: Export a function that maps Linux CPU num onto Hyper-V proc num jakeo
2015-08-02 0:54 ` [PATCH 2/4] drivers:hv: Define the channel type for Hyper-V PCI Express pass-through jakeo
2015-08-02 0:54 ` [PATCH 3/4] drivers:x86:pci: Make it possible to implement a PCI MSI IRQ Domain in a module jakeo
2015-08-02 0:54 ` [PATCH 4/4] drivers:pci:hv: New paravirtual PCI front-end for Hyper-V VMs jakeo
2015-08-02 8:47 ` Thomas Gleixner
2015-08-03 19:19 ` Jake Oshins
2015-08-03 19:43 ` Thomas Gleixner [this message]
2015-08-03 9:18 ` Paul Bolle
2015-08-03 9:52 ` Dan Carpenter
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=alpine.DEB.2.11.1508032142500.3825@nanos \
--to=tglx@linutronix.de \
--cc=apw@canonical.com \
--cc=bhelgaas@google.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jakeo@microsoft.com \
--cc=jiang.liu@linux.intel.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
/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