ne_pci_dev_...nclave_entry(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME

okay so bestie, welcome to ne_pci_dev_...nclave_entry(9) from the Kernel API Manual 🫢 β€” yes that title is a whole vibe, but the function we're actually talking about is ne_pci_dev_remove_enclave_entry, and it's here to remove the enclave entry from the data structure that is part of the NE PCI device private data. no cap, that's the whole gig ✨.

✨ SYNOPSIS ✨

the signature is literally this, don't come for me:

void ne_pci_dev_remove_enclave_entry (struct ne_enclave *ne_enclave ,
       struct ne_pci_dev *ne_pci_dev );

see that void? it's giving "returns nothing," periodt πŸ’….

🫢 ARGUMENTS 🫢

  • ne_enclave β€” private data associated with the current enclave. it's the current enclave's lil private-data situation πŸ’–.
  • ne_pci_dev β€” private data associated with the PCI device. yes, the PCI device's own private data, iconic πŸŽ€.

πŸ”’ CONTEXT πŸ”’

process context, bb πŸ¦‹. this function is called with the ne_pci_dev enclave mutex held β€” so yeah, the mutex is already locked when this runs, keep that energy πŸ”₯.

🌈 SEE ALSO 🌈


okay bestie that's the whole page πŸ’– the footer situation is source/version ./drivers/virt/nitro_enclaves, date October 2026, title ne_pci_dev_...nclave_entry(9) β€” mwah, go be iconic in the kernel 🌸🫢

πŸ“¦ where this page comes from