On (Thu) 24 Feb 2011 [11:28:19], Chuck Ebbert wrote: > The virtio configuration options are inconsistent. According to this, > every options that needs virtio will select it: > > # Virtio always gets selected by whoever wants it. > config VIRTIO > tristate > > Note that it's not user-selectable, so any config file that tries to > set it will be ignored when kconfig loads those options. And yet we > have a whole set of options that depend on VIRTIO, like VIRTIO_CONSOLE > for example. This makes it impossible to have VIRTIO_PCI modular and > VIRTIO_CONSOLE built-in on x86_64, because: Any reason to have VIRTIO_PCI modular instead of built in (on x86-64, virtio-console won't work without virtio-pci anyway)? Amit _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
