| /linux-6.14.4/Documentation/virt/hyperv/ |
| D | hibernation.rst | 40 Resuming a hibernated guest VM can be more challenging than with
53 details on this scenario and its limitations in the "Resuming on a
61 done when resuming execution in the hibernation image. If a VM is
65 mismatches when resuming the hibernation image, undefined behavior
110 Linux orchestration of hibernation and of resuming from hibernation.
135 When resuming existing primary VMBus channels, the newly offered
277 Resuming on a Different VM
316 * vPCI devices do not have the same instance GUIDs when resuming
334 similar special actions could be taken when resuming on a different VM
|
| /linux-6.14.4/Documentation/admin-guide/pm/ |
| D | suspend-flows.rst | 126 1. Resuming timekeeping and unfreezing the scheduler tick.
137 2. Resuming devices and restoring the working-state configuration of IRQs.
247 2. Resuming core system components.
257 4. Resuming devices and restoring the working-state configuration of IRQs.
|
| /linux-6.14.4/Documentation/power/ |
| D | suspend-and-interrupts.rst | 9 Suspending and Resuming Device IRQs
30 of resuming devices (that is, before starting to execute ->resume_early
38 suspend-resume cycle, including the "noirq" phases of suspending and resuming
|
| D | swsusp.rst | 94 to standby mode. Later resuming the machine the saved state is loaded back to
105 the resuming. If the option `hibernate=nocompress` is specified as a boot
257 After resuming, system is paging heavily, leading to very bad interactivity.
467 before suspending; then remount them after resuming.
|
| D | userland-swsusp.rst | 160 The suspending and resuming utilities MUST lock themselves in memory,
189 The resuming utility SHOULD NOT attempt to mount any file systems that could
|
| /linux-6.14.4/drivers/vfio/ |
| D | vfio_main.c | 669 * RESUMING -> STOP in vfio_mig_get_next_state()
670 * STOP -> RESUMING in vfio_mig_get_next_state()
706 * PRE_COPY -> RUNNING -> RUNNING_P2P -> STOP -> RESUMING in vfio_mig_get_next_state()
709 * PRE_COPY_P2P -> RUNNING_P2P -> STOP -> RESUMING in vfio_mig_get_next_state()
710 * RESUMING -> STOP -> RUNNING_P2P in vfio_mig_get_next_state()
711 * RESUMING -> STOP -> RUNNING_P2P -> PRE_COPY_P2P in vfio_mig_get_next_state()
712 * RESUMING -> STOP -> RUNNING_P2P -> RUNNING in vfio_mig_get_next_state()
713 * RESUMING -> STOP -> RUNNING_P2P -> RUNNING -> PRE_COPY in vfio_mig_get_next_state()
714 * RESUMING -> STOP -> STOP_COPY in vfio_mig_get_next_state()
717 * RUNNING -> RUNNING_P2P -> STOP -> RESUMING in vfio_mig_get_next_state()
[all …]
|
| D | debugfs.c | 43 seq_puts(seq, "RESUMING\n"); in vfio_device_state_read()
|
| /linux-6.14.4/Documentation/admin-guide/cgroup-v1/ |
| D | freezer-subsystem.rst | 24 and resuming tasks in userspace. Both of these signals are observable
49 have a problem with this method of stopping and resuming tasks.
|
| /linux-6.14.4/net/bluetooth/ |
| D | msft.c | 129 __u8 resuming; member
591 msft->resuming = true; in reregister_monitor()
604 msft->resuming = false; in reregister_monitor()
658 msft->resuming = true; in msft_do_open()
1159 if (msft->resuming || msft->suspending) in msft_add_monitor_pattern()
1173 if (msft->resuming || msft->suspending) in msft_remove_monitor()
|
| /linux-6.14.4/drivers/mfd/ |
| D | max77686.c | 238 * while suspended it will be handled before resuming I2C. in max77686_suspend()
241 * an interrupt occurs before resuming I2C bus controller. in max77686_suspend()
|
| /linux-6.14.4/arch/arm/mach-s3c/ |
| D | pm-core-s3c64xx.h | 62 * problems between going to sleep and resuming. in samsung_pm_saved_gpios()
|
| D | irq-pm-s3c64xx.c | 87 S3C_PMDBG("%s: resuming IRQs\n", __func__); in s3c64xx_irq_pm_resume()
|
| /linux-6.14.4/tools/testing/selftests/kvm/x86/ |
| D | hyperv_evmcs.c | 130 * NMI forces L2->L1 exit, resuming L2 and hope that EVMCS is in guest_code()
288 /* Force immediate L2->L1 exit before resuming */ in main()
|
| D | vmx_apic_access_test.c | 15 * this situation, so resuming L2 should result in a KVM exit for
|
| /linux-6.14.4/Documentation/devicetree/bindings/dma/ |
| D | sprd,sc9860-dma.yaml | 12 system power without resuming system by DMA interrupts if AGCP DMA
|
| /linux-6.14.4/scripts/gdb/linux/ |
| D | genpd.py | 31 "resuming",
|
| /linux-6.14.4/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pmc.txt | 41 supports disabling and resuming devices at any time.
|
| /linux-6.14.4/arch/arm/mach-pxa/ |
| D | pxa3xx.c | 99 * PXA3xx development kits assumes that the resuming process continues
119 /* resuming from D2 requires the HSIO2/BOOT/TPM clocks enabled */ in pxa3xx_cpu_pm_suspend()
|
| /linux-6.14.4/Documentation/devicetree/bindings/watchdog/ |
| D | samsung-wdt.yaml | 13 The Samsung's Watchdog controller is used for resuming system operation
|
| /linux-6.14.4/Documentation/driver-api/usb/ |
| D | power-management.rst | 74 However some devices have the capability of resuming by themselves, or
80 event. Examples include a suspended keyboard resuming when a key is
81 pressed, or a suspended USB hub resuming when a device is plugged in.
433 suspending and resuming correctly. This is exactly equivalent to
682 Resuming the child device when the parent port regains power resolves those
|
| /linux-6.14.4/drivers/usb/host/ |
| D | uhci-hub.c | 38 /* suspend/resume bits: port suspended or port resuming */
175 * after the resuming period is over. */ in uhci_check_ports()
|
| /linux-6.14.4/drivers/usb/usbip/ |
| D | vhci.h | 108 unsigned resuming:1; member
|
| /linux-6.14.4/drivers/hid/intel-thc-hid/intel-thc/ |
| D | intel-thc-dev.h | 64 * @i2c_subip_regs: the copy of THC I2C sub-system registers for resuming restore
|
| /linux-6.14.4/arch/arm/kernel/ |
| D | suspend.c | 46 * the MMU-enable code, required for resuming. On successful in cpu_suspend()
|
| /linux-6.14.4/Documentation/driver-api/pm/ |
| D | devices.rst | 269 Suspending or resuming the system is done in several phases. Different phases
420 low-power state. Instead, the PM core will unwind its actions by resuming all
427 When resuming from freeze, standby or memory sleep, the phases are:
585 Resuming from hibernation is, again, more complicated than resuming from a sleep
598 in resuming from hibernation. In fact, the restore kernel may be completely
|