Searched full:behaving (Results 1 – 21 of 21) sorted by relevance
96 * will fail. This is a stop gap measure to limit the badly behaving
21 * in response to this driver "mis-behaving" on his machine.
106 * DROPMASTER ioctl, which e.g. logind can call to force a non-behaving
56 /// force a non-behaving master (display compositor) into compliance.
212 * A poorly behaving BPF scheduler can trigger hard lockup by in watchdog_hardlockup_check()737 * A poorly behaving BPF scheduler can live-lock the system into in is_softlockup()
504 * It returns empty tokens, too, behaving exactly like the libc function
416 huge page sizes without any control over the exact sizes, behaving more like
327 * false positives but this did not break correctly behaving devices
675 * behaving just like /dev/zero in pci_mmap_legacy_page_range()
56 * close the subflow with a RST, as it is not behaving as negotiated. in mptcp_parse_option()
82 * task. If the task is behaving as a VMM, then this is will be managed by
2050 * however are automatically behaving without any manual action. in victus_s_powersource_event()
177 /* Is device behaving sane? */
1457 /* aman@sgi.com - account for badly behaving firmware/NIC: in ace_init()
54 /* bulk DMA seems to be behaving for both IN and OUT */
2294 * a well behaving guest driver, it is not expected to allow in handle_ctrl_mq()
4094 * behaving the way we expect it to. in smack_from_secattr()
5145 * behaving correctly. in __ieee80211_beacon_update_cntdwn()
3875 * A poorly behaving BPF scheduler can trigger hard lockup by e.g. putting
5210 * well-behaving guests: They have to keep IRQs disabled at in vmx_inject_nmi()
1272 * wouldn't be resetting if things were behaving normally. The register in r8152_control_msg()