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>
(cherry picked from commit 9c6e64adf200d3bac0dd47d52cdbd3bd428384a5)

Orabug: 21886720
Signed-off-by: Jason Luo <zhangqing.luo@oracle.com>

diff --git a/drivers/hv/channel_mgmt.c b/drivers/hv/channel_mgmt.c
index 35bdc2eb831419f57b539aa08b32218a7d7abf7e..05d92295687db1bda7db426250a25ba2babae139 100644 (file)
--- a/drivers/hv/channel_mgmt.c
+++ b/drivers/hv/channel_mgmt.c
@@ -400,7 +400,7 @@ static void init_vp_index(struct vmbus_channel *channel, const uuid_le *type_gui
                 * channel, bind it to cpu 0.
                 */
                channel->target_cpu = 0;
-               channel->target_vp = 0;
+               channel->target_vp = hv_context.vp_index[0];
                return;
        }