diff options
author | 2017-12-08 17:42:10 +0800 | |
---|---|---|
committer | 2018-01-10 23:24:54 -0500 | |
commit | 1689c9367bfaf4b5ff3973f26f5acbff16b63bfb (patch) | |
tree | bc4d8fa9d56dfcf9889f32ca03c6fd0ab8c2a65a /tools/perf/scripts/python/export-to-postgresql.py | |
parent | scsi: libsas: direct call probe and destruct (diff) | |
download | wireguard-linux-1689c9367bfaf4b5ff3973f26f5acbff16b63bfb.tar.xz wireguard-linux-1689c9367bfaf4b5ff3973f26f5acbff16b63bfb.zip |
scsi: libsas: notify event PORTE_BROADCAST_RCVD in sas_enable_revalidation()
There are two places queuing the disco event DISCE_REVALIDATE_DOMAIN.
One is in sas_porte_broadcast_rcvd() and uses sas_chain_event() to queue
the event. The other is in sas_enable_revalidation() and uses
sas_queue_event() to queue the event. We have diffrent work queues for
event and discovery now, so the DISCE_REVALIDATE_DOMAIN event may be
processed in both event queue and discovery queue.
Now since we do synchronous event handling, we cannot do it in discovery
queue, so have to trigger a fake broadcast event to re-trigger the
revalidation from event queue.
Signed-off-by: Jason Yan <yanaijie@huawei.com>
CC: John Garry <john.garry@huawei.com>
CC: Johannes Thumshirn <jthumshirn@suse.de>
CC: Ewan Milne <emilne@redhat.com>
CC: Christoph Hellwig <hch@lst.de>
CC: Tomas Henzl <thenzl@redhat.com>
CC: Dan Williams <dan.j.williams@intel.com>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions