From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: KVM list <kvm@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
Netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
David Hildenbrand <david@redhat.com>,
eperezma@redhat.com, "Cc: stable@vger.kernel.org,
david@redhat.com, dverkamp@chromium.org, hch@lst.de,
jasowang@redhat.com, liang.z.li@intel.com, mst@redhat.com,
tiny.windzz@gmail.com," <jasowang@redhat.com>,
lingshan.zhu@intel.com, Michal Hocko <mhocko@kernel.org>,
Nadav Amit <namit@vmware.com>,
Randy Dunlap <rdunlap@infradead.org>,
David Rientjes <rientjes@google.com>,
tiwei.bie@intel.com, tysand@google.comCc: stable@vger.kernel.org,
david@redhat.com, dverkamp@chromium.org, hch@lst.de,
jasowang@redhat.com, li
Subject: Re: [GIT PULL] vhost: fixes, vdpa
Date: Sun, 12 Apr 2020 04:37:55 -0400 [thread overview]
Message-ID: <20200412041730-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAHk-=wg7sMywb2V8gifhpUDE=DWQTvg1wDieKVc0UoOSsOrynw@mail.gmail.com>
On Sat, Apr 11, 2020 at 09:38:05AM -0700, Linus Torvalds wrote:
> On Mon, Apr 6, 2020 at 2:11 PM Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > The new vdpa subsystem with two first drivers.
>
> So this one is really annoying to configure.
>
> First it asks for vDPA driver for virtio devices (VIRTIO_VDPA) support.
>
> If you say 'n', it then asks *again* for VDPA drivers (VDPA_MENU).
>
> And then when you say 'n' to *that* it asks you for Vhost driver for
> vDPA-based backend (VHOST_VDPA).
>
> This kind of crazy needs to stop.
>
> Doing kernel configuration is not supposed to be like some truly
> horrendously boring Colossal Cave Adventure game where you have to
> search for a way out of maze of twisty little passages, all alike.
>
> Linus
Hmm it's a good point. Thanks, Linus!
I think this was copied from virtio which has drivers spread all over
the tree.
Jason, if VDPA_MENU is off, then we don't have any drivers. So what's
the point of selecting VDPA core from vhost/virtio then?
So how about this? Lightly tested. Jason, could you pls play with this
a bit more and let me know if you see any issues?
-->
vdpa: make vhost, virtio depend on menu
If user did not configure any vdpa drivers, neither vhost
nor virtio vdpa are going to be useful. So there's no point
in prompting for these and selecting vdpa core automatically.
Simplify configuration by making virtio and vhost vdpa
drivers depend on vdpa menu entry. Once done, we no longer
need a separate menu entry, so also get rid of this.
While at it, fix up the IFC entry: VDPA->vDPA for consistency
with other places.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
diff --git a/drivers/vhost/Kconfig b/drivers/vhost/Kconfig
index cb6b17323eb2..3b43411361fe 100644
--- a/drivers/vhost/Kconfig
+++ b/drivers/vhost/Kconfig
@@ -64,7 +64,7 @@ config VHOST_VDPA
tristate "Vhost driver for vDPA-based backend"
depends on EVENTFD
select VHOST
- select VDPA
+ depends on VDPA_MENU
help
This kernel module can be loaded in host kernel to accelerate
guest virtio devices with the vDPA-based backends.
diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
index 2aadf398d8cc..bf13755a5ba5 100644
--- a/drivers/virtio/Kconfig
+++ b/drivers/virtio/Kconfig
@@ -45,7 +45,7 @@ config VIRTIO_PCI_LEGACY
config VIRTIO_VDPA
tristate "vDPA driver for virtio devices"
- select VDPA
+ depend on VDPA_MENU
select VIRTIO
help
This driver provides support for virtio based paravirtual
prev parent reply other threads:[~2020-04-12 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 21:11 [GIT PULL] vhost: fixes, vdpa Michael S. Tsirkin
2020-04-07 9:50 ` Michael S. Tsirkin
2020-04-09 4:05 ` pr-tracker-bot
2020-04-11 16:38 ` Linus Torvalds
2020-04-12 8:37 ` Michael S. Tsirkin [this message]
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=20200412041730-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alexander.h.duyck@linux.intel.com \
--cc=david@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=namit@vmware.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=tiwei.bie@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=tysand@google.comCc \
--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).