diff options
| author | Sreekanth Reddy <sreekanth.reddy@broadcom.com> | 2020-10-27 18:38:40 +0530 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2020-11-04 18:42:24 -0500 |
| commit | 6df6be9168f50369ba843f2a12fe8537effbaff1 (patch) | |
| tree | e2cd1e0a892b1960d46383b0c5786b03ab4e2626 /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | c71ccf93c00c0cef062c2371e9a614526fee9adb (diff) | |
| download | linux-6df6be9168f50369ba843f2a12fe8537effbaff1.tar.gz linux-6df6be9168f50369ba843f2a12fe8537effbaff1.zip | |
scsi: mpt3sas: Get sas_device objects using device's rphy
In the following scsi_host_template and sas_function_template callback
functions the driver does not have PhysicalPort number information to
retrieve the sas_device object using SAS Address & PhysicalPort number. In
these callback functions the device's rphy object is used to retrieve
sas_device object for the device.
.target_alloc,
.get_enclosure_identifier
.get_bay_identifier
When a rphy (of type sas_rphy) object is allocated then its address is
saved in corresponding sas_device object's rphy field. In
__mpt3sas_get_sdev_by_rphy(), the driver loops over all the sas_device
objects from sas_device_list list to retrieve the sas_device objects whose
rphy matches the provided rphy.
Link: https://lore.kernel.org/r/20201027130847.9962-8-sreekanth.reddy@broadcom.com
Signed-off-by: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions