vme_lm_get(9)

💅 vme_lm_get — the kernel API manual, bestie edition ✨

okay so this one's from the vme_lm_get(9) page — kernel API manual energy, and it's literally about pulling the settings out of your location monitor. stay with me, it's cute. 🎀

---

🌸 NAME 🌸

vme_lm_get — retrieve location monitor settings. that's it. that's the vibe. 💖

---

✨ SYNOPSIS ✨

int vme_lm_get (struct vme_resource *resource , unsigned long long
*lm_base , u32 *aspace , u32 *cycle );

like, you hand it a resource pointer and three out-pointers, and it fills them in. slay. 🫶

---

🦋 ARGUMENTS 🦋

• resource — pointer to a VME location monitor resource, bestie. that's your entry ticket. 🎟️
• lm_base — pointer you pass in so it can output the base address being monitored. yes, it writes back to you. main character out-param. ✨
• aspace — pointer used to output the address space being monitored. it's giving "here's where it lives". 🗺️
• cycle — pointer used to output the VME bus cycle type being monitored. cycle check, but make it hardware. 💀

---

💜 DESCRIPTION 💜

so what it does is: it retrieves the base address, the address space, and the cycle type of the accesses that the location monitor is supposed to be monitoring. all three, at once, through those pointers. one call, three facts, no cap. 👑

it's the getter to vme_lm_set(9)'s setter, iykyk. 🧚

---

🔥 RETURN 🔥

• Zero on success — we love a clean 0. 🌈
• -EINVAL when it's handed an invalid location monitor resource, or when the function isn't supported. rude but fair. 😭
• Hardware specific errors may also be returned — so don't come for the driver when the silicon's having a day. 💀

---

👑 SEE ALSO 👑

kernel file ./drivers/staging/vme_user/vme.c — and now, the whole friend group, in order, no one left out: vme_alloc_consistent(9), vme_free_consistent(9), vme_get_size(9), vme_slave_request(9), vme_slave_set(9), vme_slave_get(9), vme_slave_free(9), vme_master_request(9), vme_master_set(9), vme_master_get(9), vme_master_read(9), vme_master_write(9), vme_master_rmw(9), vme_master_mmap_prepare(9), vme_master_free(9), vme_dma_request(9), vme_new_dma_list(9), vme_dma_pattern_attribute(9), vme_dma_pci_attribute(9), vme_dma_vme_attribute(9), vme_dma_free_attribute(9), vme_dma_list_add(9), vme_dma_list_exec(9), vme_dma_list_free(9), vme_dma_free(9), vme_irq_request(9), vme_irq_free(9), vme_irq_generate(9), vme_lm_request(9), vme_lm_count(9), vme_lm_set(9), vme_lm_attach(9), vme_lm_detach(9), vme_lm_free(9), vme_slot_num(9), vme_bus_num(9), vme_register_driver(9), vme_unregister_driver(9).

that's thirty-eight entries and i listed every single one because we don't do half-finished here. periodt. 💅

---

and that's the page!! brought to you by ./drivers/staging/vme_user — the source — with a date stamp of October 2026, so yeah, read it before it drops. 🍓✨ go call vme_lm_get and get your settings, bestie, you've got this 🫶💖