vme_lm_count(9)

✨ NAME ✨

okay so this is the vme_lm_count(9) page from the Kernel API Manual, and it's literally here to Determine number of VME Addresses monitored 💅 — that's the whole assignment, bestie.

---

🌸 SYNOPSIS 🌸

int vme_lm_count (struct vme_resource *resource );

---

🎀 ARGUMENTS 🎀

• resource — Pointer to VME location monitor resource. That's the thing you're handing over so it can do its little headcount 🫶

---

💖 DESCRIPTION 💖

okay so the number of contiguous addresses monitored is hardware dependent — meaning it's not one universal number, it depends on the hardware, no cap. This call returns the number of contiguous addresses monitored by the location monitor. That's it, that's the vibe ✨

---

🔥 RETURN 🔥

You get the count of addresses monitored, or -EINVAL when you provide an invalid location monitor resource. so yeah, invalid resource = -EINVAL, don't act surprised 😭

---

🌈 SEE ALSO 🌈

it's giving full VME squad, so here's the whole friend group in the house:

• Kernel file ./drivers/staging/vme_user/vme.c
• 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_set(9)
• vme_lm_get(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 the whole page, bestie — brought to you by source/version ./drivers/staging/vme_user, dated October 2026, under the title vme_lm_count(9). 🫶💖