On Mon, Jun 15, 2015 at 05:06:37PM +0000, jakeo@xxxxxxxxxxxxx wrote: > From: Jake Oshins <jakeo@xxxxxxxxxxxxx> > > 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@xxxxxxxxxxxxx> > --- > 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"? _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
