fm10k_io_reset_done(9)
β¨ fm10k_io_reset_done π β¨
(from the Kernel API Manual, bestie π«Ά)
πΈ NAME πΈ
fm10k_io_reset_done β the callback that gets called when the PCI function has finished resetting. π
π SYNOPSIS π
void fm10k_io_reset_done (struct pci_dev *pdev );
π¦ ARGUMENTS π¦
pdevβ Pointer to PCI device. That's the one and only argument, bestie. π«Ά
β¨ DESCRIPTION β¨
Okay so picture this: the PCI function just finished resetting, and right after that, this callback gets called. Like, it's the "reset is done, we're back" moment. π
This can happen via /sys/class/net/<enpX>/device/reset or something similar. That's literally the vibe: reset happens, then this callback is called just after. Periodt. π
π SEE ALSO π
Kernel file: ./drivers/net/ethernet/intel/fm10k/fm10k_pci.c
The whole squad, no cap:
fm10k_macvlan_schedule(9)fm10k_stop_macvlan_task(9)fm10k_resume_macvlan_task(9)fm10k_service_timer(9)fm10k_prepare_for_reset(9)fm10k_configure_swpri_map(9)fm10k_watchdog_update_host_state(9)fm10k_mbx_subtask(9)fm10k_watchdog_host_is_ready(9)fm10k_watchdog_host_not_ready(9)fm10k_update_stats(9)fm10k_watchdog_flush_tx(9)fm10k_watchdog_subtask(9)fm10k_check_hang_subtask(9)fm10k_service_task(9)fm10k_macvlan_task(9)fm10k_configure_tx_ring(9)fm10k_enable_tx_ring(9)fm10k_configure_tx(9)fm10k_configure_rx_ring(9)fm10k_update_rx_drop_en(9)fm10k_configure_dglort(9)fm10k_configure_rx(9)fm10k_qv_free_irq(9)fm10k_qv_request_irq(9)fm10k_sw_init(9)fm10k_probe(9)fm10k_remove(9)fm10k_resume(9)fm10k_suspend(9)fm10k_io_error_detected(9)fm10k_io_slot_reset(9)fm10k_io_resume(9)fm10k_io_reset_prepare(9)fm10k_register_pci_driver(9)fm10k_unregister_pci_driver(9)
okay that's the whole page, bestie π it's from the Kernel API Manual, and the source/version line says ./drivers/net/ethernet/intel/f... with the date October 2026. slay, you made it to the end πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms