linux-kernel - Re: [PATCH v2 4/6] drivers:hv: Export a function that maps Linux proc num onto Hyper-V proc num

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150615195216.GB5257@kroah.com>
Date:	Mon, 15 Jun 2015 12:52:16 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	jakeo@...rosoft.com
Cc:	kys@...rosoft.com, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org, olaf@...fle.de, apw@...onical.com,
	vkuznets@...hat.com, bhelgaas@...gle.com,
	linux-pci@...r.kernel.org, pebolle@...cali.nl,
	haiyangz@...rosoft.com, mebersol@...rosoft.com
Subject: Re: [PATCH v2 4/6] drivers:hv: Export a function that maps Linux
 proc num onto Hyper-V proc num

On Mon, Jun 15, 2015 at 05:06:37PM +0000, jakeo@...rosoft.com wrote:
> From: Jake Oshins <jakeo@...rosoft.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@...rosoft.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"?

--
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/