1948628a54
Using the same message slot as the other types of the messages has the side effect that the event timer message could be deferred to the swi threads to run (lacking of trapframe and the original code didn't even handle that, so the event timer was actually broken). As of this commit we use an independent message slot for event timer, so that we could handle all of event timer messages in the interrupt handler directly. Note, the message slot for event timer is still bind to the same interrupt vector as the other types of messages. Submitted by: Jun Su <junsu microsoft com> Reviewed by: sephe Discussed with: Jun Su <junsu microsoft com>, Dexuan Cui <decui microsoft com> MFC after: 1 week Sponsored by: Microsoft OSTC Differential Revision: https://reviews.freebsd.org/D5696 |
||
---|---|---|
.. | ||
hv_channel_mgmt.c | ||
hv_channel.c | ||
hv_connection.c | ||
hv_et.c | ||
hv_hv.c | ||
hv_ring_buffer.c | ||
hv_vmbus_drv_freebsd.c | ||
hv_vmbus_priv.h |