cachepc-linux

Fork of AMDESE/linux with modifications for CachePC side-channel attack
git clone https://git.sinitax.com/sinitax/cachepc-linux
Log | Files | Refs | README | LICENSE | sfeed.txt

sysfs-class-rapidio (2497B)


      1What:		/sys/class/rapidio_port
      2Description:
      3		On-chip RapidIO controllers and PCIe-to-RapidIO bridges
      4		(referenced as "Master Port" or "mport") are presented in sysfs
      5		as the special class of devices: "rapidio_port".
      6		The /sys/class/rapidio_port subdirectory contains individual
      7		subdirectories named as "rapidioN" where N = mport ID registered
      8		with RapidIO subsystem.
      9
     10		NOTE: An mport ID is not a RapidIO destination ID assigned to a
     11		given local mport device.
     12
     13What:		/sys/class/rapidio_port/rapidio<N>/sys_size
     14Date:		Apr, 2014
     15KernelVersion:	v3.15
     16Contact:	Matt Porter <mporter@kernel.crashing.org>,
     17		Alexandre Bounine <alexandre.bounine@idt.com>
     18Description:
     19		(RO) reports RapidIO common transport system size:
     20
     21		0 = small (8-bit destination ID, max. 256 devices),
     22
     23		1 = large (16-bit destination ID, max. 65536 devices).
     24
     25What:		/sys/class/rapidio_port/rapidio<N>/port_destid
     26Date:		Apr, 2014
     27KernelVersion:	v3.15
     28Contact:	Matt Porter <mporter@kernel.crashing.org>,
     29		Alexandre Bounine <alexandre.bounine@idt.com>
     30Description:
     31
     32(RO) reports RapidIO destination ID assigned to the given
     33RapidIO mport device. If value 0xFFFFFFFF is returned this means
     34that no valid destination ID have been assigned to the mport
     35(yet). Normally, before enumeration/discovery have been executed
     36only fabric enumerating mports have a valid destination ID
     37assigned to them using "hdid=..." rapidio module parameter.
     38
     39After enumeration or discovery was performed for a given mport device,
     40the corresponding subdirectory will also contain subdirectories for each
     41child RapidIO device connected to the mport.
     42
     43The example below shows mport device subdirectory with several child RapidIO
     44devices attached to it::
     45
     46    [rio@rapidio ~]$ ls /sys/class/rapidio_port/rapidio0/ -l
     47    total 0
     48    drwxr-xr-x 3 root root    0 Feb 11 15:10 00:e:0001
     49    drwxr-xr-x 3 root root    0 Feb 11 15:10 00:e:0004
     50    drwxr-xr-x 3 root root    0 Feb 11 15:10 00:e:0007
     51    drwxr-xr-x 3 root root    0 Feb 11 15:10 00:s:0002
     52    drwxr-xr-x 3 root root    0 Feb 11 15:10 00:s:0003
     53    drwxr-xr-x 3 root root    0 Feb 11 15:10 00:s:0005
     54    lrwxrwxrwx 1 root root    0 Feb 11 15:11 device -> ../../../0000:01:00.0
     55    -r--r--r-- 1 root root 4096 Feb 11 15:11 port_destid
     56    drwxr-xr-x 2 root root    0 Feb 11 15:11 power
     57    lrwxrwxrwx 1 root root    0 Feb 11 15:04 subsystem -> ../../../../../../class/rapidio_port
     58    -r--r--r-- 1 root root 4096 Feb 11 15:11 sys_size
     59    -rw-r--r-- 1 root root 4096 Feb 11 15:04 uevent