File: sysfs-devices-mapping

package info (click to toggle)
linux 6.1.8-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,488,076 kB
  • sloc: ansic: 23,401,844; asm: 266,744; sh: 108,976; makefile: 49,705; python: 36,927; perl: 36,810; cpp: 6,044; yacc: 4,904; lex: 2,722; awk: 1,440; ruby: 25; sed: 5
file content (34 lines) | stat: -rw-r--r-- 1,460 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
What:           /sys/devices/uncore_iio_x/dieX
Date:           February 2020
Contact:        Roman Sudarikov <roman.sudarikov@linux.intel.com>
Description:
                Each IIO stack (PCIe root port) has its own IIO PMON block, so
                each dieX file (where X is die number) holds "Segment:Root Bus"
                for PCIe root port, which can be monitored by that IIO PMON
                block.
                For example, on 4-die Xeon platform with up to 6 IIO stacks per
                die and, therefore, 6 IIO PMON blocks per die, the mapping of
                IIO PMON block 0 exposes as the following::

		    $ ls /sys/devices/uncore_iio_0/die*
		    -r--r--r-- /sys/devices/uncore_iio_0/die0
		    -r--r--r-- /sys/devices/uncore_iio_0/die1
		    -r--r--r-- /sys/devices/uncore_iio_0/die2
		    -r--r--r-- /sys/devices/uncore_iio_0/die3

		    $ tail /sys/devices/uncore_iio_0/die*
		    ==> /sys/devices/uncore_iio_0/die0 <==
		    0000:00
		    ==> /sys/devices/uncore_iio_0/die1 <==
		    0000:40
		    ==> /sys/devices/uncore_iio_0/die2 <==
		    0000:80
		    ==> /sys/devices/uncore_iio_0/die3 <==
		    0000:c0

                Which means::

		    IIO PMU 0 on die 0 belongs to PCI RP on bus 0x00, domain 0x0000
		    IIO PMU 0 on die 1 belongs to PCI RP on bus 0x40, domain 0x0000
		    IIO PMU 0 on die 2 belongs to PCI RP on bus 0x80, domain 0x0000
		    IIO PMU 0 on die 3 belongs to PCI RP on bus 0xc0, domain 0x0000