logged (full) in projects: kernel - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

12 3 4 5 6 7 8 9 10 >>...27

/kernel/linux/linux-6.6/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…`
/kernel/linux/linux-5.10/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…`
/kernel/linux/linux-6.6/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`
/kernel/linux/linux-5.10/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`
/kernel/linux/linux-6.6/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,`
/kernel/linux/linux-5.10/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…
/kernel/linux/linux-6.6/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…
/kernel/linux/linux-6.6/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…
/kernel/linux/linux-6.6/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`
/kernel/linux/linux-5.10/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`
/kernel/linux/linux-6.6/fs/btrfs/
D	tree-log.c	69 * when the directory they are being removed from was logged. 139 * using in ram and once, once to create all the inodes logged in the tree 361 * pin down any logged extents, so we have to read the block. in process_one_buffer() 475 * replay the extents we've logged we get the right nbytes. in overwrite_item() 542 * was logged as zero. This is done when the tree logging code in overwrite_item() 2086 * created in the log while the subvolume was logged. 2090 * directory is in a logged range item, but not actually in the log 2188 * by an older kernel that logged both dir index and dir item keys, all in check_item_in_log() 2944 * you know that any inodes previously logged are safely on disk only 3338 * Check if an inode was logged in the current transaction. This correctly deals [all …]
D	tree-log.h	`30 /* Indicate if the inode being logged was logged before. */`
D	btrfs_inode.h	`141 * ID of the transaction that last logged this inode. 164 * points to an inode that needs to be logged. 181 * The offset of the last dir index key that was logged. 212 * the directory was logged. See tree-log.c for all the 349 * logged.`
/kernel/linux/linux-5.10/fs/xfs/
D	xfs_buf_item_recover.c	430 * Perform a 'normal' buffer recovery. Each logged region of the 433 * where to place the logged data. 467 * The dirty regions logged in the buffer, even though in xlog_recover_do_reg_buffer() 568 * data for the inodes is always logged through the inodes themselves rather 612 * the current logged region. Find the next in xlog_recover_do_inode_buffer() 613 * logged region that contains or is beyond in xlog_recover_do_inode_buffer() 621 * If there are no more logged regions in the in xlog_recover_do_inode_buffer() 636 * If the current logged region starts after the current in xlog_recover_do_inode_buffer() 648 * The current logged region contains a copy of the in xlog_recover_do_inode_buffer() 765 * being logged. That means they do not contain a valid LSN in xlog_recover_get_buf_lsn() [all …]
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.c	63 * stretch of non-contiguous chunks to be logged. Contiguous chunks are logged 124 * logged. This makes the changes in the buffer appear to log recovery as though 131 * format structures. If the item has previously been logged and has dirty 166 * The buffer has been logged just to order it. It is not being in xfs_buf_item_size() 557 * logged data associated with the buffer recorded in the buf log item, then 564 * item was logged, then another reference was taken when it was pinned, so we 593 * The bli dirty state should match whether the blf has logged segments in xfs_buf_item_release() 900 * Return true if the buffer has any ranges logged/dirtied by a transaction,
D	xfs_inode_item.c	32 * The logged size of an inode fork is always the current size of the inode 33 * fork. This means that when an inode fork is relogged, the size of the logged 35 * previously logged state + the current state. This is different relogging 37 * previously logged changes when smaller regions are relogged. 41 * inode gets -smaller- rather than stays the same size as the previously logged 459 /* update the format with the exact fields we actually logged / in xfs_inode_item_format() 745 attached to the buffer from the AIL if they have not been re-logged and 802 * re-logged and clearing the inode's flush state.
/kernel/linux/linux-6.6/fs/xfs/
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	442 * Perform a 'normal' buffer recovery. Each logged region of the 445 * where to place the logged data. 479 * The dirty regions logged in the buffer, even though in xlog_recover_do_reg_buffer() 580 * data for the inodes is always logged through the inodes themselves rather 624 * the current logged region. Find the next in xlog_recover_do_inode_buffer() 625 * logged region that contains or is beyond in xlog_recover_do_inode_buffer() 633 * If there are no more logged regions in the in xlog_recover_do_inode_buffer() 648 * If the current logged region starts after the current in xlog_recover_do_inode_buffer() 660 * The current logged region contains a copy of the in xlog_recover_do_inode_buffer() 848 * 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() 67 "EXPERIMENTAL logged extended attributes feature in use. Use at your own risk!"); in xfs_attr_grab_log_assist() 87 /* Logged xattrs require a V5 super for log_incompat */ in xfs_attr_want_log_assist()`
D	xfs_buf_item.c	83 * 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,
/kernel/linux/linux-5.10/fs/btrfs/
D	tree-log.c	59 * when the directory they are being removed from was logged. 128 * using in ram and once, once to create all the inodes logged in the tree 307 * pin down any logged extents, so we have to read the block. in process_one_buffer() 413 * replay the extents we've logged we get the right nbytes. in overwrite_item() 480 * was logged as zero. This is done when the tree logging code in overwrite_item() 1995 /* the existing item matches the logged item / in replay_one_name() 2156 created in the log while the subvolume was logged. 2160 * directory is in a logged range item, but not actually in the log 3050 * you know that any inodes previously logged are safely on disk only 3355 * Check if an inode was logged in the current transaction. We can't always rely [all …]
/kernel/linux/linux-5.10/Documentation/filesystems/
D	xfs-delayed-logging-design.rst	11 such as inodes and dquots, are logged in logical format where the details 12 logged are made up of the changes to in-core structures rather than on-disk 14 logged. The reason for these differences is to reduce the amount of log space 15 required for objects that are frequently logged. Some parts of inodes are more 16 frequently logged than others, and inodes are typically more frequently logged 18 amount of metadata logged low is of prime importance. 119 actually relatively easy to do - all the changes to logged items are already 498 the size of the transaction and the number of regions being logged (the number 506 vector is 12 bytes, so the total to be logged is approximately 1.75MB. In

12 3 4 5 6 7 8 9 10 >>...27