Get desktop application:
View/edit binary Protocol Buffers messages
ArchiveMetadataConfig is the format of the METADATA file in tars produced by trace collection scripts.
Used in:
Trace was recorded using FTrace
Trace was recorded using eBPF
Used in:
Indexes into the EventDescriptor table.
The CPU on which, and timestamp at which, this event was recorded.
TODO(ilhamster) rename to timestamp, and add a description. The timestamp recorded in the event may have different units depending on what trace clock was used: 'local' and 'global' are converted to ns, but some clocks, such as the arch-specific 'x86_tsc', are in clockticks (convertible to, but not natively, ns), and some, like 'counter', cannot be converted to ns at all. Sideband data, such as the requested trace clock, must be used to properly interpret these.
True if this Event fell outside of the known-valid range of a trace which experienced buffer overruns.
This set of property fields has a 1:1 correspondence with the PropertyDescriptors in this event's EventDescriptor. If the corresponding PropertyDescriptor's type is NUMBER, this field should be interpreted as an int64. If the corresponding PropertyDescriptor's type is TEXT, this field should be interpreted as an index into the EventSet's string_table.
Used in:
Indexes into the string table.
Used in:
Indexes into the string table.
Used in:
Used in:
Set of strings referenced by string-index fields among the events and event descriptors
The default event loaders type of this collection.
Used in:
,The unique name of the collection.
The creator tag provided at this collection's creation.
This collection's owners.
The collection's tags.
The collection's description.
The time of this collection's creation.
Additional properties applied to this collection.
The events collected during the collection.
The target machine on which the collection was performed.
A single named property's value. Properties may not contain PII, either in their names or in their values.
Used in:
Used in:
The index of this platform
CPU vendor
CPUID fields.
The set of logical cores.
Used in:
This logical core's index in the topology. Used as a scalar identifier of this CPU in profiling tools.
The 0-indexed identifier of the socket of this logical core. 'Socket' represents a distinct IC package.
The 0-indexed NUMA node of this logical core. NUMA nodes are groupings of cores and cache hierarchy that are 'local' to their own memory; accessing non-local memory is costlier than accessing local memory.
The 0-indexed die identifier. Some IC packages may include more than one distinct dies.
The 0-indexed core identifier within its die. A core is a single processing unit with its own register storage and L1 caches.
The 0-indexed hyperthread, or hardware thread, identifier within its core. A hardware thread is a partitioning of a core that can execute a single instruction stream. Hyperthreads on a core share the core's resources, such as its functional units and cache hierarchy, but maintain independent registers, and help ensure that the CPU remains fully utilized.