From: jakeo@microsoft.com
To: gregkh@linuxfoundation.org, 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
Cc: Jake Oshins <jakeo@microsoft.com>
Subject: [PATCH 4/6] drivers:hv: Export a function that maps Linux proc num onto Hyper-V proc num
Date: Thu, 11 Jun 2015 16:22:25 +0000 [thread overview]
Message-ID: <1434039747-44535-5-git-send-email-jakeo@microsoft.com> (raw)
In-Reply-To: <1434039747-44535-1-git-send-email-jakeo@microsoft.com>
From: Jake Oshins <jakeo@microsoft.com>
Signed-off-by: Jake Oshins <jakeo@microsoft.com>
---
drivers/hv/vmbus_drv.c | 16 ++++++++++++++++
include/linux/hyperv.h | 2 ++
2 files changed, 18 insertions(+)
diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
index 067a469..65e4eb6 100644
--- a/drivers/hv/vmbus_drv.c
+++ b/drivers/hv/vmbus_drv.c
@@ -1158,6 +1158,22 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj,
}
EXPORT_SYMBOL_GPL(vmbus_allocate_mmio);
+/**
+ * This function returns the mapping between the Linux processor
+ * number and
+ * the hypervisor's virtual processor number, useful in making
+ * hypercalls and such that talk about specific processors.
+ *
+ * @param procnum - in Linux terms
+ *
+ * @return int - in Hyper-V terms
+ */
+int vmbus_procnum_to_vpnum(int procnum)
+{
+ return hv_context.vp_index[procnum];
+}
+EXPORT_SYMBOL_GPL(vmbus_procnum_to_vpnum);
+
static int vmbus_acpi_add(struct acpi_device *device)
{
acpi_status result;
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
index ffd98d7..6fec42d 100644
--- a/include/linux/hyperv.h
+++ b/include/linux/hyperv.h
@@ -987,6 +987,8 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj,
resource_size_t size, resource_size_t align,
bool fb_overlap_ok);
+int vmbus_procnum_to_vpnum(int procnum);
+
/**
* VMBUS_DEVICE - macro used to describe a specific hyperv vmbus device
*
--
1.9.1
next prev parent reply other threads:[~2015-06-11 16:22 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 ` jakeo [this message]
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 ` [PATCH 0/6] Front-end driver for PCIe Pass-through on Hyper-V Greg KH
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=1434039747-44535-5-git-send-email-jakeo@microsoft.com \
--to=jakeo@microsoft.com \
--cc=apw@canonical.com \
--cc=bhelgaas@google.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@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;
as well as URLs for NNTP newsgroup(s).