From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752718AbcEIMRB (ORCPT ); Mon, 9 May 2016 08:17:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41320 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751270AbcEIMRA (ORCPT ); Mon, 9 May 2016 08:17:00 -0400 Subject: Re: [PATCH v2] Enhance kvmconfig To: Borislav Petkov , Andrey Utkin References: <1461432408-6087-1-git-send-email-andrey_utkin@fastmail.com> <20160424163046.GD3822@pd.tnic> Cc: linux-kernel@vger.kernel.org, x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" From: Paolo Bonzini Message-ID: <57307FB7.5040600@redhat.com> Date: Mon, 9 May 2016 14:16:55 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <20160424163046.GD3822@pd.tnic> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Mon, 09 May 2016 12:16:59 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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