section 9 · Kernel routines 🧠
87928 pages · page 433 of 440
X (continued)
- xe_sriov_pf_control_reset_vf(9)Perform a VF reset (FLR).✨
- xe_sriov_pf_control_resume_vf(9)Resume a VF on all GTs.✨
- xe_sriov_pf_control_stop_vf(9)Stop a VF on all GTs.✨
- xe_sriov_pf_control_sync_flr(9)Synchronize a VF FLR between all GTs.✨
- xe_sriov_pf_control_trigger_restore_vf(9)Start VF migration data RESTORE sequence on all GTs.✨
- xe_sriov_pf_control_trigger_save_vf(9)Start VF migration data SAVE sequence on all GTs.✨
- xe_sriov_pf_control_wait_flr(9)Wait for a VF reset (FLR) to complete.✨
- xe_sriov_pf_debugfs_register(9)Register PF debugfs attributes.✨
- xe_sriov_pf_disarm_guard(9)Disarm the guard.✨
- xe_sriov_pf_end_lockdown(9)Allow the PF to enable VFs again.✨
- xe_sriov_pf_get_totalvfs(9)Get maximum number of VFs that driver can support.✨
- xe_sriov_pf_init_early(9)Initialize SR-IOV PF specific data.✨
- xe_sriov_pf_init_late(9)Late initialization of the SR-IOV PF.✨
- xe_sriov_pf_lockdown(9)Lockdown the PF to prevent VFs enabling.✨
- xe_sriov_pf_migration_disable(9)Turn off SR-IOV VF migration support on PF.✨
- xe_sriov_pf_migration_init(9)Initialize support for SR-IOV VF migration.✨
- xe_sriov_pf_migration_read(9)Read migration data from the device.✨
- xe_sriov_pf_migration_restore_produce(9)Produce a VF migration data packet to the device.✨
- xe_sriov_pf_migration_save_consume(9)Consume a VF migration data packet from the device.✨
- xe_sriov_pf_migration_size(9)Total size of migration data from all components within a device✨
- xe_sriov_pf_migration_supported(9)Check if SR-IOV VF migration is supported by the device✨
- xe_sriov_pf_migration_waitqueue(9)Get waitqueue for migration.✨
- xe_sriov_pf_migration_write(9)Write migration data to the device.✨
- xe_sriov_pf_num_vfs(9)Number of enabled VFs on the PF.✨
- xe_sriov_pf_print_vfs_summary(9)Print SR-IOV PF information.✨
- xe_sriov_pf_provision_apply_vf_eq(9)Change VF's execution quantum.✨
- xe_sriov_pf_provision_apply_vf_priority(9)Change VF's scheduling priority.✨
- xe_sriov_pf_provision_apply_vf_pt(9)Change VF's preemption timeout.✨
- xe_sriov_pf_provision_apply_vf_vram(9)Change single VF VRAM allocation.✨
- xe_sriov_pf_provision_bulk_apply_eq(9)Change execution quantum for all VFs and PF.✨
- xe_sriov_pf_provision_bulk_apply_priority(9)Change scheduling priority of all VFs and PF.✨
- xe_sriov_pf_provision_bulk_apply_pt(9)Change preemption timeout for all VFs and PF.✨
- xe_sriov_pf_provision_bulk_apply_vram(9)Change VRAM provisioning for all VFs.✨
- xe_sriov_pf_provision_query_vf_eq(9)Query VF's execution quantum.✨
- xe_sriov_pf_provision_query_vf_priority(9)Query VF's scheduling priority.✨
- xe_sriov_pf_provision_query_vf_pt(9)Query VF's preemption timeout.✨
- xe_sriov_pf_provision_query_vf_vram(9)Query VF's VRAM allocation.✨
- xe_sriov_pf_provision_set_custom_mode(9)Change VFs provision mode to custom.✨
- xe_sriov_pf_provision_set_mode(9)Change VFs provision mode.✨
- xe_sriov_pf_provision_vfs(9)Provision VFs in auto-mode.✨
- xe_sriov_pf_readiness(9)Check if PF functionality can be enabled.✨
- xe_sriov_pf_reprovision_default(9)Reprovision default PF in auto-mode.✨
- xe_sriov_pf_service_handshake_vf(9)Confirm a connection with the VF.✨
- xe_sriov_pf_service_init(9)Early initialization of the SR-IOV PF service.✨
- xe_sriov_pf_service_is_negotiated(9)Check if VF has negotiated given ABI version.✨
- xe_sriov_pf_service_print_versions(9)Print ABI versions negotiated with VFs.✨
- xe_sriov_pf_service_reset_vf(9)Reset a connection with the VF.✨
- xe_sriov_pf_sysfs_init(9)Setup PF's SR-IOV sysfs tree.✨
- xe_sriov_pf_sysfs_link_vfs(9)Add VF's links in SR-IOV sysfs tree.✨
- xe_sriov_pf_sysfs_unlink_vfs(9)Remove VF's links from SR-IOV sysfs tree.✨
- xe_sriov_pf_unprovision_vfs(9)Unprovision VFs in auto-mode.✨
- xe_sriov_pf_wait_ready(9)Wait until PF is ready to operate.✨
- xe_sriov_print_info(9)Print basic SR-IOV information.✨
- xe_sriov_probe_early(9)Probe a SR-IOV mode.✨
- xe_sriov_vf_ccs_attach_bo(9)Insert CCS read write commands in the BO.✨
- xe_sriov_vf_ccs_detach_bo(9)Remove CCS read write commands from the BO.✨
- xe_sriov_vf_ccs_init(9)Setup LRCA for save & restore.✨
- xe_sriov_vf_ccs_print(9)Print VF CCS details.✨
- xe_sriov_vf_ccs_rebase(9)Rebase GGTT addresses for CCS save / restore✨
- xe_sriov_vf_ccs_register_context(9)Register read/write contexts with guc.✨
- xe_sriov_vf_debugfs_register(9)Register VF debugfs attributes.✨
- xe_sriov_vf_init_early(9)Initialize SR-IOV VF specific data.✨
- xe_sriov_vf_init_late(9)SR-IOV VF late initialization functions.✨
- xe_sriov_vf_migration_disable(9)Turn off VF migration with given log message.✨
- xe_sriov_vf_migration_supported(9)Report whether SR-IOV VF migration is supported or not.✨
- xe_sriov_vfio_data_read(9)Read migration data from the VF device.✨
- xe_sriov_vfio_data_write(9)Write migration data to the VF device.✨
- xe_sriov_vfio_error(9)Move VF device to error state.✨
- xe_sriov_vfio_flr_prepare(9)Notify PF that VF FLR prepare has started.✨
- xe_sriov_vfio_get_pf(9)Get PF &xe_device.✨
- xe_sriov_vfio_migration_supported(9)Check if migration is supported.✨
- xe_sriov_vfio_resume_data_enter(9)Initiate a VF device migration data restore.✨
- xe_sriov_vfio_resume_data_exit(9)Finish a VF device migration data restore.✨
- xe_sriov_vfio_resume_device(9)Resume VF.✨
- xe_sriov_vfio_stop_copy_enter(9)Initiate a VF device migration data save.✨
- xe_sriov_vfio_stop_copy_exit(9)Finish a VF device migration data save.✨
- xe_sriov_vfio_stop_copy_size(9)Get a size estimate of VF device migration data.✨
- xe_sriov_vfio_suspend_device(9)Suspend VF.✨
- xe_sriov_vfio_wait_flr_done(9)Wait for VF FLR completion.✨
- xe_step_gmdid_get(9)Determine IP steppings from GMD_ID revid fields✨
- xe_step_platform_get(9)Determine platform-level stepping from PCI revid✨
- xe_step_pre_gmdid_get(9)Determine IP steppings from PCI revid✨
- xe_survivability_mode_boot_enable(9)Initialize and enable boot survivability mode✨
- xe_survivability_mode_is_boot_enabled(9)check if boot survivability mode is enabled✨
- xe_survivability_mode_is_requested(9)check if it's possible to enable survivability mode that was requested by firmware or userspace✨
- xe_survivability_mode_runtime_enable(9)Initialize and enable runtime survivability mode✨
- xe_svm_alloc_vram(9)Allocate device memory pages for range, migrating existing data.✨
- xe_svm_bo_evict(9)SVM evict BO to system memory✨
- xe_svm_close(9)SVM close✨
- xe_svm_find_vma_start(9)Find start of CPU VMA✨
- xe_svm_fini(9)SVM finalize✨
- xe_svm_flush(9)SVM flush✨
- xe_svm_handle_pagefault(9)SVM handle page fault✨
- xe_svm_has_mapping(9)SVM has mappings✨
- xe_svm_init(9)SVM initialize✨
- xe_svm_range_end(9)SVM range end address✨
- xe_svm_range_find_or_insert(9)Find or insert GPU SVM range✨
- xe_svm_range_get_pages(9)Get pages for a SVM range✨
- xe_svm_range_has_dma_mapping(9)SVM range has DMA mapping✨
- xe_svm_range_needs_migrate_to_vram(9)SVM range needs migrate to VRAM or not✨
- xe_svm_range_pages_valid(9)SVM range pages valid✨
- xe_svm_range_size(9)SVM range size✨
- xe_svm_range_start(9)SVM range start address✨
- xe_svm_range_validate(9)Check if the SVM range is valid✨
- xe_svm_ranges_zap_ptes_in_range(9)clear ptes of svm ranges in input range✨
- xe_svm_unmap_address_range(9)UNMAP SVM mappings and ranges✨
- xe_sync_entry_wait(9)Wait on in-sync✨
- xe_sync_in_fence_get(9)Get a fence from syncs, exec queue, and VM✨
- xe_sync_needs_wait(9)Sync needs a wait (input dma-fence not signaled)✨
- xe_sync_ufence_get(9)Get user fence from sync✨
- xe_sync_ufence_get_status(9)Get user fence status✨
- xe_sync_ufence_put(9)Put user fence reference✨
- xe_sysctrl_create_command(9)Create system controller command✨
- xe_sysctrl_event(9)Handler for System Controller events✨
- xe_sysctrl_init(9)Initialize System Controller subsystem✨
- xe_sysctrl_irq_handler(9)Handler for System Controller interrupts✨
- xe_sysctrl_pm_resume(9)System Controller resume handler✨
- xe_sysctrl_send_command(9)Send mailbox command to System Controller✨
- xe_tile_alloc(9)Perform per-tile memory allocation✨
- xe_tile_alloc_vram(9)Perform per-tile VRAM structs allocation✨
- xe_tile_assert(9)warn if condition is false when debugging.✨
- xe_tile_dbg_printer(9)Construct a &drm_printer that outputs like xe_tile_dbg()✨
- xe_tile_debugfs_register(9)Register tile's debugfs attributes✨
- xe_tile_debugfs_show_with_rpm(9)A show callback for struct drm_info_list✨
- xe_tile_debugfs_simple_show(9)A show callback for struct drm_info_list✨
- xe_tile_err_printer(9)Construct a &drm_printer that outputs to xe_tile_err()✨
- xe_tile_info_printer(9)Construct a &drm_printer that outputs to xe_tile_info()✨
- xe_tile_init_early(9)Initialize the tile and primary GT✨
- xe_tile_init_noalloc(9)Init tile up to the point where allocations can happen.✨
- xe_tile_local_pagemap(9)Return a pointer to the tile's local drm_pagemap if any✨
- xe_tile_sriov_pf_debugfs_populate(9)Populate SR-IOV debugfs tree with tile files.✨
- xe_tile_sriov_vf_ggtt(9)VF GGTT configuration.✨
- xe_tile_sriov_vf_ggtt_base(9)VF GGTT base configuration.✨
- xe_tile_sriov_vf_ggtt_base_store(9)Store VF GGTT base configuration✨
- xe_tile_sriov_vf_ggtt_store(9)Store VF GGTT configuration✨
- xe_tile_sriov_vf_lmem(9)VF LMEM configuration.✨
- xe_tile_sriov_vf_lmem_store(9)Store VF LMEM configuration✨
- xe_tile_to_vr(9)Return the struct xe_vram_region pointer from a struct xe_tile pointer✨
- xe_tlb_inval_all(9)Issue a TLB invalidation for all TLBs✨
- xe_tlb_inval_batch_wait(9)Wait for all fences in a TLB invalidation batch✨
- xe_tlb_inval_done_handler(9)TLB invalidation done handler✨
- xe_tlb_inval_fence_init(9)Initialize TLB invalidation fence✨
- xe_tlb_inval_fence_wait(9)TLB invalidiation fence wait✨
- xe_tlb_inval_ggtt(9)Issue a TLB invalidation for the GGTT✨
- xe_tlb_inval_idle(9)Initialize TLB invalidation is idle✨
- xe_tlb_inval_job_add_page_reclaim(9)Embed PRL into a TLB job✨
- xe_tlb_inval_job_alloc_dep(9)TLB invalidation job alloc dependency✨
- xe_tlb_inval_job_create(9)TLB invalidation job create✨
- xe_tlb_inval_job_get(9)Get a reference to TLB invalidation job✨
- xe_tlb_inval_job_push(9)TLB invalidation job push✨
- xe_tlb_inval_job_put(9)Put a reference to TLB invalidation job✨
- xe_tlb_inval_range(9)Issue a TLB invalidation for an address range✨
- xe_tlb_inval_range_tilemask_submit(9)Submit TLB invalidations for an address range on a tile mask✨
- xe_tlb_inval_reset(9)TLB invalidation reset✨
- xe_tlb_inval_reset_timeout(9)Reset TLB inval fence timeout✨
- xe_tlb_inval_vm(9)Issue a TLB invalidation for a VM✨
- xe_ttm_bo_purge(9)Purge buffer object backing store✨
- xe_ttm_stolen_cpu_access_needs_ggtt(9)If we can't directly CPU access stolen, can we then fallback to mapping through the GGTT.✨
- xe_ttm_vram_mgr_init(9)initialize TTM VRAM region✨
- xe_tuning_dump(9)Dump GT tuning info into a drm printer.✨
- xe_tuning_init(9)initialize gt with tunings bookkeeping✨
- xe_tuning_process_lrc(9)process lrc tunings✨
- xe_uc_declare_wedged(9)Declare UC wedged✨
- xe_uc_fw_copy_rsa(9)copy fw RSA to buffer✨
- xe_uc_fw_get_upload_size(9)Get size of firmware needed to be uploaded.✨
- xe_uc_init_post_hwconfig(9)init Uc post hwconfig load✨
- xe_uc_runtime_resume(9)UC runtime resume✨
- xe_uc_runtime_suspend(9)UC runtime suspend✨
- xe_validation_assert_exec(9)Assert that the drm_exec pointer is suitable for validation.✨
- xe_validation_ctx_fini(9)Finalize a validation transaction✨
- xe_validation_ctx_init(9)Initialize an xe_validation_ctx✨
- xe_validation_device_init(9)Initialize a struct xe_validation_device✨
- xe_validation_exec_lock(9)Perform drm_gpuvm_exec_lock within a validation transaction.✨
- xe_validation_guard(9)An auto-cleanup xe_validation_ctx transaction✨
- xe_validation_lockdep(9)Assert that a drm_exec locking transaction can be initialized at this point.✨
- xe_validation_retry_on_oom(9)Retry on oom in an xe_validaton transaction✨
- xe_validation_should_retry(9)Determine if a validation transaction should retry✨
- xe_vf_migration_fixups_complete_count(9)Get count of VF fixups completions.✨
- xe_vm_add_exec_queue(9)Add exec queue to VM✨
- xe_vm_add_fault_entry_pf(9)Add pagefault to vm fault list✨
- xe_vm_alloc_cpu_addr_mirror_vma(9)Allocate CPU addr mirror vma✨
- xe_vm_alloc_madvise_vma(9)Allocate VMA's with madvise ops✨
- xe_vm_assert_held(9)Assert that the vm's reservation object is held.✨
- xe_vm_bind_kernel_bo(9)bind a kernel BO to a VM✨
- xe_vm_bump_lru(9)Bump the LRU position of BOs used by a submission✨
- xe_vm_clear_validating(9)Unregister this task as currently making bos resident✨
- xe_vm_create_scratch(9)Setup a scratch memory pagetable tree for the given tile and vm.✨
- xe_vm_drm_exec_lock(9)Lock the vm's resv with a drm_exec transaction✨
- xe_vm_find_cpu_addr_mirror_vma_range(9)Extend a VMA range to include adjacent CPU-mirrored VMAs✨
- xe_vm_find_vma_by_addr(9)Find a VMA by its address✨
- xe_vm_has_scratch(9)Whether the vm is configured for scratch PTEs✨
- xe_vm_has_valid_gpu_mapping(9)Advisory helper to check if VMA or SVM range has a valid GPU mapping✨
- xe_vm_invalidate_vma(9)invalidate GPU mappings for VMA without a lock✨
- xe_vm_invalidate_vma_submit(9)Submit a job to invalidate GPU mappings for VMA.✨
- xe_vm_is_validating(9)Whether bos bound to the vm are currently being made resident by the current task.✨
- xe_vm_kill(9)VM Kill✨
- xe_vm_lock(9)Lock the vm's dma_resv object✨
- xe_vm_lock_vma(9)drm_exec utility to lock a vma✨
- xe_vm_madvise_ioctl(9)Handle MADVise ioctl for a VM✨
- xe_vm_range_rebind(9)VM range (re)bind✨
💅
getting it ready, bestie…