On Mon, Sep 21, Vitaly Kuznetsov wrote: > I'd like to see a trace from the hang, it is not obvious to me how it > happened and what caused it. (or if you have such hang scenario in your > head, can you please reveal it?)
There is no trace. I think fcopy_respond_to_host notifies the host, which in turn triggers an interrupt right away which is processed while fcopy_on_msg is executing somewhere between the return from fcopy_respond_to_host and the call into hv_fcopy_onchannelcallback. > AFAICS barriers you introduced don't give you guarantees in an SMP > environment. Happens to work on x86, and for this purpose. I will see how to add locking around access to state and context. Olaf -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
