Home
last modified time | relevance | path

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

12345678910>>...15

/linux/drivers/gpu/drm/xe/
H A Dxe_sriov_pf_migration.c24 return &xe->sriov.pf.vfs[vfid].migration; in pf_pick_migration()
28 * xe_sriov_pf_migration_waitqueue() - Get waitqueue for migration.
32 * Return: pointer to the migration waitqueue.
40 * xe_sriov_pf_migration_supported() - Check if SR-IOV VF migration is supported by the device
43 * Return: true if migration is supported, false otherwise
49 return IS_ENABLED(CONFIG_DRM_XE_DEBUG) || !xe->sriov.pf.migration.disabled; in xe_sriov_pf_migration_supported()
53 * xe_sriov_pf_migration_disable() - Turn off SR-IOV VF migration support on PF.
67 xe_sriov_notice(xe, "migration %s: %pV\n", in xe_sriov_pf_migration_disable()
73 xe->sriov.pf.migration.disabled = true; in xe_sriov_pf_migration_disable()
84 struct xe_sriov_migration_state *migration = arg; in pf_migration_cleanup() local
[all …]
H A Dxe_gt_sriov_pf_migration.c38 return &gt->sriov.pf.vfs[vfid].migration; in pf_pick_gt_migration()
116 * xe_gt_sriov_pf_migration_ggtt_save() - Save VF GGTT migration data.
134 * xe_gt_sriov_pf_migration_ggtt_restore() - Restore VF GGTT migration data.
137 * @data: the &xe_sriov_packet containing migration data
303 * xe_gt_sriov_pf_migration_guc_save() - Save VF GuC migration data.
345 * xe_gt_sriov_pf_migration_guc_restore() - Restore VF GuC migration data.
348 * @data: the &xe_sriov_packet containing migration data
473 * xe_gt_sriov_pf_migration_mmio_save() - Save VF MMIO migration data.
491 * xe_gt_sriov_pf_migration_mmio_restore() - Restore VF MMIO migration data.
494 * @data: the &xe_sriov_packet containing migration data
[all …]
H A Dxe_sriov_pf_migration_types.h14 * struct xe_sriov_pf_migration - Xe device level VF migration data
17 /** @disabled: indicates whether VF migration feature is disabled */
22 * struct xe_sriov_migration_state - Per VF device-level migration related data
27 /** @lock: Mutex protecting the migration data */
H A Dxe_sriov_vf_ccs_types.h21 * struct xe_sriov_vf_ccs_ctx - VF CCS migration context data.
27 /** @mig_q: exec queues used for migration */
38 * struct xe_sriov_vf_ccs - The VF CCS migration support data.
/linux/Documentation/mm/
H A 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 …]
/linux/tools/testing/selftests/mm/
H A Dmigration.c3 * The main purpose of the tests here is to exercise the migration entry code
27 FIXTURE(migration) in FIXTURE() argument
47 FIXTURE_SETUP(migration) in FIXTURE_SETUP() argument
78 FIXTURE_TEARDOWN(migration) in FIXTURE_TEARDOWN() argument
84 static bool kill_children(FIXTURE_DATA(migration) * self) in kill_children()
135 /* Migration is best effort. Try again */ in migrate()
165 * Basic migration entry testing. One thread will move pages back and forth
167 * migration entry wait paths in the kernel.
169 TEST_F_TIMEOUT(migration, private_anon, 2*RUNTIME)
191 TEST_F_TIMEOUT(migration, shared_anon, 2*RUNTIME)
[all …]
/linux/Documentation/ABI/testing/
H A 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
27 What: /sys/kernel/debug/vfio/<device>/migration/features
31 Description: Read the migration features of the vfio device.
H A 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/tools/testing/selftests/kvm/
H A 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()
110 * 1. To allow sched_setaffinity() to prompt migration before in migration_worker()
127 * before the next round of migration. The test's check on in migration_worker()
128 * the rseq CPU ID must wait for migration to complete in in migration_worker()
130 * will be missed if the next migration starts before the in migration_worker()
191 "Only one usable CPU, task migration not possible"); in calc_min_max_cpu()
265 * Verify rseq's CPU matches sched's CPU. Ensure migration in main()
[all...]
/linux/tools/testing/selftests/kvm/s390/
H A Dcmma_test.c3 * Test for s390x CMMA migration
197 TEST_ASSERT(!r, "enabling migration mode failed r=%d errno=%d", r, errno); in enable_migration_mode()
210 TEST_ASSERT(!r, "getting migration mode status failed r=%d errno=%d", r, errno); in is_migration_mode_on()
249 /* GET_CMMA_BITS without migration mode and without peeking should fail */ in test_get_cmma_basic()
254 /* GET_CMMA_BITS without migration mode and with peeking should work */ in test_get_cmma_basic()
285 /* enabling migration mode on a VM without memory should fail */ in test_migration_mode()
289 TEST_ASSERT(!is_migration_mode_on(vm), "migration mode should still be off"); in test_migration_mode()
306 /* migration mode when memslots have dirty tracking off should fail */ in test_migration_mode()
310 TEST_ASSERT(!is_migration_mode_on(vm), "migration mode should still be off"); in test_migration_mode()
316 /* enabling migration mode should work now */ in test_migration_mode()
[all …]
/linux/Documentation/gpu/rfc/
H A Dgpusvm.rst11 * Rely only on core MM concepts (migration PTEs, page references, and
20 * Partial migration is supported (i.e., a subset of pages attempting to
43 exception is holding a BO's dma-resv lock during the initial migration
47 migration policy requiring GPU access to occur in GPU memory.
89 :doc: Migration
113 * Higher order dma mapping for migration
114 * 4k dma mapping adversely affects migration performance on Intel
117 * Driver side madvise implementation and migration policies
/linux/mm/
H A 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:
87 * If we enable page migration for a page of a certain type by marking in page_movable_ops()
92 /* Only balloon page migration sets PageOffline pages movable. */ in page_movable_ops()
101 * isolate_movable_ops_page - isolate a movable_ops page for migration
105 * Try to isolate a movable_ops page for migration. Will fail if the page is
106 * not a movable_ops page, if the page is already isolated for migration
148 * compaction threads can race against page migration functions in isolate_movable_ops_page()
152 * being (wrongly) re-isolated while it is under migration, in isolate_movable_ops_page()
[all …]
H A Dmigrate_device.c3 * Device Memory Migration functionality.
128 * @start: start address of the range for migration
129 * @end: end address of the range for migration
133 * Collect the huge pmd entry at @pmdp for migration and set the
135 * migration will occur at HPAGE_PMD granularity
388 * any kind of migration. Side effect is that it "freezes" the in migrate_vma_collect_pmd()
402 * migration as it is only best effort anyway. in migrate_vma_collect_pmd()
404 * If we can lock the folio it's safe to set up a migration entry in migrate_vma_collect_pmd()
406 * single process setting up the migration entry now is an in migrate_vma_collect_pmd()
439 /* Setup special migration page table entry */ in migrate_vma_collect_pmd()
[all …]
/linux/drivers/gpu/drm/i915/gem/selftests/
H A 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/Documentation/networking/
H A 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.
112 Live Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode
115 net_failover also enables hypervisor controlled live migration to be supported
119 Here is a sample script that shows the steps to initiate live migration from
164 # Clean up FDB entries after migration completes.
168 On the destination hypervisor, a shared bridge 'br0' is created before migration
172 The following script is executed on the destination hypervisor once migration
/linux/Documentation/arch/powerpc/
H A Dvpa-dtl.rst149 …migration/9 67 [009] 105373.359903: sched:sched_waking: comm=perf pid=134…
150 …migration/9 67 [009] 105373.359904: sched:sched_migrate_task: comm=perf pid=134…
151 …migration/9 67 [009] 105373.359907: sched:sched_stat_runtime: comm=migration/9 …
152 …migration/9 67 [009] 105373.359908: sched:sched_switch: prev_comm=migrati…
156 …13418 [010] 105373.360052: sched:sched_waking: comm=migration/10 pid=72 prio=0…
/linux/Documentation/admin-guide/cgroup-v1/
H A Dmemcg_test.rst100 The logic is very clear. (About migration, see below)
127 7. Page Migration
160 9.3 Migration
163 For NUMA, migration is an another special case. To do easy test, cpuset
164 is useful. Following is a sample script to do migration::
177 In above set, when you moves a task from 01 to 02, page migration to
209 This is an easy way to test page migration, too.
296 9.9 Move charges at task migration
299 Charges associated with a task can be moved along with task migration.
/linux/drivers/gpu/drm/
H A Ddrm_pagemap.c22 * to handle access (and in the future migration) between devices implementing
28 * migration is best effort only and may thus fail. The implementation should
34 * DOC: Migration
36 * Migration granularity typically follows the GPU SVM range requests, but
157 * drm_pagemap_migration_unlock_put_folio() - Put a migration folio
169 * drm_pagemap_migration_unlock_put_pages() - Put migration pages
219 * drm_pagemap_migrate_map_device_private_pages() - Map device private migration
220 * pages for GPU SVM migration
221 * @dev: The device performing the migration.
227 * @mdetails: Details governing the migration behaviour.
[all …]
/linux/include/drm/
H A Ddrm_pagemap.h183 * allocations and perform operations such as migration between device memory and system
197 * @populate_devmem_pfn: Populate device memory PFN (required for migration)
210 * @copy_to_devmem: Copy to device memory (required for migration)
214 * @pre_migrate_fence: dma-fence to wait for before migration start.
229 * @copy_to_ram: Copy to system RAM (required for migration)
233 * @pre_migrate_fence: dma-fence to wait for before migration start.
315 * @pre_migrate_fence: Fence to wait for or pipeline behind before migration starts.
330 * struct drm_pagemap_migrate_details - Details to govern migration.
/linux/drivers/vfio/pci/pds/
H A Dcmds.c192 dev_dbg(dev, "vf%u: Get migration status\n", pds_vfio->vf_id); in pds_vfio_get_lm_state_size_cmd()
295 dev_dbg(&pdev->dev, "vf%u: Get migration state\n", pds_vfio->vf_id); in pds_vfio_get_lm_state_cmd()
301 dev_err(&pdev->dev, "failed to map save migration file: %pe\n", in pds_vfio_get_lm_state_cmd()
311 dev_err(&pdev->dev, "failed to get migration state: %pe\n", in pds_vfio_get_lm_state_cmd()
333 dev_dbg(&pdev->dev, "vf%u: Set migration state\n", pds_vfio->vf_id); in pds_vfio_set_lm_state_cmd()
340 "failed to map restore migration file: %pe\n", in pds_vfio_set_lm_state_cmd()
350 dev_err(&pdev->dev, "failed to set migration state: %pe\n", in pds_vfio_set_lm_state_cmd()
376 dev_warn(dev, "Invalid host VF migration status, %d\n", in pds_vfio_send_host_vf_lm_status_cmd()
383 dev_warn(dev, "failed to send host VF migration status: %pe\n", in pds_vfio_send_host_vf_lm_status_cmd()
H A Dpci_drv.c25 * Documentation states that the kernel migration driver must not in pds_vfio_recovery()
31 * 1. Migration is in progress, which will cause the next step of in pds_vfio_recovery()
32 * the migration to fail. in pds_vfio_recovery()
62 * error and may cause migration to fail. in pds_vfio_pci_notify_handler()
/linux/include/uapi/linux/
H A Dvfio.h1015 * Indicates the device can support the migration API through
1045 * Upon VFIO_DEVICE_FEATURE_SET, execute a migration state change on the VFIO
1049 * The kernel migration driver must fully transition the device to the new state
1052 * The kernel migration driver must not generate asynchronous device state
1064 * this FD when it is finished. The user must consider the migration data stream
1069 * Upon VFIO_DEVICE_FEATURE_GET, get the current migration state of the VFIO
1079 * The device migration Finite State Machine is described by the enum
1080 * vfio_device_mig_state. Some of the FSM arcs will create a migration data
1081 * transfer session by returning a FD, in this case the migration data will
1107 * migration driver must accept and respond to interaction to support external
[all …]
/linux/Documentation/virt/kvm/devices/
H A Dvm.rst291 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 Dsched-migration-report2 # description: sched migration overview
3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/sched-migration.py
/linux/drivers/vfio/pci/xe/
H A DKconfig9 migration uAPI allowing userspace to enable migration for

12345678910>>...15