| /Linux-v6.1/tools/perf/pmu-events/arch/x86/amdzen1/ |
| D | floating-point.json | 81 …number of x87 floating-point Ops that have retired. The number of events logged per cycle can vary…
88 …number of x87 floating-point Ops that have retired. The number of events logged per cycle can vary…
95 …number of x87 floating-point Ops that have retired. The number of events logged per cycle can vary…
102 …number of x87 floating-point Ops that have retired. The number of events logged per cycle can vary…
109 …e-based event. The number of retired SSE/AVX FLOPS. The number of events logged per cycle can vary…
116 …e-based event. The number of retired SSE/AVX FLOPS. The number of events logged per cycle can vary…
123 …e-based event. The number of retired SSE/AVX FLOPS. The number of events logged per cycle can vary…
130 …e-based event. The number of retired SSE/AVX FLOPS. The number of events logged per cycle can vary…
137 …e-based event. The number of retired SSE/AVX FLOPS. The number of events logged per cycle can vary…
144 …e-based event. The number of retired SSE/AVX FLOPS. The number of events logged per cycle can vary…
[all …]
|
| D | core.json | 11 …, exceptions, interrupts, microcode assists, etc.). The number of events logged per cycle can vary…
123 …used retired branch instructions retired per cycle. The number of events logged per cycle can vary…
|
| /Linux-v6.1/Documentation/admin-guide/device-mapper/ |
| D | log-writes.rst | 17 cache. This means that normal WRITE requests are not actually logged until the
39 Any REQ_FUA requests bypass this flushing mechanism and are logged as soon as
48 If we logged DISCARD when it completed, the replay would look like this:
68 <#logged entries> <highest allocated sector>
71 #logged entries Number of logged entries
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-firmware-acpi | 11 firmware_start_ns: Timer value logged at the beginning
13 bootloader_load_ns: Timer value logged just prior to
16 bootloader_launch_ns: Timer value logged just prior to
19 exitbootservice_start_ns: Timer value logged at the
23 exitbootservice_end_ns: Timer value logged at the point
38 logged since the last full boot sequence,
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/amdzen2/ |
| D | floating-point.json | 40 …e-based event. The number of retired SSE/AVX FLOPS. The number of events logged per cycle can vary…
46 …e-based event. The number of retired SSE/AVX FLOPS. The number of events logged per cycle can vary…
53 …e-based event. The number of retired SSE/AVX FLOPS. The number of events logged per cycle can vary…
59 …e-based event. The number of retired SSE/AVX FLOPS. The number of events logged per cycle can vary…
65 …e-based event. The number of retired SSE/AVX FLOPS. The number of events logged per cycle can vary…
|
| D | core.json | 11 …, exceptions, interrupts, microcode assists, etc.). The number of events logged per cycle can vary…
128 …mber of fuse-branch instructions retired per cycle. The number of events logged per cycle can vary…
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/amdzen3/ |
| D | floating-point.json | 40 …e-based event. The number of retired SSE/AVX FLOPS. The number of events logged per cycle can vary…
46 …e-based event. The number of retired SSE/AVX FLOPs. The number of events logged per cycle can vary…
52 …e-based event. The number of retired SSE/AVX FLOPs. The number of events logged per cycle can vary…
58 …e-based event. The number of retired SSE/AVX FLOPs. The number of events logged per cycle can vary…
64 …e-based event. The number of retired SSE/AVX FLOPs. The number of events logged per cycle can vary…
|
| /Linux-v6.1/fs/btrfs/ |
| D | tree-log.h | 24 /* Indicate if the inode being logged was logged before. */
26 /* Tracks the last logged dir item/index key offset. */
|
| D | tree-log.c | 60 * when the directory they are being removed from was logged.
130 * using in ram and once, once to create all the inodes logged in the tree
333 * pin down any logged extents, so we have to read the block. in process_one_buffer()
435 * replay the extents we've logged we get the right nbytes. in do_overwrite_item()
502 * was logged as zero. This is done when the tree logging code in do_overwrite_item()
2050 * created in the log while the subvolume was logged.
2054 * directory is in a logged range item, but not actually in the log
2153 * by an older kernel that logged both dir index and dir item keys, all in check_item_in_log()
2924 * you know that any inodes previously logged are safely on disk only
3323 * Check if an inode was logged in the current transaction. This correctly deals
[all …]
|
| D | btrfs_inode.h | 139 * transid that last logged this inode
166 * The offset of the last dir index key that was logged.
197 * the directory was logged. See tree-log.c for all the
331 * logged.
|
| D | delayed-inode.h | 92 * Track if this delayed item was already logged.
95 bool logged; member
|
| D | ordered-data.h | 71 /* Used during fsync to track already logged extents */
73 /* We have already logged all the csums of the ordered extent */
|
| /Linux-v6.1/Documentation/firmware-guide/acpi/ |
| D | method-tracing.rst | 201 during any method execution will be logged.
207 during method execution of "trace_method_name" will be logged.
213 during method execution of "trace_method_name" will be logged only once.
219 during method/opcode execution of "trace_method_name" will be logged.
225 during method/opcode execution of "trace_method_name" will be logged only
|
| /Linux-v6.1/fs/xfs/ |
| D | xfs_inode_item.h | 33 unsigned int ili_fields; /* fields to be logged */
34 unsigned int ili_fsync_fields; /* logged since last fsync */
|
| D | xfs_buf_item_recover.c | 439 * Perform a 'normal' buffer recovery. Each logged region of the
442 * where to place the logged data.
476 * The dirty regions logged in the buffer, even though in xlog_recover_do_reg_buffer()
577 * data for the inodes is always logged through the inodes themselves rather
621 * the current logged region. Find the next in xlog_recover_do_inode_buffer()
622 * logged region that contains or is beyond in xlog_recover_do_inode_buffer()
630 * If there are no more logged regions in the in xlog_recover_do_inode_buffer()
645 * If the current logged region starts after the current in xlog_recover_do_inode_buffer()
657 * The current logged region contains a copy of the in xlog_recover_do_inode_buffer()
784 * being logged. That means they do not contain a valid LSN in xlog_recover_get_buf_lsn()
[all …]
|
| D | xfs_xattr.c | 37 * Protect ourselves from an idle log clearing the logged xattrs log in xfs_attr_grab_log_assist()
56 "EXPERIMENTAL logged extended attributes feature in use. Use at your own risk!"); in xfs_attr_grab_log_assist()
76 /* Logged xattrs require a V5 super for log_incompat */ in xfs_attr_want_log_assist()
|
| D | xfs_buf_item.c | 82 * stretch of non-contiguous chunks to be logged. Contiguous chunks are logged
174 * logged. This makes the changes in the buffer appear to log recovery as though
181 * format structures. If the item has previously been logged and has dirty
219 * The buffer has been logged just to order it. It is not being in xfs_buf_item_size()
639 * logged data associated with the buffer recorded in the buf log item, then
646 * item was logged, then another reference was taken when it was pinned, so we
675 * The bli dirty state should match whether the blf has logged segments in xfs_buf_item_release()
982 * Return true if the buffer has any ranges logged/dirtied by a transaction,
|
| D | xfs_inode_item.c | 33 * The logged size of an inode fork is always the current size of the inode
34 * fork. This means that when an inode fork is relogged, the size of the logged
36 * previously logged state + the current state. This is different relogging
38 * previously logged changes when smaller regions are relogged.
42 * inode gets -smaller- rather than stays the same size as the previously logged
490 /* update the format with the exact fields we actually logged */ in xfs_inode_item_format()
794 * attached to the buffer from the AIL if they have not been re-logged and
|
| /Linux-v6.1/Documentation/isdn/ |
| D | interface_capi.rst | 327 logged. The traceflag parameter is initialized with the value of the
331 If the value of traceflag is non-zero, CAPI messages are logged.
332 DATA_B3 messages are only logged if the value of traceflag is > 2.
335 length are logged. Otherwise, kernelcapi logs a readable representation of
|
| /Linux-v6.1/fs/xfs/libxfs/ |
| D | xfs_log_format.h | 207 * items logged by the transaction so we know how many to expect during
217 uint th_num_items; /* num items logged by trans */
269 * log. The size of the inline data/extents/b-tree root to be logged
276 uint32_t ilf_fields; /* flags for fields logged */
298 uint32_t ilf_fields; /* flags for fields logged */
385 * Define the format of the inode core that is logged. This structure must be
506 * map describes which 128 byte chunks of the buffer have been logged.
|
| D | xfs_shared.h | 57 /* Transaction needs to be logged */
59 /* Superblock is dirty and needs to be logged */
|
| /Linux-v6.1/Documentation/x86/ |
| D | iommu.rst | 150 AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0007 address=0xffffc02000 flags=0x0000]
151 AMD-Vi: Event logged [IO_PAGE_FAULT device=07:00.0 domain=0x0007 address=0xffffc02000 flags=0x0000]
|
| /Linux-v6.1/Documentation/ABI/removed/ |
| D | sysfs-kernel-uids | 9 are two users logged in, each with an equal number of
|
| /Linux-v6.1/arch/sparc/include/asm/ |
| D | chafsr.h | 66 * subunit will be logged. All errors in subsequent 16-byte subunits
231 * Since there is only one AFAR, when multiple events have been logged by the
235 * as soon as the one bit in AFSR that corresponds to the event logged in AFAR is
|
| /Linux-v6.1/drivers/bus/ |
| D | omap_l3_noc.c | 30 * 4) Print the logged information.
43 * do not have connectivity, the error is logged in
155 * 2) Identify the slave where the error information is logged
|
