Viavi Xgig, Руководство пользователя

Страница: 301 / 468

Filter And Hide Chapter 13, Configuring Xgig TraceView
Xgig Analyzer User’s Guide 287
Figure 130: Devices And Addresses Dialog
Expert generates the end-of-capture mapping in the post-capture.devices file. When present, that
mapping is displayed in read-only so you can see the devices, addresses and configuration spaces
at the end of a boot-up sequence. The mapping at the beginning of the capture is always editable
and when you change it, TraceView prompts you to re-run Expert to regenerate the expert
annotations.
When a capture stops, TraceControl copies the device mapping from the first domain port into the
pre-capture.devices file for the domain so that every capture's pre-capture.device file is initialized
from TraceControl's domain device mapping.
The devices and addresses mapping is mandatory for TraceView and Expert to decode any
protocols over PCIe, such as NVMe. The information is exchanged during the boot sequence
between the host and the devices. It may change from one reboot to the next.
You can fill the device mapping in two ways. First, you can click the “Automatically filling this
dialog” hyperlink at the top of the dialog. When you do, a popup appears instructing you how to
fill the dialog automatically. Second, you can enter the information manually. The buttons on the
dialog's right-hand side allow you to add or remove devices, queues, and addresses.
If you are adding information manually, you should add every PCIe device found in the capture
and provide the Device ID, Class Code, and the Base Address Register (BAR) information for the
address ranges used in the capture. When the device is of Class Code 0x010802 (NVMe), then you
should also create the NVMe queues that are used in the trace and verify that the Memory Page
Size (MPS) and Sector Size are set correctly. The NVMe queues have an ID, type, and size. The
regular Submission and Completion queues can be Physically Contiguous or not, while the Admin