From: Ram Muthiah <rammuthiah@google.com>
To: "Michael S . Tsirkin" <mst@redhat.com>, Jason Wang <jasowang@redhat.com>
Cc: virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, kernel-team@android.com,
Ram Muthiah <rammuthiah@google.com>
Subject: [PATCH RESEND] virtio: virtio_pci_legacy: Remove default y from Kconfig
Date: Fri, 28 Feb 2020 15:27:36 -0800 [thread overview]
Message-ID: <20200228232736.182780-1-rammuthiah@google.com> (raw)
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 <rammuthiah@google.com>
---
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
next reply other threads:[~2020-02-28 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 23:27 Ram Muthiah [this message]
2020-03-01 7:32 ` [PATCH RESEND] virtio: virtio_pci_legacy: Remove default y from Kconfig Michael S. Tsirkin
2020-03-11 22:44 ` Ram Muthiah
2020-03-11 23:02 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200228232736.182780-1-rammuthiah@google.com \
--to=rammuthiah@google.com \
--cc=jasowang@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).