Drivers: hv: vmbus: Use the vp_index map even for channels bound to CPU 0
authorK. Y. Srinivasan <kys@microsoft.com>
Sun, 31 May 2015 06:37:47 +0000 (23:37 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 1 Jun 2015 01:56:31 +0000 (10:56 +0900)
commit9c6e64adf200d3bac0dd47d52cdbd3bd428384a5
treebcfd472eacb5f52169cbb15d3af3883cb0f7897a
parent0dcacd768ea6fc5bdd7302d43d430b92e047c134
Drivers: hv: vmbus: Use the vp_index map even for channels bound to CPU 0

Map target_cpu to target_vcpu using the mapping table.
We should use the mapping table to transform guest CPU ID to VP Index
as is done for the non-performance critical channels.
While the value CPU 0 is special and will
map to VP index 0, it is good to be consistent.

Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/hv/channel_mgmt.c