| /openbmc/linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | verifier_log.c | 117 /* validate rolling verifier log logic: try all variations of log buf in verif_log_subtest()
197 /* (ROLLING) get actual log size */ in verif_log_subtest()
208 /* (ROLLING, NULL) get actual log size */ in verif_log_subtest()
233 /* (ROLLING) expect -ENOSPC for one byte short log */ in verif_log_subtest()
240 /* (ROLLING) expect *not* -ENOSPC with exact log_true_size buffer */ in verif_log_subtest()
322 /* validate rolling verifier log logic: try all variations of log buf in verif_btf_log_subtest()
326 opts.log_level = 1; /* rolling log */ in verif_btf_log_subtest()
381 /* (ROLLING) get actual log size */ in verif_btf_log_subtest()
392 /* (ROLLING, NULL) get actual log size */ in verif_btf_log_subtest()
417 /* (ROLLING) expect -ENOSPC for one byte short log */ in verif_btf_log_subtest()
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/drivers/ |
| H A D | imx-uapi.rst | 35 sync by adding 1 dummy line every frame, which causes a rolling effect
41 From experiment it was found that during image rolling, the frame
44 and remain at that value until rolling stops.
54 to correct the rolling/split image.
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | era.rst | 16 coherency after rolling back a vendor snapshot.
72 The scenario of invalidating a cache when rolling back a vendor
83 Rolling back to an vendor snapshot
|
| H A D | persistent-data.rst | 10 different targets were rolling their own data structures, for example:
|
| /openbmc/linux/lib/zstd/compress/ |
| H A D | zstd_ldm.c | 24 U64 rolling; member
30 * Initializes the rolling hash state such that it will honor the
37 state->rolling = ~(U32)0; in ZSTD_ldm_gear_init()
68 U64 hash = state->rolling; in ZSTD_ldm_gear_reset()
103 hash = state->rolling; in ZSTD_ldm_gear_feed()
131 state->rolling = hash; in ZSTD_ldm_gear_feed()
345 /* Rolling hash state */ in ZSTD_ldm_generateSequences_internal()
355 /* Initialize the rolling hash state with the first minMatchLength bytes */ in ZSTD_ldm_generateSequences_internal()
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | xfs-delayed-logging-design.rst | 105 This results in a series of "rolling transactions" where the inode is locked
106 across the entire chain of transactions. Hence while this series of rolling
111 It is important to note that a series of rolling transactions in a permanent
158 are maintained as part of the transaction rolling mechanism.
190 transaction rolling mechanism to re-reserve space on every transaction roll. We
253 forwards progress guarantees that rolling permanent transactions require.
296 If all rolling transactions obey this rule, then they can all make forwards
336 A typical example of a rolling transaction is the removal of extents from an
338 of reservation size limitations. Hence a rolling extent removal transaction
820 rolling transactions for an example of this). Hence we *must* always have
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-fs-xfs | 37 rolling transactions. The grant head is exported in
|
| /openbmc/linux/drivers/md/bcache/ |
| H A D | stats.c | 15 * rolling averages.
17 * Every so often, a timer goes off and rescales the rolling averages.
|
| /openbmc/linux/include/asm-generic/ |
| H A D | bitops.h | 9 * out before rolling your own buggy implementation in assembly language.
|
| /openbmc/linux/drivers/net/ethernet/intel/i40e/ |
| H A D | i40e_ddp.c | 259 * @is_add: true when loading profile, false when rolling back the previous one
262 * also used for rolling back previously loaded profile.
388 * After rolling back removes entry from the list.
|
| /openbmc/linux/fs/xfs/scrub/ |
| H A D | repair.h | 22 * that we'll attach to a transaction without rolling the transaction to avoid
|
| /openbmc/qemu/tests/vm/ |
| H A D | ubuntu.aarch64 | 37 # writing. Using a rolling latest instead would mean that the SHA
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/minifi-cpp/ |
| H A D | minifi-cpp_0.15.0.bb | 156 sed -i "s|#appender.rolling.directory=.*|appender.rolling.directory=${MINIFI_LOG}|g" \
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | simple.txt | 53 than rolling your own. For one thing, the standard primitives interact
123 Please use them rather than rolling your own.
|
| /openbmc/u-boot/arch/arm/cpu/arm926ejs/mxs/ |
| H A D | spl_boot.c | 29 * code simple, it doesn't take rolling into consideration.
|
| /openbmc/linux/arch/ia64/lib/ |
| H A D | ip_fast_csum.S | 134 shr.u r10=r8,16 // yeah, keep it rolling
|
| /openbmc/linux/drivers/md/persistent-data/ |
| H A D | dm-btree-internal.h | 59 * Spines keep track of the rolling locks. There are 2 variants, read-only
|
| /openbmc/phosphor-power/power-supply/ |
| H A D | record_manager.hpp | 183 * @brief The last ID the power supply returns before rolling over
|
| /openbmc/linux/lib/raid6/ |
| H A D | altivec.uc | 48 * rolling over into the next byte
|
| H A D | int.uc | 58 * rolling over into the next byte
|
| /openbmc/witherspoon-pfault-analysis/power-supply/ |
| H A D | record_manager.hpp | 181 * @brief The last ID the power supply returns before rolling over
|
| /openbmc/linux/fs/btrfs/ |
| H A D | verity.c | 66 * stopping and rolling back rather than aborting the victim transaction.
452 * We try to handle recoverable errors while enabling verity by rolling it back
597 * interrupted or failed while rolling back, failed to cleanup the in btrfs_begin_enable_verity()
|
| /openbmc/linux/drivers/gpu/drm/i915/gt/ |
| H A D | intel_gt_clock_utils.c | 118 * rolling over every 1.5 hours). in gen6_read_clock_frequency()
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/google/gbmc/ |
| H A D | Hoth.interface.yaml | 208 Prevents hoth from rolling back and using the previous image. When an
|
| /openbmc/linux/drivers/md/ |
| H A D | dm-thin-metadata.h | 88 * Discards all uncommitted changes. Rereads the superblock, rolling back
|