diff options
author | 2016-11-10 07:18:47 +0000 | |
---|---|---|
committer | 2016-11-16 16:45:32 -0600 | |
commit | 17978524a636d007e6b929304ae3eb5ea0371019 (patch) | |
tree | 84f473f1e2f106f30ff7149b52066db49a8368ca /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | PCI: hv: Use the correct buffer size in new_pcichild_device() (diff) | |
download | linux-dev-17978524a636d007e6b929304ae3eb5ea0371019.tar.xz linux-dev-17978524a636d007e6b929304ae3eb5ea0371019.zip |
PCI: hv: Fix hv_pci_remove() for hot-remove
1. We don't really need such a big on-stack buffer when sending the
teardown_packet: vmbus_sendpacket() here only uses sizeof(struct
pci_message).
2. In the hot-remove case (PCI_EJECT), after we send PCI_EJECTION_COMPLETE
to the host, the host will send a RESCIND_CHANNEL message to us and the
host won't access the per-channel ringbuffer any longer, so we needn't send
PCI_RESOURCES_RELEASED/PCI_BUS_D0EXIT to the host, and we shouldn't expect
the host's completion message of PCI_BUS_D0EXIT, which will never come.
3. We should send PCI_BUS_D0EXIT after hv_send_resources_released().
Signed-off-by: Dexuan Cui <decui@microsoft.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Jake Oshins <jakeo@microsoft.com>
Acked-by: K. Y. Srinivasan <kys@microsoft.com>
CC: Haiyang Zhang <haiyangz@microsoft.com>
CC: Vitaly Kuznetsov <vkuznets@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions