mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-23 06:05:27 +00:00
bb2adfe934
Similar to scsi_host and fc_host, there is a relation between a scsi_target and its transport specific fc_remote_port. Let's expose this relation and relevant information behind it. An example for a virsh nodedev-dumpxml: virsh # nodedev-dumpxml scsi_target0_0_0 <device> <name>scsi_target0_0_0</name> <path>/sys/devices/[...]/host0/rport-0:0-0/target0:0:0</path> <parent>scsi_host0</parent> <capability type='scsi_target'> <target>target0:0:0</target> <capability type='fc_remote_port'> <rport>rport-0:0-0</rport> <wwpn>0x9d73bc45f0e21a86</wwpn> </capability> </capability> </device> Reviewed-by: Boris Fiuczynski <fiuczy@linux.vnet.ibm.com> Signed-off-by: Bjoern Walk <bwalk@linux.vnet.ibm.com> |
||
---|---|---|
.. | ||
ccw_0_0_10000-invalid.xml | ||
ccw_0_0_ffff.xml | ||
computer.xml | ||
drm_renderD129.xml | ||
DVD_GCC_4247N.xml | ||
DVD_with_media.xml | ||
mdev_3627463d_b7f0_4fea_b468_f1da537d301b.xml | ||
net_00_13_02_b9_f9_d3.xml | ||
net_00_15_58_2f_e9_55.xml | ||
pci_0000_00_1c_0_header_type.xml | ||
pci_0000_00_02_0_header_type.xml | ||
pci_0000_02_10_7_mdev_types.xml | ||
pci_0000_02_10_7_sriov_pf_vfs_all_header_type.xml | ||
pci_0000_02_10_7_sriov_pf_vfs_all.xml | ||
pci_0000_02_10_7_sriov_vfs.xml | ||
pci_0000_02_10_7_sriov_zero_vfs_max_count.xml | ||
pci_0000_02_10_7_sriov.xml | ||
pci_1002_71c4.xml | ||
pci_8086_0c0c_snd_hda_intel.xml | ||
pci_8086_10c9_sriov_pf.xml | ||
pci_8086_27c5_scsi_host_0_unique_id.xml | ||
pci_8086_27c5_scsi_host_0.xml | ||
pci_8086_27c5_scsi_host_scsi_device_lun0.xml | ||
pci_8086_27c5_scsi_host_scsi_host.xml | ||
pci_8086_27c5_scsi_host.xml | ||
pci_8086_4238_pcie_wireless.xml | ||
pci_82579LM_network_adapter.xml | ||
scsi_target0_0_0.xml | ||
scsi_target1_0_0.xml | ||
storage_serial_3600c0ff000d7a2a5d463ff4902000000.xml | ||
storage_serial_SATA_HTS721010G9SA00_MPCZ12Y0GNGWSE.xml | ||
usb_device_1d6b_1_0000_00_1d_0_if0.xml | ||
usb_device_1d6b_1_0000_00_1d_0.xml |