RE: [PATCH v3 12/12] Drivers: hv: vmbus: Resume after fixing up old primary channels

2019-08-30 Thread Dexuan Cui
> From: Dexuan Cui > Sent: Friday, August 30, 2019 9:37 PM > > Is the intent to proceed and use the new offer? > Yes, since this is not an error. > > I'll add a comment before the "Mismatched offer from the host" for this. Hi Michael, I'm going to make the below change in v4. ---

RE: [PATCH v3 12/12] Drivers: hv: vmbus: Resume after fixing up old primary channels

2019-08-30 Thread Dexuan Cui
> From: Michael Kelley > Sent: Friday, August 23, 2019 1:25 PM > > From: Dexuan Cui Sent: Monday, August 19, 2019 6:52 PM > > @@ -890,6 +937,11 @@ static void vmbus_onoffer(struct > > vmbus_channel_message_header *hdr) > > false); > >

RE: [PATCH v3 12/12] Drivers: hv: vmbus: Resume after fixing up old primary channels

2019-08-23 Thread Michael Kelley
From: Dexuan Cui Sent: Monday, August 19, 2019 6:52 PM > > When the host re-offers the primary channels upon resume, the host only > guarantees the Instance GUID doesn't change, so vmbus_bus_suspend() > should invalidate channel->offermsg.child_relid and figure out the > number of primary

[PATCH v3 12/12] Drivers: hv: vmbus: Resume after fixing up old primary channels

2019-08-19 Thread Dexuan Cui
When the host re-offers the primary channels upon resume, the host only guarantees the Instance GUID doesn't change, so vmbus_bus_suspend() should invalidate channel->offermsg.child_relid and figure out the number of primary channels that need to be fixed up upon resume. Upon resume,