Home
last modified time | relevance | path

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

12345

/linux-6.12.1/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.
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".
[all …]
Darch_pgtable_helpers.rst253 | is_migration_entry | Tests a migration (read or write) swapped entry |
255 | is_writable_migration_entry | Tests a write migration swapped entry |
257 | make_readable_migration_entry | Creates a read migration swapped entry |
259 | make_writable_migration_entry | Creates a write migration swapped entry |
/linux-6.12.1/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
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
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-6.12.1/tools/testing/selftests/mm/
Dmigration.c23 FIXTURE(migration) in FIXTURE() argument
32 FIXTURE_SETUP(migration) in FIXTURE_SETUP() argument
57 FIXTURE_TEARDOWN(migration) in FIXTURE_TEARDOWN() argument
123 TEST_F_TIMEOUT(migration, private_anon, 2*RUNTIME)
148 TEST_F_TIMEOUT(migration, shared_anon, 2*RUNTIME)
183 TEST_F_TIMEOUT(migration, private_anon_thp, 2*RUNTIME)
D.gitignore15 migration
Drun_vmtests.sh70 - migration
71 invoke move_pages(2) to exercise the migration entry code
453 CATEGORY="migration" run_test ./migration
DMakefile59 TEST_GEN_FILES += migration
199 $(OUTPUT)/migration: LDLIBS += -lnuma
/linux-6.12.1/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.
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
Dfailover.rst17 datapath. It also allows live migration of VMs with direct attached VFs by
/linux-6.12.1/Documentation/admin-guide/cgroup-v1/
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.
Drdma.rst53 always owned by the creator cgroup css. This allows process migration from one
57 deleted after processes migrated. This allow progress migration as well with
/linux-6.12.1/Documentation/virt/kvm/devices/
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-6.12.1/tools/perf/scripts/python/bin/
Dsched-migration-report3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/sched-migration.py
/linux-6.12.1/Documentation/driver-api/
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-6.12.1/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.12.1/drivers/vfio/pci/mlx5/
DKconfig8 This provides migration support for MLX5 devices using the VFIO
/linux-6.12.1/drivers/vfio/pci/qat/
DKconfig7 This provides migration support for Intel(R) QAT Virtual Function
/linux-6.12.1/kernel/irq/
DMakefile13 obj-$(CONFIG_GENERIC_PENDING_IRQ) += migration.o
/linux-6.12.1/drivers/gpu/drm/amd/amdkfd/
Dkfd_smi_events.h39 unsigned long address, bool migration);
/linux-6.12.1/Documentation/arch/powerpc/
Ddawr-power9.rst43 migration from POWER8 to POWER9, at the cost of silently losing the
44 DAWR on the migration.
/linux-6.12.1/include/scsi/
Dviosrp.h188 struct mad_migration_cap migration; member
/linux-6.12.1/fs/nfs/
DKconfig145 bool "NFSv4.1 client support for migration"
150 it can support NFSv4 migration.
152 The NFSv4.1 pieces of the Linux NFSv4 migration implementation are

12345