STRUCT PCI_EPF(9)
πΈ NAME πΈ
okay bestie, welcome to the Kernel API Manual page for struct pci_epf β yes, the (9) one, iykyk. π
struct pci_epf β represents the PCI EPF device. Thatβs the vibe, thatβs the whole assignment. β¨
π¦ SYNOPSIS π¦
okay so hereβs the full struct, literally every field, no cap:
struct pci_epf {
struct device dev;
const char *name;
struct pci_epf_header *header;
struct pci_epf_bar bar[PCI_STD_NUM_BARS];
u8 msi_interrupts;
u16 msix_interrupts;
u8 func_no;
u8 vfunc_no;
struct pci_epc *epc;
struct pci_epf *epf_pf;
struct pci_epf_driver *driver;
const struct pci_epf_device_id *id;
struct list_head list;
struct mutex lock;
struct pci_epc *sec_epc;
struct list_head sec_epc_list;
struct pci_epf_bar sec_epc_bar[PCI_STD_NUM_BARS];
u8 sec_epc_func_no;
struct config_group *group;
unsigned int is_bound;
unsigned int is_vf;
unsigned long vfunction_num_map;
struct list_head pci_vepf;
const struct pci_epc_event_ops *event_ops;
struct pci_epf_doorbell_msg *db_msg;
u16 num_db;
};
π Members π
devβ the PCI EPF device π«Άnameβ the name of the PCI EPF deviceheaderβ represents standard configuration headerbarβ represents the BAR of EPF devicemsi_interruptsβ number of MSI interrupts required by this functionmsix_interruptsβ number of MSI-X interrupts required by this functionfunc_noβ unique (physical) function number within this endpoint devicevfunc_noβ unique virtual function number within a physical functionepcβ the EPC device to which this EPF device is boundepf_pfβ the physical EPF device to which this virtual EPF device is bounddriverβ the EPF driver to which this EPF device is boundidβ pointer to the EPF device IDlistβ to addpci_epfas a list of PCI endpoint functions topci_epclockβ mutex to protectpci_epf_opssec_epcβ the secondary EPC device to which this EPF device is boundsec_epc_listβ to addpci_epfas list of PCI endpoint functions to secondary EPC devicesec_epc_barβ represents the BAR of EPF device associated with secondary EPCsec_epc_func_noβ unique (physical) function number within the secondary EPCgroupβ configfs group associated with the EPF deviceis_boundβ indicates if bind notification to function driver has been invokedis_vfβtrue- virtual function,false- physical functionvfunction_num_mapβ bitmap to manage virtual function numberpci_vepfβ list of virtual endpoint functions associated with this functionevent_opsβ callbacks for capturing the EPC eventsdb_msgβ data for MSI from RC sidenum_dbβ number of doorbells
π SEE ALSO π
Kernel file ./include/linux/pci-epf.h keeps company with struct pci_epf_header(9), struct pci_epf_ops(9), struct pci_epc_event_ops(9), struct pci_epf_driver(9), struct pci_epf_bar_submap(9), struct pci_epf_bar(9), struct pci_epf_doorbell_msg(9), and struct pci_epf_msix_tbl(9). π
π«Ά this page came from./include/linuxand is datedOctober 2026β bye bestie, stan the kernel π
π¦ 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