These were the commits applied in the test kernel posted in comment #13. The SHA1s are different because this is the tree used to build my test kernel.
e8aae57 Drivers: hv: vmbus: Fix a Host signaling bug
5d9beeb Drivers: hv: vmbus: Fix a siganlling host signalling issue
4763d20 Drivers: hv: vmbus: Export the vmbus_sendpacket_pagebuffer_ctl()
eab3ca4 Drivers: hv: vmbus: Suport an API to send packet with additional control
be7bca0 Drivers: hv: vmbus: Suport an API to send pagebuffers with additional control
6d43771 Drivers: hv: vmbus: Implement per-CPU mapping of relid to channel
b09952c Drivers: hv: Eliminate the channel spinlock in the callback path
So the changes to drivers/hv in Trusty -proposed are the same. I can build a Trusty -proposed test kernel without these 7 patches to see if they are the cause. If they are not, there may be a new regression in this -proposed kernel that we need to figure out.
These were the commits applied in the test kernel posted in comment #13. The SHA1s are different because this is the tree used to build my test kernel.
e8aae57 Drivers: hv: vmbus: Fix a Host signaling bug t_pagebuffer_ ctl()
5d9beeb Drivers: hv: vmbus: Fix a siganlling host signalling issue
4763d20 Drivers: hv: vmbus: Export the vmbus_sendpacke
eab3ca4 Drivers: hv: vmbus: Suport an API to send packet with additional control
be7bca0 Drivers: hv: vmbus: Suport an API to send pagebuffers with additional control
6d43771 Drivers: hv: vmbus: Implement per-CPU mapping of relid to channel
b09952c Drivers: hv: Eliminate the channel spinlock in the callback path
So the changes to drivers/hv in Trusty -proposed are the same. I can build a Trusty -proposed test kernel without these 7 patches to see if they are the cause. If they are not, there may be a new regression in this -proposed kernel that we need to figure out.