/linux/arch/um/kernel/ |
H A D | time.c | 64 panic("time-travel: time goes backwards %lld -> %lld\n", in time_travel_set_time() 85 printk(KERN_INFO "time-travel: received broadcast 0x%llx\n", bc_message); in _time_travel_print_bc_msg() 158 panic("time-travel external link is broken\n"); in time_travel_handle_message() 160 panic("invalid time-travel message - %d bytes\n", ret); in time_travel_handle_message() 164 WARN_ONCE(1, "time-travel: unexpected message %lld\n", in time_travel_handle_message() 236 panic("time-travel: ACK message has different seqno! op=%d, seq=%d != %d time=%lld\n", in time_travel_ext_req() 313 panic("time-travel: setting time while not running\n"); in __time_travel_propagate_time() 679 panic("time-travel: invalid external ID in string '%s'\n", in time_travel_connect_external() 689 panic("time-travel: failed to connect to external socket %s\n", in time_travel_connect_external() 766 * In basic time-travel mode we still get real interrupts in timer_handler() [all …]
|
H A D | irq.c | 178 * If we're called to only run time-travel handlers then don't in sigio_reg_handler() 181 * despite time-travel not being configured and used. in sigio_reg_handler() 204 /* Flush out pending events that were ignored due to time-travel. */ in _sigio_handler()
|
H A D | um_arch.c | 534 * In external time-travel mode we can't use signals to wake up in init_pm_wake_signal()
|
/linux/include/uapi/linux/ |
H A D | um_timetravel.h | 10 * struct um_timetravel_msg - UM time travel message 164 * enum um_timetravel_schedshm_cap - time travel capabilities of every client 180 * enum um_timetravel_schedshm_flags - time travel flags of every client 195 * DOC: Time travel shared memory overview 197 * The main purpose of the shared memory is to avoid all time travel message 224 * union um_timetravel_schedshm_client - UM time travel client struct 249 * struct um_timetravel_schedshm - UM time travel shared memory struct
|
/linux/Documentation/ABI/testing/ |
H A D | configfs-most | 31 configure type of data that will travel over 86 configure type of data that will travel over 141 configure type of data that will travel over 207 configure type of data that will travel over
|
/linux/arch/um/ |
H A D | Kconfig | 220 prompt "Support time-travel mode (e.g. for test execution)" 225 Enable this option to support time travel inside the UML instance. 239 In UML inf-cpu and ext time-travel mode userspace can run without being
|
/linux/arch/um/os-Linux/ |
H A D | signal.c | 91 * In TT_MODE_EXTERNAL, need to still call time-travel in sig_handler() 367 * time-travel=ext simulation mode, in which case in mark_sigio_pending() 425 * we need to run time-travel handlers even in unblock_signals_hard()
|
/linux/drivers/staging/most/Documentation/ |
H A D | driver_usage.txt | 136 configure type of data that will travel over this channel 207 should travel to the host within one USB transaction need to be written to
|
/linux/arch/um/include/shared/ |
H A D | irq_kern.h | 32 * number, fd, dev_id and time-travel event pointer.
|
H A D | os.h | 334 /* time-travel */
|
/linux/Documentation/translations/zh_CN/maintainer/ |
H A D | pull-requests.rst | 86 latest time travel bus architecture that provides i/o to
|
/linux/Documentation/devicetree/bindings/input/touchscreen/ |
H A D | azoteq,iqs7211.yaml | 323 a finger may travel to be considered a gesture. 330 Specifies the minimum distance a finger must travel to elicit a 338 Specifies the maximum angle (in degrees) a finger may travel to
|
/linux/drivers/net/usb/ |
H A D | r8153_ecm.c | 132 /* Lenovo Powered USB-C Travel Hub (4X90S92381, based on Realtek RTL8153) */
|
/linux/arch/um/drivers/ |
H A D | rtc_kern.c | 37 /* Use this to get correct time in time-travel mode */ in uml_rtc_read_time()
|
H A D | Kconfig | 344 rtcwake, especially in time-travel mode. This driver enables that
|
H A D | chan_kern.c | 112 * In time-travel modes infinite-CPU and external we need to guarantee in open_one_chan()
|
/linux/Documentation/userspace-api/media/v4l/ |
H A D | dev-rds.rst | 11 format, for example the station name or travel information, on an
|
/linux/Documentation/scsi/ |
H A D | scsi_eh.rst | 13 [1] How SCSI commands travel through the midlayer and to EH 30 1. How SCSI commands travel through the midlayer and to EH
|
/linux/Documentation/devicetree/bindings/input/ |
H A D | azoteq,iqs7222.yaml | 291 flick gesture must travel in order to be acknowledged by the 297 to travel before the gesture is rejected by the device. 750 flick gesture must travel in order to be acknowledged by the
|
H A D | iqs269a.yaml | 271 Specifies the number of points across which an axial gesture must travel
|
/linux/Documentation/userspace-api/ioctl/ |
H A D | hdio.rst | 308 travel on DD8-DD15 on little endian machines 311 travel on DD0-DD7 on little endian machines
|
/linux/arch/powerpc/include/asm/ |
H A D | paca.h | 76 * instruction. They must travel together and be properly
|
/linux/Documentation/networking/ |
H A D | dccp.rst | 217 DCCP does not travel through NAT successfully at present on many boxes. This is
|
/linux/Documentation/input/devices/ |
H A D | atarikbd.rst | 56 approximately 200 counts (phase changes or 'clicks') per inch of travel. The 302 cursor keycode after mouse travel exceeding the user specified deltas in
|
/linux/drivers/rtc/ |
H A D | class.c | 172 pr_debug("%s: time travel!\n", dev_name(&rtc->dev)); in rtc_resume()
|