Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp1029094ybh; Wed, 11 Mar 2020 16:03:19 -0700 (PDT) X-Google-Smtp-Source: ADFU+vvB4xwAunrKziOO4ALEYRSnvrbSOf05WcNHqCbVCACzCXYcCW/i4xM8vljzLJcS2f0orWwR X-Received: by 2002:aca:b608:: with SMTP id g8mr691166oif.142.1583967799470; Wed, 11 Mar 2020 16:03:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1583967799; cv=none; d=google.com; s=arc-20160816; b=W8xhqQ7I0LZnl0uhPl0+keW2oWU342A0eUUkm7Xz+Pu10RAd8pIOjgRABcqkZ8GPEJ 8kYY0ifvLoArScnHQfdMjOMRsZTz7GZ0uNAdgJZhnRhUB5A+iRaH/1nisEcBT5hVHcvq rjHTkMNm4IV9XbpGwWLxeHZJZHYG2XJP2cZAMXpyUrAGa2h8hQyBRiP47BDPfXa7FkNG ZwS0puklBXeNIngrUcrZ4lTIDZp9Zu33BaZ8atNH77k6j20oh/ei+DHrB3q/BC1SNop+ xdhCukUL7M9kkOhNBqpHDpqevWOZAsIlPqXqpchPdJNtK/JXkJSZgu9x1IYhFkg6luWX kGZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=3mEzkj6XRFR4kWdQY1UH1Sim7j3oSUMmKUovhUqapmI=; b=hRC6rCmj5mSnMMSEX3LS4rJBKs1HYjUXvQIDuuMWfXJrB0RYf8ujg28SjUC78kgPua hyBKLpof0DHR/1/F+GxWZALW5hYO7a/QhF42RL/h0BZzNFGJ5EbnkpnFqTiLRbrA7wnt zHJ5ETtvvLutqBUnENgwH05kA3E+qnAUgegw4WKMhO7eMnUZO7PAE8xqKdvxt6u4/TIA ZKe6SWBRtUOp6+PMxgb9zBqlVRg/I3Xa9vIE162/w6Crnu3ZMX195INnO+SuxwuZn8n2 d/GcUmvr+gyztA5mqzeGQ7SuEaIZ2bQz3SQSglkGpmTQr3c4BarvtEBpRz2IBpJtH/qK XmQg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=VTU4olTS; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e5si1731161otp.317.2020.03.11.16.03.03; Wed, 11 Mar 2020 16:03:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=VTU4olTS; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731383AbgCKXCm (ORCPT + 99 others); Wed, 11 Mar 2020 19:02:42 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:42441 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729739AbgCKXCm (ORCPT ); Wed, 11 Mar 2020 19:02:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1583967760; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=3mEzkj6XRFR4kWdQY1UH1Sim7j3oSUMmKUovhUqapmI=; b=VTU4olTSc8nF7xSAOiGKvhZCx7PYIwbWSxRehaaR/hiTjBibW2DSouZR74jARnNqZJidS5 2TlIs+iMZyfvH24DKleULzUoeLopgR5Jau07H40w56dd24JYP0zCAGIevHQVjKe3Mwov43 ForxQbOLXqPISq9SLQ4YDpV/h7nGISU= Received: from mail-qk1-f197.google.com (mail-qk1-f197.google.com [209.85.222.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-79-NlIRHvtrNy6gNi6RbMmXgw-1; Wed, 11 Mar 2020 19:02:38 -0400 X-MC-Unique: NlIRHvtrNy6gNi6RbMmXgw-1 Received: by mail-qk1-f197.google.com with SMTP id x126so2597851qka.1 for ; Wed, 11 Mar 2020 16:02:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=3mEzkj6XRFR4kWdQY1UH1Sim7j3oSUMmKUovhUqapmI=; b=JvyKXzeB1EkqMfTAf9kxa6R3MfVb63XOWONAEhyic0eIsNK0w2lXhO1GFGzvYCdVWY c7gdP8RR+snLr3aZ5vtDKhgJ/eltcc4MTUrwLDwa3XeATy6t4HYUz/G2cn/xJ+ImTGOd aRistvEZEGKOXZTMV6Yslb5qYlQ9spP21Z8eD/iuJ23lecaPwbGnEzIc2pgDVBPAlomk EUeScpvk80tfeqomliHUSiryrjiFTASzTho0arcfm7Q0qIZ0owJkFpXFNigNvyVGcHWQ fA27vNjs5phAQEEIhrpIDVpxN9Lm9uO2r+vWqOICMecCwU4+q/QwDeWW9xIrq80yplyU nvHA== X-Gm-Message-State: ANhLgQ3J/zmtYlIgJeolVyOL40qHWokcL8462kFifACDLco7axl2VBl0 ahefqFlu0rxd1172L3Vxqwil3czsXCVOyuUxZ/juVpNa5AFFxGWvWOaOog8U+f5TcmmD5rN28S9 dTJik1zDaYcNBwqC39ECZyUnF X-Received: by 2002:ac8:351c:: with SMTP id y28mr4762168qtb.379.1583967758131; Wed, 11 Mar 2020 16:02:38 -0700 (PDT) X-Received: by 2002:ac8:351c:: with SMTP id y28mr4762149qtb.379.1583967757888; Wed, 11 Mar 2020 16:02:37 -0700 (PDT) Received: from redhat.com (bzq-79-178-2-19.red.bezeqint.net. [79.178.2.19]) by smtp.gmail.com with ESMTPSA id b8sm19471664qte.52.2020.03.11.16.02.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 11 Mar 2020 16:02:37 -0700 (PDT) Date: Wed, 11 Mar 2020 19:02:32 -0400 From: "Michael S. Tsirkin" To: Ram Muthiah Cc: Jason Wang , virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, kernel-team@android.com Subject: Re: [PATCH RESEND] virtio: virtio_pci_legacy: Remove default y from Kconfig Message-ID: <20200311190026-mutt-send-email-mst@kernel.org> References: <20200228232736.182780-1-rammuthiah@google.com> <20200301023025-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 11, 2020 at 03:44:14PM -0700, Ram Muthiah wrote: > On Sat, Feb 29, 2020 at 11:32 PM Michael S. Tsirkin wrote: > > > > On Fri, Feb 28, 2020 at 03:27:36PM -0800, Ram Muthiah wrote: > > > The legacy pci driver should no longer be default enabled. QEMU has > > > implemented support for Virtio 1 for virtio-pci since June 2015 > > > on SHA dfb8e184db75. > > > > > > Signed-off-by: Ram Muthiah > > > > I see little reason to do this: y is safer and will boot on more > > hypervisors, so people that aren't sure should enable it. > > > > In that case, would it be reasonable to fold VIRTIO_PCI_LEGACY > into VIRTIO_PCI? > > The result would boot more hypervisors as well and remove the > CONFIG in the process. This might break configurations relying on the flying car joke to be there. > > > --- > > > drivers/virtio/Kconfig | 6 ------ > > > 1 file changed, 6 deletions(-) > > > > > > diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig > > > index 078615cf2afc..eacd0b90d32b 100644 > > > --- a/drivers/virtio/Kconfig > > > +++ b/drivers/virtio/Kconfig > > > @@ -26,7 +26,6 @@ config VIRTIO_PCI > > > > > > config VIRTIO_PCI_LEGACY > > > bool "Support for legacy virtio draft 0.9.X and older devices" > > > - default y > > > depends on VIRTIO_PCI > > > ---help--- > > > Virtio PCI Card 0.9.X Draft (circa 2014) and older device support. > > > @@ -36,11 +35,6 @@ config VIRTIO_PCI_LEGACY > > > If disabled, you get a slightly smaller, non-transitional driver, > > > with no legacy compatibility. > > > > > > - So look out into your driveway. Do you have a flying car? If > > > - so, you can happily disable this option and virtio will not > > > - break. Otherwise, leave it set. Unless you're testing what > > > - life will be like in The Future. > > > - > > > If unsure, say Y. > > > > > > config VIRTIO_PMEM > > > -- > > > 2.25.0.265.gbab2e86ba0-goog > >