Help¶

MSI-X vector holders must be pre-allocated. One can pre-allocate more or less than necessary. Depends on how many VMs will connect with each other. These are know to be the notification vectors in ivshmem.

Direct dependencies¶

IVSHMEM_DOORBELL && IVSHMEM && VIRTUALIZATION

(Includes any dependencies from ifs and menus.)

Default¶

2

Kconfig definition¶

At <Zephyr>/drivers/virtualization/Kconfig:40

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:32 → <Zephyr>/drivers/Kconfig:106

Menu path: (Top) → Device Drivers → Virtualization guests drivers → Inter-VM shared memory device (ivshmem) → Support interrupt based ivshmem (doorbell version)

config IVSHMEM_MSI_X_VECTORS
    int "How many notification vectors should be pre-allocated?"
    default 2
    depends on IVSHMEM_DOORBELL && IVSHMEM && VIRTUALIZATION
    help
      MSI-X vector holders must be pre-allocated. One can pre-allocate
      more or less than necessary. Depends on how many VMs will connect
      with each other. These are know to be the notification vectors in
      ivshmem.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)