linux-kernel - Re: Adding VIRTIO to the multi_v7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 29 Nov 2015 14:56:53 -0800
From:	Peter Crosthwaite <crosthwaitepeter@...il.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	linux-arm-kernel@...ts.infradead.org,
	Guenter Roeck <linux@...ck-us.net>,
	linux-kernel@...r.kernel.org,
	Peter Maydell <peter.maydell@...aro.org>
Subject: Re: Adding VIRTIO to the multi_v7_defconfig

On Sun, Nov 29, 2015 at 2:31 PM, Arnd Bergmann <arnd@...db.de> wrote:
> On Sunday 29 November 2015 14:18:24 Peter Crosthwaite wrote:
>>
>> I started a small project to test as many QEMU emulated ARM boards
>> using the multi_v7 defconfig:
>>
>> https://lists.gnu.org/archive/html/qemu-devel/2015-10/msg00755.html
>>
>> One thing that came up was we cannot use the virt board as it relies
>> on virtio hotplug and drivers to get block and network support. The
>> defconfig is missing the drivers. Should we add the VIRTIO drivers to
>> the defconfig to bring this into play?
>
> Yes, please send a patch, this is definitely useful. We normally ask
> everyone to use loadable modules for newly enabled device drivers
> in multi_v7_defconfig, but we might actually use built-in drivers
> here if that would otherwise be the only module needed for booting.
>

So minimally I am looking for:

CONFIG_VIRTIO_PCI=y"
CONFIG_VIRTIO_BLK=y"
CONFIG_VIRTIO_NET=y"

As that gets you booted with network without needing initrd. I guess
the rest of VIRTIO makes more sense as modules as follow up work?

Regards,
Peter

>         Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/