Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp187664pxy; Wed, 28 Apr 2021 02:09:44 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz/IPynA5hv/AbXw8cqY5kvlEYUhk6WW+Qiod4kFzR3nj/ocg6ETUKdFjDYGl+UYy8qObwr X-Received: by 2002:a05:6402:31a8:: with SMTP id dj8mr9818909edb.316.1619600984787; Wed, 28 Apr 2021 02:09:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619600984; cv=none; d=google.com; s=arc-20160816; b=NTBQ8HhRu+dkAqPjZjm05/Klu3xl/GJdTX0s0lOTlYkMycoQCEaYewMCEQfE9okQe/ 7rvonsbSxWSbMqVE0RJW7D5gRdGh8urBO/h5ORwvLhorCeBrjKv14MHbkmPQlIjLUVpY YdmsjCblJMe1gEk7CZcdK00+s76Xi1TQmd5Ohwtd7zfX42pNBiPwn2p1YllP7Alq7zfF T1OPBveULiXNtUTwg9z+OICyybELwWQUhVcCFPqpzMxItcnb7k7wlUUHtbfbgUBDNFnH V5a/yNECCVcbywJcXWbSuSsg1SEde+xJRPxZvsL/JdychAE0fNu5DDiO90iogazlUN8s PGzg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:dkim-signature; bh=Fhr6VD9MpmIRwGw/LQkBVjKYFz4C2wLpeHZjuBPrxEw=; b=MQXW1pK7J3h3GYPaOj6U+z6Ul24QDwxhDxddxuooxecIk8edpgGFDYlqSCYfwzTYpO aQhEl1bh/OZIcBEgnXUGSdVg6Kq04FoQpsycAwZSA2+JP5CHVr7NA6S/JAUS5ZgOEzw1 PCmYmagEABt0kIwwv5zijHmgf2Ty3aJRPImjGEOMJneMo6FPRICvYzEAiRZZt9K6YEQ7 FLjn+dV6pwAk9RZRAZWtH//dx3KcuvEnrp1GrSXC9UiOY5RinBZcTwIFbwF6HEAEYBqX JD60HXPYAdjQL+majz5ae02hmMXiKMzj+T3dzDAkTiYxpNEQ10RkYBCRa0lC0hxJh21+ IIpQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=K12dyoJ6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id j4si5589025edk.420.2021.04.28.02.09.20; Wed, 28 Apr 2021 02:09:44 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=K12dyoJ6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S236343AbhD1JJP (ORCPT + 99 others); Wed, 28 Apr 2021 05:09:15 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:23204 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229643AbhD1JJO (ORCPT ); Wed, 28 Apr 2021 05:09:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1619600909; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Fhr6VD9MpmIRwGw/LQkBVjKYFz4C2wLpeHZjuBPrxEw=; b=K12dyoJ6FUTb7XJozjP3pAYRBfr/077POcjMw+WVC3GYu75zFeSOfrTut0165Vl6A27pWx 1/EKw27F87Si4QzUjGSY+la6MroEuSHBd/Awa5Lsv/mMjEOH7GVVr65zAXpqp5NQ0D7N80 yRJevCwKjZy/PbK6aQOQ6r1I+yv3qq4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-489-0_PvrvcsMLaWe9oxDTpISQ-1; Wed, 28 Apr 2021 05:08:27 -0400 X-MC-Unique: 0_PvrvcsMLaWe9oxDTpISQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 00D4D19251A4; Wed, 28 Apr 2021 09:08:26 +0000 (UTC) Received: from gondolin.fritz.box (ovpn-113-113.ams2.redhat.com [10.36.113.113]) by smtp.corp.redhat.com (Postfix) with ESMTP id 48FE919C45; Wed, 28 Apr 2021 09:08:24 +0000 (UTC) Date: Wed, 28 Apr 2021 11:08:21 +0200 From: Cornelia Huck To: Christian Borntraeger Cc: Thomas Huth , linux-s390@vger.kernel.org, Heiko Carstens , linux-kernel@vger.kernel.org, Vasily Gorbik , Marc Hartmayer , Halil Pasic Subject: Re: [PATCH] arch/s390/configs: Change CONFIG_VIRTIO_CONSOLE to "m" Message-ID: <20210428110821.70aa5774.cohuck@redhat.com> In-Reply-To: References: <20210428082442.321327-1-thuth@redhat.com> Organization: Red Hat GmbH MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 28 Apr 2021 10:31:54 +0200 Christian Borntraeger wrote: > On 28.04.21 10:24, Thomas Huth wrote: > > In former times, the virtio-console code had to be compiled into > > the kernel since the old guest virtio transport had some hard de- > > pendencies. But since the old virtio transport has been removed in > > commit 7fb2b2d51244 ("s390/virtio: remove the old KVM virtio transport"), > > we do not have this limitation anymore. > > Commit bb533ec8bacd ("s390/config: do not select VIRTIO_CONSOLE via > > Kconfig") then also lifted the hard setting in the Kconfig system, so > > we can finally switch the CONFIG_VIRTIO_CONSOLE knob to compile this > > driver as a module now, making it more flexible for the user to only > > load it if it is really required. > > Isnt that a distro specific decision? I would be perfectly fine to have > this change in Fedora, Redhat and co. Not so sure about defconfig. > We often use the defconfig in our CI and development things to have a > kernel config that boots up fine, even without a ramdisk. I agree that > virtio console is no longer really the most important console but does > it really hurt? Is any distro using the defconfig unmodified? Having a value in the defconfig that will be sensible for most users sounds good to me, independent of what different distros choose to do. (Or am I misunderstanding the purpose of the defconfig?) For booting without a ramdisk, I see that virtio-blk and virtio-input are y, while other virtio drivers are m. That should be sufficient, shouldn't it?