Home
last modified time | relevance | path

Searched refs:migration (Results 1 – 25 of 108) sorted by relevance

12345

/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
H A 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
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
H A Dsysfs-class-rnbd-client14 > [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/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 allow
[all...]
H A 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.
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 i
[all...]
H A Darch_pgtable_helpers.rst247 | is_migration_entry | Tests a migration (read or write) swapped entry |
249 | is_writable_migration_entry | Tests a write migration swapped entry |
251 | make_readable_migration_entry | Creates a read migration swapped entry |
253 | make_writable_migration_entry | Creates a write migration swapped entry |
/linux/drivers/gpu/drm/xe/
H A Dxe_sriov_vf.c55 * the MIGRATED interrupt and schedules post-migration recovery worker.
110 * | | migration fixups -------[ ]
144 INIT_WORK(&xe->sriov.vf.migration.worker, migration_worker_func); in xe_sriov_vf_init_early()
147 xe_sriov_info(xe, "migration not supported by this module version\n"); in xe_sriov_vf_init_early()
152 return test_bit(gt->info.id, &gt_to_xe(gt)->sriov.vf.migration.gt_flags); in gt_vf_post_migration_needed()
189 if (test_and_clear_bit(id, &xe->sriov.vf.migration.gt_flags)) in vf_get_next_migrated_gt_id()
196 * Perform post-migration fixups on a single GT.
198 * After migration, GuC needs to be re-queried for VF configuration to check
231 drm_dbg(&xe->drm, "migration recovery in progress\n"); in vf_post_migration_recovery()
235 xe_sriov_err(xe, "migration no in vf_post_migration_recovery()
[all...]
H A Dxe_gt_sriov_pf_migration.c119 return gt->sriov.pf.migration.supported; in pf_migration_supported()
125 return &gt->sriov.pf.migration.snapshot_lock; in pf_migration_mutex()
395 * xe_gt_sriov_pf_migration_init() - Initialize support for VF migration.
409 gt->sriov.pf.migration.supported = pf_check_migration_support(gt); in xe_gt_sriov_pf_migration_init()
414 err = drmm_mutex_init(&xe->drm, &gt->sriov.pf.migration.snapshot_lock); in xe_gt_sriov_pf_migration_init()
H A Dxe_sriov_vf_types.h32 /** @migration: VF Migration state data */
34 /** @migration.worker: VF migration recovery worker */
36 /** @migration.gt_flags: Per-GT request flags for VF migration recovery */
38 } migration; member
H A Dxe_gt_sriov_pf_types.h52 * @migration: migration data.
61 struct xe_gt_sriov_pf_migration migration; member
/linux/tools/testing/selftests/mm/
H A Dmigration.c3 * The main purpose of the tests here is to exercise the migration entry code
26 FIXTURE(migration) in FIXTURE() argument
35 FIXTURE_SETUP(migration) in FIXTURE_SETUP() argument
60 FIXTURE_TEARDOWN(migration) in FIXTURE_TEARDOWN() argument
120 * Basic migration entry testing. One thread will move pages back and forth
122 * migration entry wait paths in the kernel.
124 TEST_F_TIMEOUT(migration, private_anon, 2*RUNTIME)
149 TEST_F_TIMEOUT(migration, shared_anon, 2*RUNTIME)
182 * Tests the pmd migration entry paths.
184 TEST_F_TIMEOUT(migration, private_anon_th
[all...]
H A D.gitignore15 migration
/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.
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/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.
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 Dfailover.rst17 datapath. It also allows live migration of VMs with direct attached VFs by
/linux/Documentation/admin-guide/cgroup-v1/
H A Dmemcg_test.rst102 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 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 mod
[all...]
/linux/tools/perf/Documentation/
H A Dperf-sched.txt75 79371.874603 [0010] migration/10[59] 3.350 0.004 0.011
195 Show migration events.
226 Show pre-migration wait time. pre-migration wait time is the time spent
229 time between sched_wakeup and migrate_task is the pre-migration wait
/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/Documentation/driver-api/
H A Dvfio-pci-device-specific-driver-acceptance.rst16 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 DKconfig8 This provides migration support for MLX5 devices using the VFIO
/linux/Documentation/admin-guide/mm/
H A 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 threa
[all...]
/linux/drivers/vfio/pci/qat/
H A DKconfig7 This provides migration support for Intel(R) QAT Virtual Function
/linux/kernel/irq/
H A DMakefile13 obj-$(CONFIG_GENERIC_PENDING_IRQ) += migration.o

12345