1LSTOPO(1) hwloc LSTOPO(1)
2
6 lstopo, lstopo-no-graphics, hwloc-ls - Show the topology of the system
7
9 lstopo [ options ]... [ filename ]
10 lstopo-no-graphics [ options ]... [ filename ]
12 hwloc-ls [ options ]... [ filename ]
14 Note that hwloc(7) provides a detailed explanation of the hwloc system;
16 it should be read before reading this man page
17
19 --of <format>, --output-format <format>
20 Enforce the output in the given format. See the OUTPUT FORMATS
21 section below.
22 -i <file>, --input <file>
24 Read topology from XML file <file> (instead of discovering the
25 topology on the local machine). If <file> is "-", the standard
26 input is used. XML support must have been compiled in to hwloc
27 for this option to be usable.
28 -i <directory>, --input <directory>
30 Read topology from <directory> instead of discovering the topol‐
31 ogy of the local machine. On Linux, the directory may contain
32 the topology files gathered from another machine topology with
33 hwloc-gather-topology. On x86, the directory may contain a
34 cpuid dump gathered with hwloc-gather-cpuid.
35 -i <specification>, --input <specification>
37 Simulate a fake hierarchy (instead of discovering the topology
38 on the local machine). If <specification> is "node:2 pu:3", the
39 topology will contain two NUMA nodes with 3 processing units in
40 each of them. The <specification> string must end with a number
41 of PUs.
42 --if <format>, --input-format <format>
44 Enforce the input in the given format, among xml, fsroot, cpuid
45 and synthetic.
46 --export-xml-flags <flags>
48 Enforce flags when exporting to the XML format. Flags may be
49 given as numeric values or as a comma-separated list of flag
50 names that are passed to hwloc_topology_export_xml(). Those
51 names may be substrings of actual flag names as long as a single
52 one matches. A value of 1 (or v1) reverts to the format of
53 hwloc v1.x. The default is 0 (or none).
54 --export-synthetic-flags <flags>
56 Enforce flags when exporting to the synthetic format. Flags may
57 be given as numeric values or as a comma-separated list of flag
58 names that are passed to hwloc_topology_export_synthetic().
59 Those names may be substrings of actual flag names as long as a
60 single one matches. A value of 2 (or no_attr) reverts to the
61 format of hwloc v1.9. A value of 3 (or no_ext,no_attr) reverts
62 to the original minimalistic format (before v1.9). The default
63 is 0 (or none).
64 -v --verbose
66 Include additional detail. The hwloc-info tool may be used to
67 display even more information about specific objects.
68 -s --silent
70 Reduce the amount of details to show.
71 --distances
73 Only display distance matrices.
74 --memattrs
76 Only display memory attributes. All of them are displayed
77 (while the default textual output selects memory attribute de‐
78 tails depending on the verbosity level).
79 --cpukinds
81 Only display CPU kinds.
82 -f --force
84 If the destination file already exists, overwrite it.
85 -l --logical
87 Display hwloc logical indexes of all objects, with prefix "L#".
88 By default, both logical and physical/OS indexes are displayed
89 for PUs and NUMA nodes, logical only for cores, dies and pack‐
90 ages, and no index for other types.
91 -p --physical
93 Display OS/physical indexes of all objects, with prefix "P#".
94 By default, both logical and physical/OS indexes are displayed
95 for PUs and NUMA nodes, logical only for cores, dies and pack‐
96 ages, and no index for other types.
97 -c --cpuset
99 Display the cpuset of each object.
100 -C --cpuset-only
102 Only display the cpuset of each object; do not display anything
103 else about the object.
104 --taskset
106 Show CPU set strings in the format recognized by the taskset
107 command-line program instead of hwloc-specific CPU set string
108 format. This option should be combined with --cpuset or
109 --cpuset-only, otherwise it will imply --cpuset.
110 --only <type>
112 Only show objects of the given type in the textual output.
113 --filter <type>:<kind>, --filter <type>
115 Filter objects of type <type>, or of any type if <type> is
116 "all". "io", "cache" and "icache" are also supported.
117 <kind> specifies the filtering behavior. If "none" or not spec‐
119 ified, all objects of the given type are removed. If "all", all
120 objects are kept as usual. If "structure", objects are kept
121 when they bring structure to the topology. If "important" (only
122 applicable to I/O), only important objects are kept. See
123 hwloc_topology_set_type_filter() for more details.
124 hwloc supports filtering any type except PUs and NUMA nodes.
126 lstopo also offers PU and NUMA node filtering by hiding them in
127 the graphical and textual outputs, but any object included in
128 them (for instance Misc) will be hidden as well. Note that PUs
129 and NUMA nodes may not be ignored in the XML output. Note also
130 that the top-level object type cannot be ignored (usually Ma‐
131 chine or System).
132 --ignore <type>
134 This is the old way to specify --filter <type>:none.
135 --no-smt
137 Ignore PUs. This is identical to --filter PU:none.
138 --no-caches
140 Do not show caches. This is identical to --filter cache:none.
141 --no-useless-caches
143 This is identical to --filter cache:structure.
144 --no-icaches
146 This is identical to --filter icache:none.
147 --disallowed
149 Include objects disallowed by administrative limitations.
150 --allow <all|local|0xff|nodeset=0xf0>
152 Include objects disallowed by administrative limitations (im‐
153 plies --disallowed) and also change the set of allowed ones.
154 If local is given, only objects available to the current process
156 are allowed (default behavior when loading from the native oper‐
157 ating system backend). It may be useful if the topology was
158 created by another process (with different administrative re‐
159 strictions such as Linux Cgroups) and loaded here loaded from
160 XML or synthetic. This case implies --thissystem.
161 If all, all objects are allowed.
163 If a bitmap is given as a hexadecimal string, it is used as the
165 set of allowed PUs.
166 If a bitmap is given after prefix nodeset=, it is the set of al‐
168 lowed NUMA nodes.
169 --flags <flags>
171 Enforce topology flags. Flags may be given as numeric values or
172 as a comma-separated list of flag names that are passed to
173 hwloc_topology_set_flags(). Those names may be substrings of
174 actual flag names as long as a single one matches, for instance
175 disallowed,thissystem_allowed. The default is 8 (or import).
176 --merge
178 Do not show levels that do not have a hierarchical impact. This
179 sets HWLOC_TYPE_FILTER_KEEP_STRUCTURE for all object types.
180 This is identical to --filter all:structure.
181 --no-factorize --no-factorize=<type>
183 Never factorize identical objects in the graphical output.
184 If an object type is given, only factorizing of these objects is
186 disabled. This only applies to normal CPU-side objects, it is
187 independent from PCI collapsing.
188 --factorize --factorize=[<type>,]<N>[,<L>[,<F>]
190 Factorize identical children in the graphical output (enabled by
191 default).
192 If <N> is specified (4 by default), factorizing only occurs when
194 there are strictly more than N identical children. If <L> and
195 <F> are specified, they set the numbers of first and last chil‐
196 dren to keep after factorizing.
197 If an object type is given, only factorizing of these objects is
199 configured. This only applies to normal CPU-side object, it is
200 independent from PCI collapsing.
201 --no-collapse
203 Do not collapse identical PCI devices. By default, identical
204 sibling PCI devices (such as many virtual functions inside a
205 single physical device) are collapsed.
206 --no-cpukinds
208 Do not show different kinds of CPUs in the graphical output. By
209 default, when supported, different types of lines, thickness and
210 bold font may be used to display PU boxes of different kinds.
211 --restrict <cpuset>
213 Restrict the topology to the given cpuset.
214 --restrict nodeset=<nodeset>
216 Restrict the topology to the given nodeset, unless --restrict-
217 flags specifies something different.
218 --restrict binding
220 Restrict the topology to the current process binding. This op‐
221 tion requires the use of the actual current machine topology (or
222 any other topology with --thissystem or with HWLOC_THISSYSTEM
223 set to 1 in the environment).
224 --restrict-flags <flags>
226 Enforce flags when restricting the topology. Flags may be given
227 as numeric values or as a comma-separated list of flag names
228 that are passed to hwloc_topology_restrict(). Those names may
229 be substrings of actual flag names as long as a single one
230 matches, for instance bynodeset,memless. The default is 0 (or
231 none).
232 --no-io
234 Do not show any I/O device or bridge. This is identical to
235 --filter io:none. By default, common devices (GPUs, NICs, block
236 devices, ...) and interesting bridges/switches are shown.
237 --no-bridges
239 Do not show any I/O bridge except hostbridges. This is identi‐
240 cal to --filter bridge:none. By default, common devices (GPUs,
241 NICs, block devices, ...) and interesting bridges/switches are
242 shown.
243 --whole-io
245 Show all I/O devices and bridges. This is identical to --filter
246 io:all. By default, only common devices (GPUs, NICs, block de‐
247 vices, ...) and interesting bridges/switches are shown.
248 --thissystem
250 Assume that the selected backend provides the topology for the
251 system on which we are running. This is useful when loading a
252 custom topology such as an XML file and using --restrict binding
253 or --allow all.
254 --pid <pid>
256 Detect topology as seen by process <pid>, i.e. as if process
257 <pid> did the discovery itself. Note that this can for instance
258 change the set of allowed processors. Also show this process
259 current CPU and Memory binding by marking the corresponding PUs
260 and NUMA nodes (in Green in the graphical output, see the COLORS
261 section below, or by appending (binding) to the verbose text
262 output). If 0 is given as pid, the current binding for the
263 lstopo process will be shown.
264 --ps --top
266 Show existing processes as misc objects in the output. To avoid
267 uselessly cluttering the output, only processes that are re‐
268 stricted to some part of the machine are shown. On Linux, ker‐
269 nel threads are not shown. If many processes appear, the output
270 may become hard to read anyway, making the hwloc-ps program more
271 practical.
272 --children-order <order>
274 Change the order of the different kinds of children with respect
275 to their parent in the graphical output.
276 The default order is memoryabove: it displays memory children
278 above other children (and above the parent if it is a cache).
279 PUs are therefore below their local NUMA nodes, like hwloc 1.x
280 did.
281 If the order is changed to plain, lstopo displays the topology
283 in a basic manner that strictly matches the actual tree: memory
284 children are listed below their parent just like any other
285 child. PUs are therefore on the side of their local NUMA nodes,
286 below a common ancestor.
287 See also the GRAPHICAL OUTPUT section below.
289 --fontsize <size>
291 Set the size of text font in the graphical output.
292 The default is 10.
294 Boxes are scaled according to the text size. The
296 LSTOPO_TEXT_XSCALE environment variable may be used to further
297 scale the width of boxes (its default value is 1.0).
298 The --fontsize option is ignored in the ASCII backend.
300 --gridsize <size>
302 Set the margin between elements in the graphical output.
303 The default is 7. It was 10 prior to hwloc 2.1.
305 This option is ignored in the ASCII backend.
307 --linespacing <size>
309 Set the spacing between lines of text in the graphical output.
310 The default is 4.
312 The option was included in --gridsize prior to hwloc 2.1 (and
314 its default was 10).
315 This option is ignored in the ASCII backend.
317 --thickness <size>
319 Set the thickness of lines and boxes in the graphical output.
320 The default is 1.
322 This option is ignored in the ASCII backend.
324 --horiz, --horiz=<type1,...>
326 Force a horizontal graphical layout instead of nearly 4/3 ratio
327 in the graphical output. If a comma-separated list of object
328 types is given, the layout only applies to the corresponding
329 container objects. Ignored for bridges since their children are
330 always vertically aligned.
331 --vert, --vert=<type1,...>
333 Force a vertical graphical layout instead of nearly 4/3 ratio in
334 the graphical output. If a comma-separated list of object types
335 is given, the layout only applies to the corresponding container
336 objects.
337 --rect, --rect=<type1,...>
339 Force a rectangular graphical layout with nearly 4/3 ratio in
340 the graphical output. If a comma-separated list of object types
341 is given, the layout only applies to the corresponding container
342 objects. Ignored for bridges since their children are always
343 vertically aligned.
344 --no-text, --no-text=<type1,...>
346 Do not display any text in boxes in the graphical output. If a
347 comma-separated list of object types is given, text is disabled
348 for the corresponding objects. This is mostly useful for remov‐
349 ing text from Group objects.
350 --text, --text=<type1,...>
352 Display text in boxes in the graphical output (default). If a
353 comma-separated list of object types is given, text is reenabled
354 for the corresponding objects (if it was previously disabled
355 with --no-text).
356 --no-index, --no-index=<type1,...>
358 Do not show object indexes in the graphical output. If a comma-
359 separated list of object types is given, indexes are disabled
360 for the corresponding objects.
361 --index, --index=<type1,...>
363 Show object indexes in the graphical output (default). If a
364 comma-separated list of object types is given, indexes are reen‐
365 abled for the corresponding objects (if they were previously
366 disabled with --no-index).
367 --no-attrs, --no-attrs=<type1,...>
369 Do not show object attributes (such as memory size, cache size,
370 PCI bus ID, PCI link speed, etc.) in the graphical output. If
371 a comma-separated list of object types is given, attributes are
372 disabled for the corresponding objects.
373 --attrs, --attrs=<type1,...>
375 Show object attributes (such as memory size, cache size, PCI bus
376 ID, PCI link speed, etc.) in the graphical output (default).
377 If a comma-separated list of object types is given, attributes
378 are reenabled for the corresponding objects (if they were previ‐
379 ously disabled with --no-attrs).
380 --no-legend
382 Remove all text legend lines at the bottom of the graphical out‐
383 put.
384 --no-default-legend
386 Remove default text legend lines at the bottom of the graphical
387 output. User-added legend lines with --append-legend or the
388 "lstopoLegend" info are still displayed if any.
389 --append-legend <line>
391 Append the line of text to the bottom of the legend in the
392 graphical output. If adding multiple lines, each line should be
393 given separately by passing this option multiple times. Addi‐
394 tional legend lines may also be specified inside the topology
395 using the "lstopoLegend" info attributes on the topology root
396 object.
397 --binding-color none
399 Do not colorize PUs and NUMA nodes according to the binding in
400 the graphical output.
401 --disallowed-color none
403 Do not colorize disallowed PUs and NUMA nodes in the graphical
404 output.
405 --top-color <none|#xxyyzz>
407 Do not colorize task objects in the graphical output when --top
408 is given, or change the background color.
409 --version
411 Report version and exit.
412 -h --help
414 Display help message and exit.
415
417 lstopo and lstopo-no-graphics are capable of displaying a topological
418 map of the system in a variety of different output formats. The only
419 difference between lstopo and lstopo-no-graphics is that graphical out‐
420 puts are only supported by lstopo, to reduce dependencies on external
421 libraries. hwloc-ls is identical to lstopo-no-graphics.
422 The filename specified directly implies the output format that will be
424 used; see the OUTPUT FORMATS section, below. Output formats that sup‐
425 port color will indicate specific characteristics about individual CPUs
426 by their color; see the COLORS section, below.
427
429 By default, if no output filename is specific, the output is sent to a
430 graphical window if possible in the current environment (DISPLAY envi‐
431 ronment variable set on Unix, etc.). Otherwise, a text summary is dis‐
432 played in the console.
433 The filename on the command line usually determines the format of the
435 output. There are a few filenames that indicate specific output for‐
436 mats and devices (e.g., a filename of "-" will output a text summary to
437 stdout), but most filenames indicate the desired output format by their
438 suffix (e.g., "topo.png" will output a PNG-format file).
439 The format of the output may also be changed with "--of". For in‐
441 stance, "--of pdf" will generate a PDF-format file on the standard out‐
442 put, while "--of fig toto" will output a Xfig-format file named "toto".
443 The list of currently supported formats is given below. Any of them may
445 be used with "--of" or as a filename suffix.
446 default
448 Send the output to a window or to the console depending on the
449 environment.
450 console
452 Send a text summary to stdout. Binding or unallowed processors
453 are only annotated in this mode if verbose; see the COLORS sec‐
454 tion, below.
455 ascii Output an ASCII art representation of the map (formerly called
457 txt). If outputting to stdout and if colors are supported on
458 the terminal, the output will be colorized.
459 tikz or tex
461 Output a LaTeX tikzpicture representation of the map that can be
462 compiled with a LaTeX compiler.
463 fig Output a representation of the map that can be loaded in Xfig.
465 svg Output a SVG representation of the map, using Cairo (by default,
467 if supported) or a native SVG backend (fallback, always sup‐
468 ported). See cairosvg and nativesvg below.
469 cairosvg or svg(cairo)
471 If lstopo was compiled with the proper support, output a SVG
472 representation of the map using Cairo.
473 nativesvg or svg(native)
475 Output a SVG representation of the map using the native SVG
476 backend. It may be less pretty than the Cairo output, but it is
477 always supported, and SVG objects have attributes for identify‐
478 ing and manipulating them. See dynamic_SVG_example.html for an
479 example.
480 pdf If lstopo was compiled with the proper support, lstopo outputs a
482 PDF representation of the map.
483 ps If lstopo was compiled with the proper support, lstopo outputs a
485 Postscript representation of the map.
486 png If lstopo was compiled with the proper support, lstopo outputs a
488 PNG representation of the map.
489 synthetic
491 If the topology is symmetric (which requires that the root ob‐
492 ject has its symmetric_subtree field set), lstopo outputs a syn‐
493 thetic description string. This output may be reused as an in‐
494 put synthetic topology description later. See also the Syn‐
495 thetic topologies section in the documentation. Note that Misc
496 and I/O devices are ignored during this export.
497 xml If lstopo was compiled with the proper support, lstopo outputs
499 an XML representation of the map. It may be reused later, even
500 on another machine, with lstopo --input, the HWLOC_XMLFILE envi‐
501 ronment variable, or the hwloc_topology_set_xml() function.
502 The following special names may be used:
505 - Send a text summary to stdout.
507 /dev/stdout
509 Send a text summary to stdout. It is effectively the same as
510 specifying "-".
511 -.<format>
513 If the entire filename is "-.<format>", lstopo behaves as if
514 "--of <format> -" was given, which means a file of the given
515 format is sent to the standard output.
516 See the output of "lstopo --help" for a specific list of what graphical
519 output formats are supported in your hwloc installation.
520
522 The graphical output is made of nested boxes representing the inclusion
523 of objects in the hierarchy of resources. Usually a Machine box con‐
524 tains one or several Package boxes, that contain multiple Core boxes,
525 with one or several PUs each.
526 Caches
529 Caches are displayed in a slightly different manner because they do not
530 actually include computing resources such as cores. For instance, a L2
531 Cache shared by a pair of Cores is drawn as a Cache box on top of two
532 Core boxes (instead of having Core boxes inside the Cache box).
533 NUMA nodes and Memory-side Caches
536 By default, NUMA nodes boxes are drawn on top of their local computing
537 resources. For instance, a processor Package containing one NUMA node
538 and four Cores is displayed as a Package box containing the NUMA node
539 box above four Core boxes. If a NUMA node is local to the L3 Cache,
540 the NUMA node is displayed above that Cache box. All this specific
541 drawing strategy for memory objects may be disabled by passing command-
542 line option --children-order plain.
543 If multiple NUMA nodes are attached to the same parent object, they are
545 displayed inside an additional unnamed memory box.
546 If some Memory-side Caches exist in front of some NUMA nodes, they are
548 drawn as boxes immediately above them.
549 PCI bridges, PCI devices and OS devices
552 The PCI hierarchy is not drawn as a set of included boxes but rather as
553 a tree of bridges (that may actually be switches) with links between
554 them. The tree starts with a small square on the left for the host‐
555 bridge or root complex. It ends with PCI device boxes on the right.
556 Intermediate PCI bridges/switches may appear as additional small
557 squares in the middle.
558 PCI devices on the right of the tree are boxes containing their PCI bus
560 ID (such as 00:02.3). They may also contain sub-boxes for OS device
561 objects such as a network interface eth0 or a CUDA GPU cuda0.
562 The datarate of a PCI link may be written (in GB/s) right below its
564 drawn line (if the operating system and/or libraries are able to report
565 that information). This datarate is the currently configured PCI
566 datarate. It may change during execution since some devices are able
567 to slow their PCI links down when idle.
568 When there is a single link (horizontal line) on the right of a PCI
570 bridge, it means that a single device or bridge is connected on the
571 secondary PCI bus behind that bridge. When there is a vertical line,
572 it means that multiple devices and/or bridges are connected to the same
573 secondary PCI bus.
574
577 Individual CPUs and NUMA nodes are colored in the graphical output for‐
578 mats to indicate different characteristics:
579 Green The topology is reported as seen by a specific process (see
581 --pid), and the given CPU or NUMA node is in this process CPU or
582 Memory binding mask.
583 White The CPU or NUMA node is in the allowed set (see below). If the
585 topology is reported as seen by a specific process (see --pid),
586 the object is also not in this process binding mask.
587 Red The CPU or NUMA node is not in the allowed set (see below).
589 The "allowed set" is the set of CPUs or NUMA nodes to which the current
591 process is allowed to bind. The allowed set is usually either inher‐
592 ited from the parent process or set by administrative qpolicies on the
593 system. Linux cpusets are one example of limiting the allowed set for
594 a process and its children to be less than the full set of CPUs or NUMA
595 nodes on the system.
596 Different processes may therefore have different CPUs or NUMA nodes in
598 the allowed set. Hence, invoking lstopo in different contexts and/or
599 as different users may display different colors for the same individual
600 CPUs (e.g., running lstopo in one context may show a specific CPU as
601 red, but running lstopo in a different context may show the same CPU as
602 white).
603 Some lstopo output modes, e.g. the console mode (default non-graphical
605 output), do not support colors at all. The console mode displays the
606 above characteristics by appending text to each PU line if verbose mes‐
607 sages are enabled.
608
610 The color of each object in the graphical output may be enforced by
611 specifying a "lstopoStyle" info attribute in that object. Its value
612 should be a semi-colon separated list of "<attribute>=#rrggbb" where
613 rr, gg and bb are the RGB components of a color, each between 0 and
614 255, in hexadecimal (00 to ff). <attribute> may be
615 Background
617 Sets the background color of the main object box.
618 Text Sets the color of the text showing the object name, type, index,
620 etc.
621 Text2 Sets the color of the additional text near the object, for in‐
623 stance the link speed behind a PCI bridge.
624 The "lstopoStyle" info may be added to a temporarily-saved XML topolo‐
626 gies with hwloc-annotate, or with hwloc_obj_add_info(). For instance,
627 to display all core objects in blue (with white names):
628 lstopo save.xml
630 hwloc-annotate save.xml save.xml core:all info lstopoStyle "Back‐
631 ground=#0000ff;Text=#ffffff"
632 lstopo -i save.xml
633
635 In its graphical output, lstopo uses simple rectangular heuristics to
636 try to achieve a 4/3 ratio between width and height. Although the hi‐
637 erarchy of resources is properly reflected, the exact physical organi‐
638 zation (NUMA distances, rings, complete graphs, etc.) is currently ig‐
639 nored. The layout of a level may be changed with --vert, --horiz, and
640 --rect.
641 The position of memory children with respect to other children objects
643 may be changed using --children-order.
644
646 To display the machine topology in textual mode:
647 lstopo-no-graphics
649 To display the machine topology in ascii-art mode:
651 lstopo-no-graphics -.ascii
653 To display in graphical mode (assuming that the DISPLAY environment
655 variable is set to a relevant value):
656 lstopo
658 To export the topology to a PNG file:
660 lstopo file.png
662 To export an XML file on a machine and later display the corresponding
664 graphical output on another machine:
665 machine1$ lstopo file.xml
667 <transfer file.xml from machine1 to machine2>
668 machine2$ lstopo --input file.xml
669 To save the current machine topology to XML and later reload it faster
671 while still considering it as the current machine:
672 $ lstopo file.xml
674 <...>
675 $ lstopo --input file.xml --thissystem
676 To restrict an XML topology to only physical processors 0, 1, 4 and 5:
678 lstopo --input file.xml --restrict 0x33 newfile.xml
680 To restrict an XML topology to only numa node whose logical index is 1:
682 lstopo --input file.xml --restrict $(hwloc-calc --input file.xml
684 node:1) newfile.xml
685 To display a summary of the topology:
687 lstopo -s
689 To get more details about the topology:
691 lstopo -v
693 To only show cores:
695 lstopo --only core
697 To show cpusets:
699 lstopo --cpuset
701 To only show the cpusets of package:
703 lstopo --only package --cpuset-only
705 Simulate a fake hierarchy; this example shows with 2 NUMA nodes of 2
707 processor units:
708 lstopo --input "node:2 2"
710 To count the number of logical processors in the system
712 lstopo --only pu | wc -l
714 To append the kernel release and version to the graphical legend:
716 lstopo --append-legend "Kernel release: $(uname -r)" --append-legend
718 "Kernel version: $(uname -v)"
719
722 hwloc(7), hwloc-info(1), hwloc-bind(1), hwloc-annotate(1), hwloc-ps(1),
723 hwloc-gather-topology(1), hwloc-gather-cpuid(1)
7242.4.1 Feb 11, 2021 LSTOPO(1)