1HWLOC-INFO(1) hwloc HWLOC-INFO(1)
2
6 hwloc-info - Show some information about some objects or about a topol‐
7 ogy or about support features
8
10 hwloc-info [ options ]... <object>...
11 hwloc-info [ options ]...
13 Note that hwloc(7) provides a detailed explanation of the hwloc system
15 and of valid <object> formats; it should be read before reading this
16 man page.
17
19 --objects
20 Report information specific objects. This is the default if
21 some objects are given on the command-line.
22 --topology
24 Report a summary of the topology instead of about some specific
25 objects. This is the default if no object is given on the com‐
26 mand-line.
27 --support
29 Report the features that are supported by hwloc on the topology.
30 The features are those available through the hwloc_topol‐
31 ogy_get_support() function. This is useful for verifying which
32 CPU or memory binding options are supported by the current hwloc
33 installation.
34 -i <file>, --input <file>
36 Read topology from XML file <file> (instead of discovering the
37 topology on the local machine). If <file> is "-", the standard
38 input is used. XML support must have been compiled in to hwloc
39 for this option to be usable.
40 -i <directory>, --input <directory>
42 Read topology from the chroot specified by <directory> (instead
43 of discovering the topology on the local machine). This option
44 is generally only available on Linux. The chroot was usually
45 created by gathering another machine topology with hwloc-gather-
46 topology.
47 -i <specification>, --input <specification>
49 Simulate a fake hierarchy (instead of discovering the topology
50 on the local machine). If <specification> is "node:2 pu:3", the
51 topology will contain two NUMA nodes with 3 processing units in
52 each of them. The <specification> string must end with a number
53 of PUs.
54 --if <format>, --input-format <format>
56 Enforce the input in the given format, among xml, fsroot and
57 synthetic.
58 -v --verbose
60 Include additional detail.
61 -s --silent
63 Reduce the amount of details to show. A single summary line per
64 object is displayed.
65 --ancestors
67 Display information about the object as well as about all its
68 ancestors up to the root of the topology.
69 --ancestor <type>
71 Only display the object ancestors that match the given type.
72 --children
74 Display information about the object children.
75 --descendants <type>
77 Display information about the object descendants that match the
78 given type.
79 -n When outputting object information, prefix each line with the
81 index of the considered object within the input. For instance,
82 if three cores were given in input, the output lines will be
83 prefixed with "0: ", "1: " or "2: ". If --ancestor is also
84 used, the prefix will be "X.Y: " where X is the index of the
85 considered object within the input, and Y is the parent index (0
86 for the object itself, increasing towards the root of the topol‐
87 ogy).
88 --whole-system
90 Do not consider administration limitations.
91 --restrict <cpuset>
93 Restrict the topology to the given cpuset.
94 --restrict binding
96 Restrict the topology to the current process binding. This
97 option requires the use of the actual current machine topology
98 (or any other topology with --thissystem or with HWLOC_THISSYS‐
99 TEM set to 1 in the environment).
100 --no-icaches
102 Do not show Instruction caches, only Data and Unified caches are
103 considered.
104 --no-io
106 Do not show any I/O device or bridge. By default, common
107 devices (GPUs, NICs, block devices, ...) and interesting bridges
108 are shown.
109 --no-bridges
111 Do not show any I/O bridge except hostbridges. By default, com‐
112 mon devices (GPUs, NICs, block devices, ...) and interesting
113 bridges are shown.
114 --whole-io
116 Show all I/O devices and bridges. By default, only common
117 devices (GPUs, NICs, block devices, ...) and interesting bridges
118 are shown.
119 --thissystem
121 Assume that the selected backend provides the topology for the
122 system on which we are running. This is useful when using
123 --restrict binding and loading a custom topology such as an XML
124 file.
125 --pid <pid>
127 Detect topology as seen by process <pid>, i.e. as if process
128 <pid> did the discovery itself. Note that this can for instance
129 change the set of allowed processors. Also show this process
130 current CPU binding by marking the corresponding PUs (in Green
131 in the graphical output, see the COLORS section below, or by
132 appending (binding) to the verbose text output). If 0 is given
133 as pid, the current binding for the lstopo process will be
134 shown.
135 -p --physical
137 Use OS/physical indexes instead of logical indexes for input.
138 -l --logical
140 Use logical indexes instead of physical/OS indexes for input
141 (default).
142 --version
144 Report version and exit.
145
147 hwloc-info displays information about the specified object. It is
148 intended to be used with tools such as grep for filtering certain
149 attribute lines. When no object is specified, or when --topology is
150 passed, hwloc-info prints a summary of the topology. When --support is
151 passed, hwloc-info lists the supported features for the topology.
152 Objects may be specified as location tuples, as explained in hwloc(7).
154 However hexadecimal bitmasks are not accepted since they may correspond
155 to multiple objects.
156 NOTE: It is highly recommended that you read the hwloc(7) overview page
158 before reading this man page. Most of the concepts described in
159 hwloc(7) directly apply to the hwloc-calc utility.
160
162 To display information about each package:
163 $ hwloc-info package:all
165 Package L#0
166 logical index = 0
167 ...
168 To display information about the core whose physical index is 2:
170 $ utils/hwloc-info -p core:2
172 Core L#1
173 logical index = 1
174 os index = 2
175 ...
176
178 hwloc(7), lstopo(1), hwloc-calc(1), hwloc-bind(1), hwloc-ps(1), hwloc-
179 gather-topology(1)
1801.11.9 Jan 18, 2018 HWLOC-INFO(1)