[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <802e6da9-4827-a9a4-b409-f08a5de4e750@redhat.com>
Date: Tue, 14 Apr 2020 17:48:04 +0800
From: Jason Wang <jasowang@...hat.com>
To: Christian Borntraeger <borntraeger@...ibm.com>, mst@...hat.com
Cc: linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-s390@...r.kernel.org,
kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org,
netdev@...r.kernel.org, geert@...ux-m68k.org,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
Heiko Carstens <heiko.carstens@...ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>
Subject: Re: [PATCH] vhost: do not enable VHOST_MENU by default
On 2020/4/14 下午3:26, Christian Borntraeger wrote:
> On 14.04.20 04:44, Jason Wang wrote:
>> We try to keep the defconfig untouched after decoupling CONFIG_VHOST
>> out of CONFIG_VIRTUALIZATION in commit 20c384f1ea1a
>> ("vhost: refine vhost and vringh kconfig") by enabling VHOST_MENU by
>> default. Then the defconfigs can keep enabling CONFIG_VHOST_NET
>> without the caring of CONFIG_VHOST.
>>
>> But this will leave a "CONFIG_VHOST_MENU=y" in all defconfigs and even
>> for the ones that doesn't want vhost. So it actually shifts the
>> burdens to the maintainers of all other to add "CONFIG_VHOST_MENU is
>> not set". So this patch tries to enable CONFIG_VHOST explicitly in
>> defconfigs that enables CONFIG_VHOST_NET and CONFIG_VHOST_VSOCK.
>>
>> Cc: Thomas Bogendoerfer<tsbogend@...ha.franken.de>
>> Cc: Benjamin Herrenschmidt<benh@...nel.crashing.org>
>> Cc: Paul Mackerras<paulus@...ba.org>
>> Cc: Michael Ellerman<mpe@...erman.id.au>
>> Cc: Heiko Carstens<heiko.carstens@...ibm.com>
>> Cc: Vasily Gorbik<gor@...ux.ibm.com>
>> Cc: Christian Borntraeger<borntraeger@...ibm.com>
> Fine with me.
> s390 part
>
> Acked-by: Christian Borntraeger<borntraeger@...ibm.com>
>
> That was my first approach to get things fixed before I reported
> this to you.
Exactly.
Thanks
>
Powered by blists - more mailing lists