/linux/Documentation/trace/rv/ |
H A D | runtime-verification.rst | 19 *online* verification of a system, enabling the *reaction* for unexpected 46 | | Reaction | | 55 react to an unexpected event. The forms of reaction can vary from logging the 59 In Linux terms, a *reactor* is an reaction method available for *RV monitors*. 61 which is already a reaction. In addition, other reactions will be available 187 - Reading returns the current status of the reaction 217 - List available reactors, with the select reaction for the given *MONITOR*
|
H A D | da_monitor_synthesis.rst | 18 trace output as a reaction to event parsing and exceptions, as depicted 31 | | Reaction | |
|
/linux/kernel/ |
H A D | Kconfig.preempt | 43 This allows reaction to interactive events by allowing a 58 preemptible. This allows reaction to interactive events by
|
/linux/kernel/trace/rv/ |
H A D | rv_reactors.c | 7 * A runtime monitor can cause a reaction to the detection of an 17 * the reaction. 46 * - List available reactors, with the select reaction for the given
|
H A D | Kconfig | 59 monitor can cause a reaction to the detection of an exception
|
H A D | rv.c | 14 * monitored system while enabling the reaction for unexpected 43 * of trace output as a reaction for event parsing and exceptions, 56 * | | Reaction | |
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-devices-platform-_UDC_-gadget | 16 Show or set the reaction on the FUA (Force Unit Access) bit in
|
/linux/drivers/gpu/drm/amd/pm/powerplay/hwmgr/ |
H A D | pptable_v1_0.h | 283 USHORT usFanOutputSensitivity; /* Sensitivity of fan reaction to temepature changes */ 303 USHORT usFanOutputSensitivity; /* Sensitivity of fan reaction to temepature changes */ 330 USHORT usFanOutputSensitivity; /* Sensitivity of fan reaction to temepature changes */
|
H A D | vega10_pptable.h | 243 USHORT usFanOutputSensitivity; /* Sensitivity of fan reaction to temepature changes. */
|
/linux/Documentation/process/ |
H A D | 3.Early-stage.rst | 177 reaction, but, instead, little or no reaction at all. The sad truth of the
|
H A D | 6.Followthrough.rst | 218 be hurtful and discouraging, but the community will remember your reaction
|
/linux/arch/x86/boot/ |
H A D | a20.c | 148 return 0; /* BIOS worked, but with delayed reaction */ in enable_a20()
|
/linux/tools/power/cpupower/bench/ |
H A D | README-BENCH | 9 - Identify average reaction time of a governor to CPU load changes
|
/linux/Documentation/driver-api/usb/ |
H A D | hotplug.rst | 46 reaction to a configuration change, from a thread in that subsystem.
|
/linux/drivers/pps/generators/ |
H A D | pps_gen_parport.c | 51 /* calibrated time between a hrtimer event and the reaction */
|
/linux/Documentation/virt/kvm/x86/ |
H A D | mmu.rst | 319 Reaction to events 468 As mentioned in "Reaction to events" above, kvm will cache MMIO
|
/linux/Documentation/hid/ |
H A D | uhid.rst | 121 read() will return a queued output report. No reaction is required to any of
|
/linux/net/ipv4/ |
H A D | tcp_dctcp.c | 141 * packets. Because of EWMA smoothing, PLB reaction can in dctcp_update_alpha()
|
H A D | tcp_lp.c | 18 * o Handle reaction for Early Congestion Indication (ECI) within
|
/linux/Documentation/devicetree/bindings/regulator/ |
H A D | regulator.yaml | 193 provides a defined duration before a more severe reaction to the
|
/linux/include/linux/qed/ |
H A D | qed_rdma_if.h | 186 /* fields for reaction point */
|
/linux/mm/ |
H A D | vmpressure.c | 137 * scanned. This makes it possible to set desired reaction time in vmpressure_calc_level()
|
/linux/drivers/media/platform/samsung/s5p-mfc/ |
H A D | regs-mfc.h | 301 #define S5P_FIMV_ENC_RC_RPARA 0xc5b0 /* rate control reaction coeff */
|
/linux/include/linux/ |
H A D | power_supply.h | 633 * The chemical reaction in the battery will make the voltage go up as 640 * the voltage the same. A chemical reaction in the battery goes on
|
/linux/Documentation/admin-guide/ |
H A D | reporting-issues.rst | 1403 Some reports will not get any reaction from the responsible Linux kernel 1419 proper reaction, you first should reconsider your approach. Did you maybe try 1435 If the second reminder again results in no reaction within a week, try to 1450 getting help are explained in 'Why some issues won't get any reaction or remain 1677 Why some issues won't get any reaction or remain unfixed after being reported
|