logged (full) in projects: Linux-v5.15 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

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

/Linux-v5.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-v5.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-v5.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,`
D	sysfs-platform-dfl-fme	`53 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-v5.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-v5.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-v5.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-v5.15/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() 775 * 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	81 * stretch of non-contiguous chunks to be logged. Contiguous chunks are logged 173 * logged. This makes the changes in the buffer appear to log recovery as though 180 * format structures. If the item has previously been logged and has dirty 218 * The buffer has been logged just to order it. It is not being in xfs_buf_item_size() 638 * logged data associated with the buffer recorded in the buf log item, then 645 * item was logged, then another reference was taken when it was pinned, so we 674 * The bli dirty state should match whether the blf has logged segments in xfs_buf_item_release() 981 * 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 485 /* update the format with the exact fields we actually logged / in xfs_inode_item_format() 771 attached to the buffer from the AIL if they have not been re-logged and 828 * re-logged and clearing the inode's flush state.
/Linux-v5.15/fs/btrfs/
D	tree-log.c	59 * when the directory they are being removed from was logged. 129 * using in ram and once, once to create all the inodes logged in the tree 348 * pin down any logged extents, so we have to read the block. in process_one_buffer() 454 * replay the extents we've logged we get the right nbytes. in overwrite_item() 521 * was logged as zero. This is done when the tree logging code in overwrite_item() 2008 /* the existing item matches the logged item / in replay_one_name() 2169 created in the log while the subvolume was logged. 2173 * directory is in a logged range item, but not actually in the log 3067 * you know that any inodes previously logged are safely on disk only 3444 * Check if an inode was logged in the current transaction. This may often [all …]
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 */`
D	btrfs_inode.h	`129 * transid that last logged this inode 177 * the directory was logged. See tree-log.c for all the 318 * logged.`
/Linux-v5.15/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
/Linux-v5.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-v5.15/fs/xfs/libxfs/
D	xfs_log_format.h	`203 * items logged by the transaction so we know how many to expect during 213 uint th_num_items; /* num items logged by trans / 261 log. The size of the inline data/extents/b-tree root to be logged 268 uint32_t ilf_fields; /* flags for fields logged / 290 uint32_t ilf_fields; / flags for fields logged / 377 Define the format of the inode core that is logged. This structure must be 473 * map describes which 128 byte chunks of the buffer have been logged.`
/Linux-v5.15/Documentation/ABI/removed/
D	sysfs-kernel-uids	`9 are two users logged in, each with an equal number of`
/Linux-v5.15/drivers/bus/
D	omap_l3_noc.c	`38 * 4) Print the logged information. 51 * do not have connectivity, the error is logged in 163 * 2) Identify the slave where the error information is logged`
/Linux-v5.15/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-v5.15/drivers/firmware/efi/
D	efi-pstore.c	`214 * This function returns a size of NVRAM entry logged via efi_pstore_write(). 217 * size > 0: Got data of an entry logged via efi_pstore_write() successfully, 219 * size == 0: Entry was not logged via efi_pstore_write(),`
/Linux-v5.15/arch/x86/ras/
D	Kconfig	`23 file that dumps out the current state of all pages logged so far.`
/Linux-v5.15/fs/pstore/
D	Kconfig	`157 This enables panic and oops messages to be logged to a circular 180 This enables panic and oops message to be logged to a block dev`

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