Home
last modified time | relevance | path

Searched full:migration (Results 1 – 25 of 501) sorted by relevance

12345678910>>...21

/linux-6.14.4/Documentation/mm/
Dpage_migration.rst2 Page migration
5 Page migration allows moving the physical location of pages between
13 The main intent of page migration is to reduce the latency of memory accesses
17 Page migration allows a process to manually relocate the node on which its
23 Page migration functions are provided by the numactl package by Andi Kleen
27 migration. cat ``/proc/<pid>/numa_maps`` allows an easy review of where the
31 Manual migration is useful if for example the scheduler has relocated
35 manual page migration support. Automatic page migration may be implemented
52 Page migration allows the preservation of the relative location of pages
53 within a group of nodes for all migration techniques which will preserve a
[all …]
Dhmm.rst23 Finally, the last section presents a new migration helper that allows
104 Shared address space and migration
124 main memory to device memory using existing migration mechanisms and everything
128 memory for the device memory and second to perform migration. Policy decisions
131 Note that any CPU access to a device page triggers a page fault and a migration
134 address A triggers a page fault and initiates a migration back to main memory.
260 Migration to and from device 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
[all …]
/linux-6.14.4/tools/testing/selftests/mm/
Dmigration.c3 * The main purpose of the tests here is to exercise the migration entry code
23 FIXTURE(migration) in FIXTURE() argument
32 FIXTURE_SETUP(migration) in FIXTURE_SETUP() argument
57 FIXTURE_TEARDOWN(migration) in FIXTURE_TEARDOWN() argument
84 /* Migration is best effort; try again */ in migrate()
119 * Basic migration entry testing. One thread will move pages back and forth
121 * migration entry wait paths in the kernel.
123 TEST_F_TIMEOUT(migration, private_anon, 2*RUNTIME)
148 TEST_F_TIMEOUT(migration, shared_anon, 2*RUNTIME)
181 * Tests the pmd migration entry paths.
[all …]
/linux-6.14.4/drivers/gpu/drm/xe/
Dxe_sriov_vf.c52 * the MIGRATED interrupt and schedules post-migration recovery worker.
107 * | | migration fixups -------[ ]
132 INIT_WORK(&xe->sriov.vf.migration.worker, migration_worker_func); in xe_sriov_vf_init_early()
139 * After migration, we need to re-query all VF configuration to make sure
164 * Return: True if migration recovery worker will soon be running. Any worker currently
169 return xe->sriov.vf.migration.gt_flags != 0 || in vf_post_migration_imminent()
170 work_pending(&xe->sriov.vf.migration.worker); in vf_post_migration_imminent()
196 drm_dbg(&xe->drm, "migration recovery in progress\n"); in vf_post_migration_recovery()
207 drm_notice(&xe->drm, "migration recovery ended\n"); in vf_post_migration_recovery()
211 drm_dbg(&xe->drm, "migration recovery deferred\n"); in vf_post_migration_recovery()
[all …]
Dxe_sriov_types.h67 /** @migration: VF Migration state data */
69 /** @migration.worker: VF migration recovery worker */
71 /** @migration.gt_flags: Per-GT request flags for VF migration recovery */
73 } migration; member
Dxe_gt_sriov_pf_types.h43 * @migration: migration data.
51 struct xe_gt_sriov_pf_migration migration; member
/linux-6.14.4/Documentation/ABI/testing/
Ddebugfs-vfio10 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
Ddebugfs-hisi-migration1 What: /sys/kernel/debug/vfio/<device>/migration/hisi_acc/dev_data
6 required for device live migration. These data include device
9 is defined by the live migration driver.
11 What: /sys/kernel/debug/vfio/<device>/migration/hisi_acc/migf_data
15 Description: Read the data from the last completed live migration.
19 What: /sys/kernel/debug/vfio/<device>/migration/hisi_acc/cmd_state
Dsysfs-kernel-mm-numa11 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
/linux-6.14.4/tools/testing/selftests/kvm/
Drseq_test.c33 * Any bug related to task migration is likely to be timing-dependent; perform
87 * that a migration may have occurred in between rseq and sched in migration_worker()
88 * CPU ID reads. An odd sequence count indicates a migration in migration_worker()
90 * a migration occurred since the count was last read. in migration_worker()
112 * 1. To allow sched_setaffinity() to prompt migration before in migration_worker()
129 * before the next round of migration. The test's check on in migration_worker()
130 * the rseq CPU ID must wait for migration to complete in in migration_worker()
132 * will be missed if the next migration starts before the in migration_worker()
193 "Only one usable CPU, task migration not possible"); in calc_min_max_cpu()
252 * Verify rseq's CPU matches sched's CPU. Ensure migration in main()
[all …]
/linux-6.14.4/tools/testing/selftests/kvm/s390/
Dcmma_test.c3 * Test for s390x CMMA migration
191 TEST_ASSERT(!r, "enabling migration mode failed r=%d errno=%d", r, errno); in enable_migration_mode()
204 TEST_ASSERT(!r, "getting migration mode status failed r=%d errno=%d", r, errno); in is_migration_mode_on()
243 /* GET_CMMA_BITS without migration mode and without peeking should fail */ in test_get_cmma_basic()
248 /* GET_CMMA_BITS without migration mode and with peeking should work */ in test_get_cmma_basic()
279 /* enabling migration mode on a VM without memory should fail */ in test_migration_mode()
283 TEST_ASSERT(!is_migration_mode_on(vm), "migration mode should still be off"); in test_migration_mode()
300 /* migration mode when memslots have dirty tracking off should fail */ in test_migration_mode()
304 TEST_ASSERT(!is_migration_mode_on(vm), "migration mode should still be off"); in test_migration_mode()
310 /* enabling migration mode should work now */ in test_migration_mode()
[all …]
/linux-6.14.4/mm/
Dmigrate_device.c3 * Device Memory Migration functionality.
173 * any kind of migration. Side effect is that it "freezes" the in migrate_vma_collect_pmd()
187 * migration as it is only best effort anyway. in migrate_vma_collect_pmd()
189 * If we can lock the folio it's safe to set up a migration entry in migrate_vma_collect_pmd()
191 * single process setting up the migration entry now is an in migrate_vma_collect_pmd()
222 /* Setup special migration page table entry */ in migrate_vma_collect_pmd()
290 * @migrate: migrate struct containing all migration information
322 * folio_migrate_mapping(), except that here we allow migration of a
359 * Unmaps pages for migration. Returns number of source pfns marked as
439 * migrate_vma_unmap() - replace page mapping with special migration pte entry
[all …]
Dmigrate.c3 * Memory Migration functionality - linux/mm/migrate.c
7 * Page migration was first developed in the context of the memory hotplug
8 * project. The main authors of the migration code are:
81 * compaction threads can race against page migration functions in isolate_movable_page()
85 * being (wrongly) re-isolated while it is under migration, in isolate_movable_page()
127 * from where they were once taken off for compaction/migration.
237 * Restore a potential migration pte to a working pte entry
259 /* PMD-mapped THP migration entry */ in remove_migration_pte()
345 * Get rid of all migration entries and replace them by
369 * Something used the pte of a page under migration. We need to
[all …]
/linux-6.14.4/include/linux/
Dmigrate.h17 * - negative errno on page migration failure;
18 * - zero on page migration success;
24 * struct movable_operations - Driver page migration
38 * If page migration is successful, the driver should call
41 * -EAGAIN. The VM interprets this as a temporary migration failure and
42 * will retry it later. Any other error value is a permanent migration
43 * failure and migration will not be retried.
48 * If migration fails on the isolated page, the VM informs the driver
49 * that the page is no longer a candidate for migration by calling
Dballoon_compaction.h7 * Balloon page migration makes use of the general non-lru movable page
11 * page->mapping is used in context of non-lru page migration to reference
12 * the address space operations for page isolation/migration/compaction.
17 * and safely perform balloon's page compaction and migration we must, always,
33 * compaction / migration.
51 * have to cope for page compaction / migration, as well as it serves the
55 unsigned long isolated_pages; /* # of isolated pages for migration */
Dvfio.h186 * struct vfio_migration_ops - VFIO bus device driver migration callbacks
188 * @migration_set_state: Optional callback to change the migration state for
189 * devices that support migration. It's mandatory for
190 * VFIO_DEVICE_FEATURE_MIGRATION migration support.
193 * of stream or error whenever the migration FSM leaves a data transfer
195 * @migration_get_state: Optional callback to get the migration state for
196 * devices that support migration. It's mandatory for
197 * VFIO_DEVICE_FEATURE_MIGRATION migration support.
200 * VFIO_DEVICE_FEATURE_MIGRATION migration support.
/linux-6.14.4/drivers/gpu/drm/i915/gem/selftests/
Di915_gem_migrate.c137 * Migration will implicitly unbind (asynchronously) any bound in lmem_pages_migrate_one()
144 pr_err("Object failed migration to smem\n"); in lmem_pages_migrate_one()
163 pr_err("Object failed migration to lmem\n"); in lmem_pages_migrate_one()
269 /* Finally sync migration and check content. */ in __igt_lmem_pages_migrate()
360 * This subtest tests that unbinding at migration is indeed performed
362 * that spinner to have terminated. Before each migration we bind a
363 * vma, which should then be async unbound by the migration operation.
368 * Note that each async bind operation is awaiting the previous migration
369 * due to the moving fence resulting from the migration.
443 * arming the migration error check and block async migration. This
/linux-6.14.4/Documentation/networking/
Dnet_failover.rst24 datapath. It also enables hypervisor controlled live migration of a VM with
65 be brought UP during live migration to allow uninterrupted communication.
113 Live Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode
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
/linux-6.14.4/include/uapi/linux/
Dvmclock-abi.h7 * live migration, which other clock enlightenments do not.
15 * live migration there is a step change in the frequency, with no warning.
22 * host before migration is invalid, and needs to be redone on the new host.
25 * guest that live migration has occurred. This allows the guest to know that
36 * immediately after live migration, rather than having to pause operations
50 * migration problem seems a little less than fit for purpose. For that
84 * counter is disrupted, for example on live migration. This lets
/linux-6.14.4/Documentation/admin-guide/cgroup-v1/
Dmemcg_test.rst102 The logic is very clear. (About migration, see below)
129 7. Page Migration
162 9.3 Migration
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-6.14.4/kernel/cgroup/
Dcgroup-internal.h108 /* used to track tasks and csets during migration */
123 * Before migration is committed, the target migration tasks are on
126 * or ->dst_csets depending on whether migration is committed.
136 /* migration context also tracks preloading */
140 * atomic success or failure on actual migration.
148 /* subsystems affected by migration */
/linux-6.14.4/Documentation/admin-guide/mm/
Duserfaultfd.rst295 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-6.14.4/drivers/vfio/pci/virtio/
DKconfig7 This provides migration support for VIRTIO NET PCI VF devices
8 using the VFIO framework. Migration support requires the
13 Migration support in this driver relies on dirty page tracking
/linux-6.14.4/kernel/time/
Dtimer_migration.h22 * struct tmigr_group - timer migration hierarchy group
76 * struct tmigr_cpu - timer migration per CPU group
84 * idle before the timer migration hierarchy hotplug AP is
87 * @idle: Indicates whether the CPU is idle in the timer migration
92 * @wakeup: Stores the first timer when the timer migration
/linux-6.14.4/arch/powerpc/platforms/pseries/
Dvas.c433 * The migration SUSPEND thread sets migration_in_progress and in vas_allocate_window()
438 * initiates the migration. in vas_allocate_window()
533 * lost the credit or with migration. So just remove the entry in vas_deallocate_window()
677 * For partition migration, reopen all windows that are closed in reconfig_open_windows()
691 * Open windows if they are closed only with migration or in reconfig_open_windows()
701 * This window is closed with DLPAR and migration events. in reconfig_open_windows()
704 * migration notifier. So the user space can issue DLPAR in reconfig_open_windows()
705 * CPU hotplug while migration in progress. In this case in reconfig_open_windows()
777 * or for migration before. Go for next window. in reconfig_close_windows()
778 * For migration, nothing to do since this window in reconfig_close_windows()
[all …]

12345678910>>...21