linux-kernel - Re: [PATCH v2] Enhance kvmconfig

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]

Message-ID: <57307FB7.5040600@redhat.com>
Date:	Mon, 9 May 2016 14:16:55 +0200
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Borislav Petkov <bp@...en8.de>,
	Andrey Utkin <andrey_utkin@...tmail.com>
Cc:	linux-kernel@...r.kernel.org, x86@...nel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH v2] Enhance kvmconfig



On 24/04/2016 18:30, Borislav Petkov wrote:
>> > +CONFIG_SCSI_VIRTIO=y
>> > +CONFIG_VIRTIO_INPUT=y
>> > +CONFIG_VIRTIO_MMIO=y
>> > +CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
>> > --
> Frankly, I'm still not sure we want to do this. Apparently, virtio is
> the way to go on kvm but it is not absolutely necessary to get a booting
> guest.
> 
> Paolo, what do you think?

I think adding virtio storage is a good idea for "make kvmconfig".

virtio-input is not _that_ useful on x86, but it's getting more useful
(recent QEMU can pass evdev events directly to a VM via virtio-input).
I'm ambivalent about it.

VIRTIO_MMIO should only be added by some ARM thing though.

Paolo