drivers/net/xen-netback/netback.c

File Facts

System

Linux kernel

Corpus path

drivers/net/xen-netback/netback.c

Extension

.c

Size

48023 bytes

Lines

1791

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• common.h
• linux/kthread.h
• linux/if_vlan.h
• linux/udp.h
• linux/highmem.h
• linux/skbuff_ref.h
• net/tcp.h
• xen/xen.h
• xen/events.h
• xen/interface/memory.h
• xen/page.h
• asm/xen/hypercall.h

Detected Declarations

• struct xenvif_tx_cb
• function idx_to_pfn
• function idx_to_kaddr
• function frag_get_pending_idx
• function frag_set_pending_idx
• function pending_index
• function xenvif_kick_thread
• function xenvif_napi_schedule_or_enable_events
• function tx_add_credit
• function xenvif_tx_credit_callback
• function xenvif_tx_err
• function xenvif_fatal_tx_err
• function xenvif_count_requests
• function xenvif_tx_create_map_op
• function xenvif_get_requests
• function xenvif_grant_handle_set
• function xenvif_grant_handle_reset
• function xenvif_tx_check_gop
• function xenvif_fill_frags
• function xenvif_get_extras
• function xenvif_set_skb_gso
• function checksum_setup
• function tx_credit_exceeded
• function xenvif_mcast_match
• function xenvif_mcast_del
• function list_for_each_entry_rcu
• function xenvif_mcast_match
• function xenvif_mcast_addr_list_free
• function xenvif_tx_build_gops
• function xenvif_handle_frag_list
• function xenvif_tx_submit
• function xenvif_zerocopy_callback
• function xenvif_tx_dealloc_action
• function xenvif_tx_action
• function _make_tx_response
• function push_tx_responses
• function xenvif_idx_release
• function make_tx_response
• function xenvif_idx_unmap
• function tx_work_todo
• function tx_dealloc_work_todo
• function xenvif_unmap_frontend_data_rings
• function xenvif_map_frontend_data_rings
• function xenvif_dealloc_kthread_should_stop
• function xenvif_dealloc_kthread
• function make_ctrl_response
• function push_ctrl_response
• function process_ctrl_request

Annotated Snippet

module_init(netback_init);

static void __exit netback_fini(void)
{
#ifdef CONFIG_DEBUG_FS
	debugfs_remove_recursive(xen_netback_dbg_root);
#endif /* CONFIG_DEBUG_FS */
	xenvif_xenbus_fini();
}
module_exit(netback_fini);

MODULE_DESCRIPTION("Xen backend network device module");
MODULE_LICENSE("Dual BSD/GPL");
MODULE_ALIAS("xen-backend:vif");

Annotation

• Immediate include surface: `common.h`, `linux/kthread.h`, `linux/if_vlan.h`, `linux/udp.h`, `linux/highmem.h`, `linux/skbuff_ref.h`, `net/tcp.h`, `xen/xen.h`.
• Detected declarations: `struct xenvif_tx_cb`, `function idx_to_pfn`, `function idx_to_kaddr`, `function frag_get_pending_idx`, `function frag_set_pending_idx`, `function pending_index`, `function xenvif_kick_thread`, `function xenvif_napi_schedule_or_enable_events`, `function tx_add_credit`, `function xenvif_tx_credit_callback`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.