:orphan:

.. title:: CONFIG_IVSHMEM_MSI_X_VECTORS

.. kconfig:: CONFIG_IVSHMEM_MSI_X_VECTORS

CONFIG_IVSHMEM_MSI_X_VECTORS
############################

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

Type: ``int``

Help
====

.. code-block:: none

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

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

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

Default
=======

- 2

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



At ``<Zephyr Driver>/virtualization/Kconfig:40``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:42`` → ``<Zephyr Driver>/Kconfig:108``

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

.. code-block:: kconfig

    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.)*