• Ohad Ben-Cohen's avatar
    virtio: expose for non-virtualization users too · e7254219
    Ohad Ben-Cohen authored
    virtio has been so far used only in the context of virtualization,
    and the virtio Kconfig was sourced directly by the relevant arch
    Kconfigs when VIRTUALIZATION was selected.
    Now that we start using virtio for inter-processor communications,
    we need to source the virtio Kconfig outside of the virtualization
    scope too.
    Moreover, some architectures might use virtio for both virtualization
    and inter-processor communications, so directly sourcing virtio
    might yield unexpected results due to conflicting selections.
    The simple solution offered by this patch is to always source virtio's
    Kconfig in drivers/Kconfig, and remove it from the appropriate arch
    Kconfigs. Additionally, a virtio menu entry has been added so virtio
    drivers don't show up in the general drivers menu.
    This way anyone can use virtio, though it's arguably less accessible
    (and neat!) for virtualization users now.
    Note: some architectures (mips and sh) seem to have a VIRTUALIZATION
    menu merely for sourcing virtio's Kconfig, so that menu is removed too.
    Signed-off-by: default avatarOhad Ben-Cohen <ohad@wizery.com>
    Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>
Kconfig 59 KB