linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: jakeo@microsoft.com
Cc: kys@microsoft.com, linux-kernel@vger.kernel.org,
	devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
	vkuznets@redhat.com, bhelgaas@google.com,
	linux-pci@vger.kernel.org, pebolle@tiscali.nl,
	haiyangz@microsoft.com, mebersol@microsoft.com
Subject: Re: [PATCH v2 4/6] drivers:hv: Export a function that maps Linux proc num onto Hyper-V proc num
Date: Mon, 15 Jun 2015 12:52:16 -0700	[thread overview]
Message-ID: <20150615195216.GB5257@kroah.com> (raw)
In-Reply-To: <1434387999-1885-5-git-send-email-jakeo@microsoft.com>

On Mon, Jun 15, 2015 at 05:06:37PM +0000, jakeo@microsoft.com wrote:
> From: Jake Oshins <jakeo@microsoft.com>
> 
> This patch exports a function which maps Linux processor number onto Hyper-V
> virtual processor number.  This is necessary in order to map message-
> signaled interrupts (MSIs) into a VM, as the hypervisor needs to know the
> right target VP.
> 
> 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

What kind of comment structure is this?  It's not kernel doc :(

And "procnum" sounds like "process number", why not "cpu_number"?


  reply	other threads:[~2015-06-15 19:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 17:06 [PATCH v2 0/6] hv: Front-end driver for PCIe Pass-through on Hyper-V jakeo
2015-06-15 17:06 ` [PATCH v2 1/6] drivers:hv: Modify vmbus to search for all MMIO ranges available jakeo
2015-06-15 17:06 ` [PATCH v2 2/6] drivers:hv: Move MMIO range picking from hyper_fb.mod to hv_vmbus.mod jakeo
2015-06-15 17:06 ` [PATCH v2 3/6] arch:x86:hv: Add mechanism for Hyper-V paravirt drivers to hook msi message creation jakeo
2015-06-15 17:06 ` [PATCH v2 4/6] drivers:hv: Export a function that maps Linux proc num onto Hyper-V proc num jakeo
2015-06-15 19:52   ` Greg KH [this message]
2015-06-15 21:23     ` Jake Oshins
2015-06-15 17:06 ` [PATCH v2 5/6] drivers:hv: Define the channel type for Hyper-V PCI Express pass-through jakeo
2015-06-15 17:06 ` [PATCH v2 6/6] drivers:pci:hv: New paravirtual PCI front-end for Hyper-V VMs jakeo
2015-06-15 19:50   ` 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=20150615195216.GB5257@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=apw@canonical.com \
    --cc=bhelgaas@google.com \
    --cc=devel@linuxdriverproject.org \
    --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=mebersol@microsoft.com \
    --cc=olaf@aepfle.de \
    --cc=pebolle@tiscali.nl \
    --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).