Home
last modified time | relevance | path

Searched full:evaluating (Results 1 – 25 of 103) sorted by relevance

12345

/linux-6.12.1/tools/perf/Documentation/
Dperf-bench.txt79 Suite for evaluating performance of scheduler and IPC mechanisms.
168 Suite for evaluating performance of core system call throughput (both usecs/op and ops/sec metrics).
176 Suite for evaluating performance of simple memory copy in various ways.
200 Suite for evaluating performance of simple memory set in various ways.
226 Suite for evaluating NUMA workloads.
231 Suite for evaluating hash tables.
234 Suite for evaluating wake calls.
237 Suite for evaluating parallel wake calls.
240 Suite for evaluating requeue calls.
243 Suite for evaluating futex lock_pi calls.
[all …]
/linux-6.12.1/net/ipv4/
Dtcp_westwood.c37 u32 snd_una; /* used for evaluating the number of acked bytes */
115 * it. If so it calls filter for evaluating bandwidth.
177 * This function evaluates cumul_ack for evaluating bk in case of
/linux-6.12.1/drivers/platform/x86/amd/pmf/
DKconfig28 information after evaluating a ACPI method and the information is stored
/linux-6.12.1/drivers/acpi/acpica/
Ddbcmds.c795 acpi_os_printf("Evaluating _PRT\n"); in acpi_db_device_resources()
822 acpi_os_printf("Evaluating _CRS\n"); in acpi_db_device_resources()
883 acpi_os_printf("Evaluating _SRS\n"); in acpi_db_device_resources()
900 acpi_os_printf("Evaluating _PRS\n"); in acpi_db_device_resources()
932 acpi_os_printf("Evaluating _AEI\n"); in acpi_db_device_resources()
/linux-6.12.1/drivers/virt/
Dvmgenid.c64 ACPI_EXCEPTION((AE_INFO, status, "Evaluating ADDR")); in vmgenid_add_acpi()
/linux-6.12.1/drivers/acpi/
Dpci_slot.c171 * we want to check _STA before evaluating _SUN.
Dthermal.c55 * when re-evaluating the AML code.
696 * the evaluating order of _TMP and _CRT/_HOT/_PSV/_ACx.
/linux-6.12.1/Documentation/cpu-freq/
Dcpufreq-stats.rst60 useful for evaluating system behaviour under different governors without the
/linux-6.12.1/drivers/platform/x86/
Dasus-wireless.c59 acpi_handle_debug(handle, "Evaluating method %s, parameter %#x\n", in asus_wireless_method()
Dquickstart.c189 * We have to initialize the device wakeup before evaluating GHID because in quickstart_probe()
/linux-6.12.1/drivers/gpu/drm/i915/
Di915_scheduler_types.h54 * We let a new context run for a small amount of time before re-evaluating
/linux-6.12.1/drivers/platform/surface/aggregator/
Dssh_packet_layer.h66 * @rx.buf: Buffer for evaluating data on receiver thread.
/linux-6.12.1/drivers/usb/storage/
Dprotocol.c78 /* XXX We should be constantly re-evaluating the need for these */ in usb_stor_ufi_command()
/linux-6.12.1/arch/x86/include/asm/
Dsev-common.h145 * without evaluating the impact to stack usage.
/linux-6.12.1/drivers/platform/surface/
Dsurfacepro3_button.c170 * If evaluating the _DSM fails, the method is not present. This means in surface_button_check_MSHW0040()
/linux-6.12.1/tools/include/linux/
Dcompiler.h78 * a constant expression, most importantly without evaluating the argument.
/linux-6.12.1/Documentation/security/
Dipe.rst130 IPE was designed after evaluating existing integrity policy solutions
356 and investigation times when policy failures are observed while evaluating
/linux-6.12.1/include/linux/
Dstackdepot.h100 * be done when evaluating kernel boot parameters.
Dtick.h189 * Check if a CPU is part of the nohz_full subset. Arrange for evaluating
/linux-6.12.1/Documentation/devicetree/bindings/arm/
Darm,vexpress-juno.yaml83 V2M-Juno) was introduced as a vehicle for evaluating big.LITTLE on
/linux-6.12.1/Documentation/trace/coresight/
Dcoresight-config.rst225 to substitute the syntax for the name when evaluating the command::
/linux-6.12.1/scripts/
Ddocumentation-file-ref-check143 # Check if exists, evaluating wildcards
/linux-6.12.1/drivers/platform/x86/dell/
Ddell-smbios-wmi.c63 dev_dbg(&wdev->dev, "evaluating: %u/%u [%x,%x,%x,%x]\n", in run_smbios_call()
/linux-6.12.1/include/linux/regulator/
Ddriver.h514 * @irq_off_ms: The time which IRQ is kept disabled before re-evaluating the
554 * not retrigger evaluating what events are active or resending
/linux-6.12.1/Documentation/process/
D6.Followthrough.rst187 after it's merged. The next time you post a patch, they will be evaluating

12345