diff options
author | 2016-02-26 15:13:15 -0800 | |
---|---|---|
committer | 2016-03-01 16:57:20 -0800 | |
commit | 7be3e169444d2c625f15a0b6639252b98d1f226a (patch) | |
tree | c26bf9fe6a7f9ccbd28fa41177cb35533827569c /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | misc: at24: replace memory_accessor with nvmem_device_read (diff) | |
download | linux-dev-7be3e169444d2c625f15a0b6639252b98d1f226a.tar.xz linux-dev-7be3e169444d2c625f15a0b6639252b98d1f226a.zip |
Drivers: hv: vmbus: don't loose HVMSG_TIMER_EXPIRED messages
We must handle HVMSG_TIMER_EXPIRED messages in the interrupt context
and we offload all the rest to vmbus_on_msg_dpc() tasklet. This functions
loops to see if there are new messages pending. In case we'll ever see
HVMSG_TIMER_EXPIRED message there we're going to lose it as we can't
handle it from there. Avoid looping in vmbus_on_msg_dpc(), we're OK
with handling one message per interrupt.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Reviewed-by: Radim Kr.má<rkrcmar@redhat.com>
Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions