:orphan:

.. title:: IVSHMEM_MSI_X_VECTORS

.. option:: CONFIG_IVSHMEM_MSI_X_VECTORS

*How many notification vectors should be pre-allocated?*

Type: ``int``

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
===================

\ :option:`IVSHMEM_DOORBELL <CONFIG_IVSHMEM_DOORBELL>` && \ :option:`IVSHMEM <CONFIG_IVSHMEM>` && \ :option:`VIRTUALIZATION <CONFIG_VIRTUALIZATION>`

*(Includes any dependencies from ifs and menus.)*

Default
=======

- 2

Kconfig definition
==================

.. highlight:: kconfig

At ``drivers/virtualization/Kconfig:40``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:32`` → ``drivers/Kconfig:106``

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

.. parsed-literal::

    config IVSHMEM_MSI_X_VECTORS
    	int "How many notification vectors should be pre-allocated?"
    	default 2
    	depends on \ :option:`IVSHMEM_DOORBELL <CONFIG_IVSHMEM_DOORBELL>` && \ :option:`IVSHMEM <CONFIG_IVSHMEM>` && \ :option:`VIRTUALIZATION <CONFIG_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.)*