/openbmc/qemu/include/block/ |
H A D | accounting.h | 65 * .boundaries = {10, 50, 100}, 69 * @boundaries array define histogram intervals as follows: 70 * [0, boundaries[0]), [boundaries[0], boundaries[1]), ... 71 * [boundaries[nbins-2], +inf) 77 uint64_t *boundaries; /* @nbins-1 numbers here member 78 (all boundaries, except 0 and +inf) */ 121 uint64List *boundaries);
|
/openbmc/qemu/block/ |
H A D | accounting.c | 141 if (latency_ns < hist->boundaries[0]) { in block_latency_histogram_account() 146 if (latency_ns >= hist->boundaries[hist->nbins - 2]) { in block_latency_histogram_account() 151 pos = bsearch(&latency_ns, hist->boundaries, hist->nbins - 2, in block_latency_histogram_account() 152 sizeof(hist->boundaries[0]), in block_latency_histogram_account() 156 hist->bins[pos - hist->boundaries + 1]++; in block_latency_histogram_account() 160 uint64List *boundaries) in block_latency_histogram_set() argument 168 for (entry = boundaries; entry; entry = entry->next) { in block_latency_histogram_set() 177 g_free(hist->boundaries); in block_latency_histogram_set() 178 hist->boundaries = g_new(uint64_t, hist->nbins - 1); in block_latency_histogram_set() 179 for (entry = boundaries, ptr = hist->boundaries; entry; in block_latency_histogram_set() [all …]
|
H A D | qapi-sysemu.c | 511 bool has_boundaries, uint64List *boundaries, in qmp_block_latency_histogram_set() argument 538 has_boundaries_read ? boundaries_read : boundaries); in qmp_block_latency_histogram_set() 540 error_setg(errp, "Device '%s' set read boundaries fail", id); in qmp_block_latency_histogram_set() 548 has_boundaries_write ? boundaries_write : boundaries); in qmp_block_latency_histogram_set() 550 error_setg(errp, "Device '%s' set write boundaries fail", id); in qmp_block_latency_histogram_set() 558 has_boundaries_append ? boundaries_append : boundaries); in qmp_block_latency_histogram_set() 560 error_setg(errp, "Device '%s' set append write boundaries fail", id); in qmp_block_latency_histogram_set() 568 has_boundaries_flush ? boundaries_flush : boundaries); in qmp_block_latency_histogram_set() 570 error_setg(errp, "Device '%s' set flush boundaries fail", id); in qmp_block_latency_histogram_set()
|
/openbmc/qemu/qapi/ |
H A D | block.json | 521 # @boundaries: list of interval boundary values (see description in 524 # io types with intervals corresponding to @boundaries (except for 525 # io types, for which specific boundaries are set through the 528 # @boundaries-read: list of interval boundary values for read latency 531 # @boundaries-read. The parameter has higher priority then 532 # @boundaries. 534 # @boundaries-write: list of interval boundary values for write 537 # @boundaries-zap: list of interval boundary values for zone append 540 # @boundaries-flush: list of interval boundary values for flush 556 # "boundaries": [10, 50, 100] } } [all …]
|
/openbmc/linux/include/uapi/linux/ |
H A D | falloc.h | 21 * filesystem block size boundaries, but this boundary may be larger or 53 * boundaries, but this boundary may be larger or smaller depending on 70 * block size boundaries, but this boundary may be larger or smaller
|
H A D | types.h | 49 * 64-bit values align to 4-byte boundaries on x86_32 (and possibly other 50 * architectures) and to 8-byte boundaries on 64-bit architectures. The new
|
/openbmc/linux/Documentation/hwmon/ |
H A D | gsc-hwmon.rst | 44 PWM value will be scaled depending on 6 temperature boundaries. 45 The tempeature boundaries are read-write and in millidegree Celsius and the
|
H A D | adt7475.rst | 132 speed when the temperature is between the two temperature boundaries. 133 Temperature boundaries are associated to temperature channels rather than
|
/openbmc/linux/drivers/char/ipmi/ |
H A D | ipmi_dmi.c | 182 case 0: /* Byte boundaries */ in dmi_decode_ipmi() 185 case 1: /* 32-bit boundaries */ in dmi_decode_ipmi() 188 case 2: /* 16-byte boundaries */ in dmi_decode_ipmi()
|
/openbmc/linux/Documentation/livepatch/ |
H A D | reliable-stacktrace.rst | 135 At function call boundaries the stack and other unwind state is expected to be 150 boundaries. Note that it may be reliable to unwind across certain 155 have no such cases) should attempt to unwind across exception boundaries, as 307 the case must reject unwinding across exception boundaries unless they can
|
/openbmc/linux/drivers/thermal/ |
H A D | thermal_acpi.c | 17 * the boundaries for the [trips] temperature returned by the 18 * firmware. Any values out of these boundaries may be considered
|
H A D | thermal_trip.c | 40 * The function computes the next temperature boundaries by browsing 102 "new temperature boundaries: %d < x < %d\n", low, high); in __thermal_zone_set_trips()
|
/openbmc/linux/drivers/net/ethernet/intel/i40e/ |
H A D | i40e_lan_hmc.h | 17 * boundaries. If we do not have the width of the variable set to the correct 50 * boundaries. If we do not have the width of the variable set to the correct
|
/openbmc/linux/include/uapi/linux/sched/ |
H A D | types.h | 78 * the utilization boundaries within which it should schedule the task. These 79 * boundaries are valuable hints to support scheduler decisions on both task
|
/openbmc/u-boot/post/drivers/ |
H A D | rtc.c | 19 * o) Passing month boundaries 107 /* Passing month boundaries */ in rtc_post_test()
|
/openbmc/linux/drivers/misc/lkdtm/ |
H A D | stackleak.c | 41 * within the expected task stack boundaries. These tests should never in check_stackleak_irqoff() 42 * fail unless the boundaries are incorrect or we're clobbering the in check_stackleak_irqoff()
|
/openbmc/qemu/host/include/i386/host/ |
H A D | bufferiszero.c.inc | 21 /* Align head/tail to 16-byte boundaries. */ 67 /* Align head/tail to 32-byte boundaries. */
|
/openbmc/linux/arch/powerpc/xmon/ |
H A D | xmon_bpts.S | 7 /* Prefixed instructions can not cross 64 byte boundaries */
|
/openbmc/u-boot/arch/microblaze/include/asm/ |
H A D | processor.h | 9 /* References to section boundaries */
|
/openbmc/linux/Documentation/filesystems/ |
H A D | romfs.rst | 51 byte boundaries for fast access. The minimum space a file will take 146 aligned to 16 byte boundaries, but most hardware devices and the block 181 boundaries, thus it would be possible to directly map a big portion of
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H A D | selection-api-configuration.rst | 39 active cropping area must lie completely inside the capture boundaries. 99 must lie completely inside the crop boundaries and the driver may
|
/openbmc/qemu/docs/specs/ |
H A D | ppc-spapr-numa.rst | 50 to define the relevant performance/distance related boundaries, defining 59 less significant boundaries. Allocated resources that belongs to the 60 same performance boundaries are expected to have relative NUMA distance 63 other. Subsequent boundaries represents greater distances and degraded
|
/openbmc/u-boot/test/py/tests/ |
H A D | test_sleep.py | 26 # 3s isn't too long, but is enough to cross a few second boundaries.
|
/openbmc/linux/arch/sh/include/cpu-sh4/cpu/ |
H A D | sq.h | 17 * to 32-byte boundaries, we need to be sure that all allocations are aligned.
|
/openbmc/linux/arch/microblaze/ |
H A D | Kconfig.platform | 17 boundary. However, if they are aligned on different boundaries
|