RE: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-22 Thread KY Srinivasan
ft.com>; Alex Ng (LIS) <ale...@microsoft.com>; > Radim Krcmar <rkrc...@redhat.com>; Cathy Avery <cav...@redhat.com> > Subject: Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios > > KY Srinivasan <k...@microsoft.com> writes: > > >>

RE: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-22 Thread KY Srinivasan
o: KY Srinivasan > >> Cc: de...@linuxdriverproject.org; linux-kernel@vger.kernel.org; Haiyang > >> Zhang ; Alex Ng (LIS) > ; > >> Radim Krcmar ; Cathy Avery > > >> Subject: Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios > >> > &

Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-22 Thread Vitaly Kuznetsov
x-kernel@vger.kernel.org; Haiyang >> Zhang <haiya...@microsoft.com>; Alex Ng (LIS) <ale...@microsoft.com>; >> Radim Krcmar <rkrc...@redhat.com>; Cathy Avery <cav...@redhat.com> >> Subject: Re: [PATCH] Drivers: hv: vmbus: handle various crash scenari

Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-22 Thread Vitaly Kuznetsov
x Ng (LIS) ; >> Radim Krcmar ; Cathy Avery >> Subject: Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios >> >> KY Srinivasan writes: >> >> >> -Original Message- >> >> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]

Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-22 Thread Vitaly Kuznetsov
x-kernel@vger.kernel.org; Haiyang >> Zhang <haiya...@microsoft.com>; Alex Ng (LIS) <ale...@microsoft.com>; >> Radim Krcmar <rkrc...@redhat.com>; Cathy Avery <cav...@redhat.com> >> Subject: Re: [PATCH] Drivers: hv: vmbus: handle various crash scenari

Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-22 Thread Vitaly Kuznetsov
x Ng (LIS) ; >> Radim Krcmar ; Cathy Avery >> Subject: Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios >> >> KY Srinivasan writes: >> >> >> -Original Message- >> >> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]

RE: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-21 Thread KY Srinivasan
ft.com>; Alex Ng (LIS) <ale...@microsoft.com>; > Radim Krcmar <rkrc...@redhat.com>; Cathy Avery <cav...@redhat.com> > Subject: Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios > > KY Srinivasan <k...@microsoft.com> writes: > > >>

RE: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-21 Thread KY Srinivasan
e...@linuxdriverproject.org > >> Cc: linux-kernel@vger.kernel.org; KY Srinivasan ; > >> Haiyang Zhang ; Alex Ng (LIS) > >> ; Radim Krcmar ; Cathy > >> Avery > >> Subject: [PATCH] Drivers: hv: vmbus: handle various crash scenarios > >> > >&

Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-21 Thread Vitaly Kuznetsov
t;k...@microsoft.com>; >> Haiyang Zhang <haiya...@microsoft.com>; Alex Ng (LIS) >> <ale...@microsoft.com>; Radim Krcmar <rkrc...@redhat.com>; Cathy >> Avery <cav...@redhat.com> >> Subject: [PATCH] Drivers: hv: vmbus: handle various crash scenarios >

Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-21 Thread Vitaly Kuznetsov
x Ng (LIS) >> ; Radim Krcmar ; Cathy >> Avery >> Subject: [PATCH] Drivers: hv: vmbus: handle various crash scenarios >> >> Kdump keeps biting. Turns out CHANNELMSG_UNLOAD_RESPONSE is always >> delivered to CPU0 regardless of what CPU we're sending >> C

Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-19 Thread Vitaly Kuznetsov
Radim Krcmar writes: > 2016-03-18 13:33+0100, Vitaly Kuznetsov: >> Kdump keeps biting. Turns out CHANNELMSG_UNLOAD_RESPONSE is always >> delivered to CPU0 regardless of what CPU we're sending CHANNELMSG_UNLOAD >> from. vmbus_wait_for_unload() doesn't account for the fact that

Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-19 Thread Vitaly Kuznetsov
Radim Krcmar writes: > 2016-03-18 13:33+0100, Vitaly Kuznetsov: >> Kdump keeps biting. Turns out CHANNELMSG_UNLOAD_RESPONSE is always >> delivered to CPU0 regardless of what CPU we're sending CHANNELMSG_UNLOAD >> from. vmbus_wait_for_unload() doesn't account for the fact that in case >> we're

RE: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-19 Thread KY Srinivasan
.com>; Alex Ng (LIS) > <ale...@microsoft.com>; Radim Krcmar <rkrc...@redhat.com>; Cathy > Avery <cav...@redhat.com> > Subject: [PATCH] Drivers: hv: vmbus: handle various crash scenarios > > Kdump keeps biting. Turns out CHANNELMSG_UNLOAD_RESPONSE is

RE: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-19 Thread KY Srinivasan
Avery > Subject: [PATCH] Drivers: hv: vmbus: handle various crash scenarios > > Kdump keeps biting. Turns out CHANNELMSG_UNLOAD_RESPONSE is always > delivered to CPU0 regardless of what CPU we're sending > CHANNELMSG_UNLOAD > from. vmbus_wait_for_unload() doesn't account for the

Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-18 Thread Radim Krcmar
2016-03-18 16:53+0100, Vitaly Kuznetsov: > Radim Krcmar writes: >> 2016-03-18 13:33+0100, Vitaly Kuznetsov: >>> @@ -530,9 +542,17 @@ static void vmbus_wait_for_unload(void) >> >> (I'm not a huge fan of the unloaded variable; what about remembering the >> header/msgtype here

Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-18 Thread Radim Krcmar
2016-03-18 16:53+0100, Vitaly Kuznetsov: > Radim Krcmar writes: >> 2016-03-18 13:33+0100, Vitaly Kuznetsov: >>> @@ -530,9 +542,17 @@ static void vmbus_wait_for_unload(void) >> >> (I'm not a huge fan of the unloaded variable; what about remembering the >> header/msgtype here ... >> >>>

[PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-18 Thread Vitaly Kuznetsov
Kdump keeps biting. Turns out CHANNELMSG_UNLOAD_RESPONSE is always delivered to CPU0 regardless of what CPU we're sending CHANNELMSG_UNLOAD from. vmbus_wait_for_unload() doesn't account for the fact that in case we're crashing on some other CPU and CPU0 is still alive and operational

[PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-18 Thread Vitaly Kuznetsov
Kdump keeps biting. Turns out CHANNELMSG_UNLOAD_RESPONSE is always delivered to CPU0 regardless of what CPU we're sending CHANNELMSG_UNLOAD from. vmbus_wait_for_unload() doesn't account for the fact that in case we're crashing on some other CPU and CPU0 is still alive and operational

Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-18 Thread Radim Krcmar
2016-03-18 13:33+0100, Vitaly Kuznetsov: > Kdump keeps biting. Turns out CHANNELMSG_UNLOAD_RESPONSE is always > delivered to CPU0 regardless of what CPU we're sending CHANNELMSG_UNLOAD > from. vmbus_wait_for_unload() doesn't account for the fact that in case > we're crashing on some other CPU and

Re: [PATCH] Drivers: hv: vmbus: handle various crash scenarios

2016-03-18 Thread Radim Krcmar
2016-03-18 13:33+0100, Vitaly Kuznetsov: > Kdump keeps biting. Turns out CHANNELMSG_UNLOAD_RESPONSE is always > delivered to CPU0 regardless of what CPU we're sending CHANNELMSG_UNLOAD > from. vmbus_wait_for_unload() doesn't account for the fact that in case > we're crashing on some other CPU and