| /linux-6.15/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-6.15/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-6.15/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-6.15/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-6.15/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-6.15/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-6.15/fs/bcachefs/ |
| D | logged_ops.c | 43 "filesystem marked as clean but have logged op\n%s", in resume_logged_op()
103 * operation in the logged ops btree. in bch2_logged_op_finish()
113 bch2_fs_fatal_error(c, "deleting logged operation %s: %s", in bch2_logged_op_finish()
|
| /linux-6.15/fs/btrfs/ |
| D | tree-log.c | 67 * when the directory they are being removed from was logged.
137 * using in ram and once, once to create all the inodes logged in the tree
353 * pin down any logged extents, so we have to read the block. in process_one_buffer()
463 * replay the extents we've logged we get the right nbytes. in overwrite_item()
531 * was logged as zero. This is done when the tree logging code in overwrite_item()
2015 * created in the log while the subvolume was logged.
2019 * directory is in a logged range item, but not actually in the log
2117 * by an older kernel that logged both dir index and dir item keys, all in check_item_in_log()
2897 * logged are safely on disk only if it returns 0.
3286 * Check if an inode was logged in the current transaction. This correctly deals
[all …]
|
| D | tree-log.h | 38 /* Indicate if the inode being logged was logged before. */
|
| D | delayed-inode.h | 100 * Track if this delayed item was already logged.
103 bool logged; member
|
| D | btrfs_inode.h | 210 * ID of the transaction that last logged this inode.
233 * points to an inode that needs to be logged.
250 * The offset of the last dir index key that was logged.
299 * the directory was logged. See tree-log.c for all the
447 * logged.
|
| /linux-6.15/fs/xfs/ |
| D | xfs_mount.h | 546 /* Kernel has logged a warning about pNFS being used on this fs. */ in __XFS_HAS_V4_FEAT()
548 /* Kernel has logged a warning about online fsck being used on this fs. */ in __XFS_HAS_V4_FEAT()
550 /* Kernel has logged a warning about shrink being used on this fs. */ in __XFS_HAS_V4_FEAT()
552 /* Kernel has logged a warning about logged xattr updates being used. */ in __XFS_HAS_V4_FEAT()
558 /* Filesystem can use logged extended attributes */ in __XFS_HAS_V4_FEAT()
560 /* Kernel has logged a warning about blocksize > pagesize on this fs. */ in __XFS_HAS_V4_FEAT()
562 /* Kernel has logged a warning about exchange-range being used on this fs. */ in __XFS_HAS_V4_FEAT()
564 /* Kernel has logged a warning about parent pointers being used on this fs. */ in __XFS_HAS_V4_FEAT()
566 /* Kernel has logged a warning about metadata dirs being used on this fs. */ in __XFS_HAS_V4_FEAT()
570 /* Kernel has logged a warning about zoned RT device being used on this fs. */ in __XFS_HAS_V4_FEAT()
|
| D | xfs_inode_item.h | 34 unsigned int ili_fields; /* fields to be logged */
35 unsigned int ili_fsync_fields; /* logged since last fsync */
|
| D | xfs_buf_item_recover.c | 459 * Perform a 'normal' buffer recovery. Each logged region of the
462 * where to place the logged data.
496 * The dirty regions logged in the buffer, even though in xlog_recover_do_reg_buffer()
597 * data for the inodes is always logged through the inodes themselves rather
641 * the current logged region. Find the next in xlog_recover_do_inode_buffer()
642 * logged region that contains or is beyond in xlog_recover_do_inode_buffer()
650 * If there are no more logged regions in the in xlog_recover_do_inode_buffer()
665 * If the current logged region starts after the current in xlog_recover_do_inode_buffer()
677 * The current logged region contains a copy of the in xlog_recover_do_inode_buffer()
899 * being logged. That means they do not contain a valid LSN in xlog_recover_get_buf_lsn()
[all …]
|
| D | xfs_buf_item.c | 65 * stretch of non-contiguous chunks to be logged. Contiguous chunks are logged
111 * logged. This makes the changes in the buffer appear to log recovery as though
118 * format structures. If the item has previously been logged and has dirty
156 * The buffer has been logged just to order it. It is not being in xfs_buf_item_size()
568 * logged data associated with the buffer recorded in the buf log item, then
575 * item was logged, then another reference was taken when it was pinned, so we
604 * The bli dirty state should match whether the blf has logged segments in xfs_buf_item_release()
942 * Return true if the buffer has any ranges logged/dirtied by a transaction,
|
| /linux-6.15/Documentation/admin-guide/LSM/ |
| D | landlock.rst | 19 Denied access requests are logged by default for a sandboxed program if `audit`
46 the first logged ``AUDIT_LANDLOCK_ACCESS`` record of a domain. It identifies
66 which might not have been logged according to the audit rules and
110 logged or not.
|
| /linux-6.15/Documentation/filesystems/bcachefs/ |
| D | errorcodes.rst | 21 recovered even if it wasn't logged.
28 as possible. Frequently, the error will be logged at a place far removed from
|
| /linux-6.15/include/linux/ |
| D | aer.h | 37 u8 header_len; /* Length of the Logged TLP Header in DWORDs */
38 bool flit; /* TLP was logged when in Flit mode */
|
| /linux-6.15/tools/testing/selftests/acct/ |
| D | acct_syscall.c | 66 ksft_test_result_fail("Terminated child process not logged\n"); in main()
71 ksft_test_result_pass("Successfully logged terminated process.\n"); in main()
|
| /linux-6.15/drivers/crypto/intel/qat/qat_common/ |
| D | adf_gen4_tl.h | 48 * @reg_tl_rd_lat_max: maximum logged read latency
50 * @reg_tl_gp_lat_max: maximum logged get to put latency
|
| /linux-6.15/security/landlock/ |
| D | domain.h | 89 * @log_status: Whether this domain should be logged or not. Because
96 * Masked (i.e. never logged) denials are still counted.
|
| /linux-6.15/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-6.15/Documentation/arch/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]
|