Home
last modified time | relevance | path

Searched full:logged (Results 1 – 25 of 334) sorted by relevance

12345678910>>...14

/linux/tools/perf/pmu-events/arch/x86/amdzen1/
H A Dfloating-point.json81 …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 …]
H A Dcore.json11 …, 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/Documentation/admin-guide/device-mapper/
H A Dlog-writes.rst17 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/Documentation/ABI/testing/
H A Dsysfs-firmware-acpi11 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,
H A Dsysfs-platform-dfl-fme53 Write this file to clear errors logged in pcie0_errors. Write
62 Write this file to clear errors logged in pcie1_errors. Write
92 Write this file to clear errors logged in fme_errors. Write
/linux/tools/perf/pmu-events/arch/x86/amdzen2/
H A Dfloating-point.json40 …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…
H A Dcore.json11 …, 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/tools/perf/pmu-events/arch/x86/amdzen3/
H A Dfloating-point.json40 …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/fs/btrfs/
H A Dtree-log.c67 * 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()
466 * replay the extents we've logged we get the right nbytes. in overwrite_item()
533 * was logged as zero. This is done when the tree logging code in overwrite_item()
2031 * created in the log while the subvolume was logged.
2035 * directory is in a logged range item, but not actually in the log
2133 * by an older kernel that logged both dir index and dir item keys, all in check_item_in_log()
2915 * logged are safely on disk only if it returns 0.
3304 * Check if an inode was logged in the current transaction. This correctly deals
[all …]
H A Dtree-log.h38 /* Indicate if the inode being logged was logged before. */
H A Dbtrfs_inode.h209 * ID of the transaction that last logged this inode.
232 * points to an inode that needs to be logged.
249 * The offset of the last dir index key that was logged.
298 * the directory was logged. See tree-log.c for all the
446 * logged.
H A Dordered-data.h79 /* Used during fsync to track already logged extents */
81 /* We have already logged all the csums of the ordered extent */
/linux/Documentation/firmware-guide/acpi/
H A Dmethod-tracing.rst201 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/fs/bcachefs/
H A Dlogged_ops.c43 "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/fs/xfs/
H A Dxfs_mount.h499 /* Kernel has logged a warning about pNFS being used on this fs. */ in __XFS_HAS_V4_FEAT()
501 /* Kernel has logged a warning about online fsck being used on this fs. */ in __XFS_HAS_V4_FEAT()
503 /* Kernel has logged a warning about shrink being used on this fs. */ in __XFS_HAS_V4_FEAT()
505 /* Kernel has logged a warning about logged xattr updates being used. */ in __XFS_HAS_V4_FEAT()
511 /* Filesystem can use logged extended attributes */ in __XFS_HAS_V4_FEAT()
513 /* Kernel has logged a warning about blocksize > pagesize on this fs. */ in __XFS_HAS_V4_FEAT()
515 /* Kernel has logged a warning about exchange-range being used on this fs. */ in __XFS_HAS_V4_FEAT()
517 /* Kernel has logged a warning about parent pointers being used on this fs. */ in __XFS_HAS_V4_FEAT()
519 /* Kernel has logged a warning about metadata dirs being used on this fs. */ in __XFS_HAS_V4_FEAT()
H A Dxfs_inode_item.h34 unsigned int ili_fields; /* fields to be logged */
35 unsigned int ili_fsync_fields; /* logged since last fsync */
H A Dxfs_buf_item_recover.c459 * 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 …]
H A Dxfs_buf_item.c83 * stretch of non-contiguous chunks to be logged. Contiguous chunks are logged
175 * logged. This makes the changes in the buffer appear to log recovery as though
182 * format structures. If the item has previously been logged and has dirty
220 * The buffer has been logged just to order it. It is not being in xfs_buf_item_size()
682 * logged data associated with the buffer recorded in the buf log item, then
689 * item was logged, then another reference was taken when it was pinned, so we
718 * The bli dirty state should match whether the blf has logged segments in xfs_buf_item_release()
1056 * Return true if the buffer has any ranges logged/dirtied by a transaction,
/linux/Documentation/filesystems/bcachefs/
H A Derrorcodes.rst21 recovered even if it wasn't logged.
28 as possible. Frequently, the error will be logged at a place far removed from
/linux/drivers/crypto/intel/qat/qat_common/
H A Dadf_gen4_tl.h48 * @reg_tl_rd_lat_max: maximum logged read latency
50 * @reg_tl_gp_lat_max: maximum logged get to put latency
/linux/Documentation/isdn/
H A Dinterface_capi.rst327 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/Documentation/arch/x86/
H A Diommu.rst150 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/fs/pstore/
H A DKconfig76 This enables panic and oops messages to be logged to a circular
98 This enables panic and oops message to be logged to a block dev
/linux/drivers/bus/
H A Domap_l3_noc.c30 * 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
/linux/arch/sparc/include/asm/
H A Dchafsr.h66 * 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

12345678910>>...14