/linux/Documentation/mm/ |
H A D | page_migration.rst | 2 Page migration 5 Page migration allows moving the physical location of pages between 17 Page migration allows a process to manually relocate the node on which its 31 Manual migration is useful if for example the scheduler has relocated 35 manual page migration support. Automatic page migration may be implemented 56 Processes will run with similar performance after migration. 58 Page migration occurs in several steps. First a high level 72 so that it cannot vanish while the page migration occurs. 81 to do the migration. It will call the function to allocate 105 or wait for the migration page table entry to be removed. [all …]
|
H A D | hmm.rst | 23 Finally, the last section presents a new migration helper that allows 104 Shared address space and migration 128 memory for the device memory and second to perform migration. Policy decisions 134 address A triggers a page fault and initiates a migration back to main memory. 295 The overall migration steps are similar to migrating NUMA pages within system 303 be held for the duration of the migration. 336 the LRU), unmapped from the process, and a special migration PTE is 367 This step is where the migration is actually "committed". 378 migration on the CPU side. 389 This step replaces the special migration page table entry with the new [all …]
|
H A D | arch_pgtable_helpers.rst | 257 | is_migration_entry | Tests a migration (read or write) swapped entry | 259 | is_writable_migration_entry | Tests a write migration swapped entry | 261 | make_readable_migration_entry | Creates a read migration swapped entry | 263 | make_writable_migration_entry | Creates a write migration swapped entry |
|
/linux/Documentation/ABI/testing/ |
H A D | debugfs-vfio | 10 What: /sys/kernel/debug/vfio/<device>/migration 15 of vfio devices that support live migration. 16 The debugfs of each vfio device that supports live migration 19 What: /sys/kernel/debug/vfio/<device>/migration/state 23 Description: Read the live migration status of the vfio device. 24 The contents of the state file reflects the migration state
|
H A D | sysfs-kernel-mm-numa | 11 Page migration during reclaim is intended for systems 16 Allowing page migration during reclaim enables these 18 when the fast tier is under pressure. This migration
|
H A D | sysfs-class-rnbd-client | 14 > [access_mode=<ro|rw|migration>] > map_device 27 [access_mode=<ro|rw|migration>] 82 a device to be exported in rw mode only once. The "migration"
|
/linux/tools/testing/selftests/mm/ |
H A D | migration.c | 23 FIXTURE(migration) in FIXTURE() argument 32 FIXTURE_SETUP(migration) in FIXTURE_SETUP() argument 57 FIXTURE_TEARDOWN(migration) in FIXTURE_TEARDOWN() argument 118 TEST_F_TIMEOUT(migration, private_anon, 2*RUNTIME) 143 TEST_F_TIMEOUT(migration, shared_anon, 2*RUNTIME) 178 TEST_F_TIMEOUT(migration, private_anon_thp, 2*RUNTIME)
|
H A D | .gitignore | 14 migration
|
H A D | Makefile | 55 TEST_GEN_FILES += migration 192 $(OUTPUT)/migration: LDLIBS += -lnuma
|
H A D | run_vmtests.sh | 70 - migration 71 invoke move_pages(2) to exercise the migration entry code 443 CATEGORY="migration" run_test ./migration
|
/linux/Documentation/networking/ |
H A D | net_failover.rst | 24 datapath. It also enables hypervisor controlled live migration of a VM with 65 be brought UP during live migration to allow uninterrupted communication. 116 net_failover also enables hypervisor controlled live migration to be supported 120 Here is a sample script that shows the steps to initiate live migration from 165 # Clean up FDB entries after migration completes. 169 On the destination hypervisor, a shared bridge 'br0' is created before migration 173 The following script is executed on the destination hypervisor once migration
|
H A D | failover.rst | 17 datapath. It also allows live migration of VMs with direct attached VFs by
|
/linux/Documentation/admin-guide/cgroup-v1/ |
H A D | memcg_test.rst | 102 The logic is very clear. (About migration, see below) 165 For NUMA, migration is an another special case. To do easy test, cpuset 166 is useful. Following is a sample script to do migration:: 179 In above set, when you moves a task from 01 to 02, page migration to 211 This is an easy way to test page migration, too. 298 9.9 Move charges at task migration 301 Charges associated with a task can be moved along with task migration.
|
/linux/Documentation/virt/kvm/devices/ |
H A D | vm.rst | 291 Allows userspace to stop migration mode, needed for PGSTE migration. 292 Setting this attribute when migration mode is not active will have no 301 Allows userspace to start migration mode, needed for PGSTE migration. 302 Setting this attribute when migration mode is already active will have 306 dirty tracking is disabled on any memslot, migration mode is automatically 310 :Returns: -ENOMEM if there is not enough free memory to start migration mode; 317 Allows userspace to query the status of migration mode. 320 the data itself is either 0 if migration mode is disabled or 1
|
/linux/tools/perf/scripts/python/bin/ |
H A D | sched-migration-report | 3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/sched-migration.py
|
/linux/Documentation/driver-api/ |
H A D | vfio-pci-device-specific-driver-acceptance.rst | 16 state for the purposes of supporting migration. 30 extensions, for example in the case of migration data, how is the
|
/linux/drivers/vfio/pci/mlx5/ |
H A D | Kconfig | 8 This provides migration support for MLX5 devices using the VFIO
|
/linux/Documentation/admin-guide/mm/ |
H A D | userfaultfd.rst | 295 the VM to another physical machine. Since we want the migration to be 304 migration. Postcopy live migration is one form of memory 309 migration to QEMU. 317 It is generally beneficial to run one pass of precopy live migration 318 just before starting postcopy live migration, in order to avoid 321 The implementation of postcopy live migration currently uses one 327 in the destination node, into the socket, and the migration thread of 337 by the parallel QEMU migration thread). 345 migration thread in the QEMU running in the destination node will 353 migration around and a single per-page bitmap has to be maintained in [all …]
|
/linux/drivers/vfio/pci/qat/ |
H A D | Kconfig | 7 This provides migration support for Intel(R) QAT Virtual Function
|
/linux/kernel/irq/ |
H A D | Makefile | 13 obj-$(CONFIG_GENERIC_PENDING_IRQ) += migration.o
|
/linux/fs/proc/ |
H A D | task_mmu.c | 445 bool migration) in smaps_account() argument 485 if ((folio_ref_count(folio) == 1) || migration) { in smaps_account() 559 migration = true; in smaps_pte_entry() 582 bool migration = false; in smaps_pmd_entry() local 590 migration = true; in smaps_pmd_entry() 607 locked, migration); in smaps_pmd_entry() 1418 bool migration = false; in pte_to_pagemap_entry() local 1450 migration = is_migration_entry(entry); in pte_to_pagemap_entry() 1459 if (page && !migration && page_mapcount(page) == 1) in pte_to_pagemap_entry() 1476 bool migration = false; in pagemap_pmd_range() local [all …]
|
/linux/drivers/gpu/drm/amd/amdkfd/ |
H A D | kfd_smi_events.h | 36 unsigned long address, bool migration);
|
/linux/Documentation/arch/powerpc/ |
H A D | dawr-power9.rst | 43 migration from POWER8 to POWER9, at the cost of silently losing the 44 DAWR on the migration.
|
/linux/include/scsi/ |
H A D | viosrp.h | 188 struct mad_migration_cap migration; member
|
/linux/fs/nfs/ |
H A D | Kconfig | 144 bool "NFSv4.1 client support for migration" 149 it can support NFSv4 migration. 151 The NFSv4.1 pieces of the Linux NFSv4 migration implementation are
|