Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.189.118]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 3FEDC781A60 for ; Thu, 30 Jan 2020 22:00:15 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 1BCF92DE45E5; Thu, 30 Jan 2020 22:00:13 +0000 (UTC) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 11D8E2DE42C4; Thu, 30 Jan 2020 22:00:11 +0000 (UTC) Date: Thu, 30 Jan 2020 23:00:04 +0100 From: Natanael Copa To: Tobias Waldekranz Cc: alpine-aports@lists.alpinelinux.org Subject: Re: [PATCH] main/linux-lts: enable VIRTIO_PCI for armv7 Message-ID: <20200130230004.1ebcbc10@ncopa-desktop.copa.dup.pw> In-Reply-To: <20200130214707.GA29092@wkz-x260> References: <20200127185955.5916-1-tobias@waldekranz.com> <20200129154459.4909eaa5@ncopa-desktop.copa.dup.pw> <20200130214707.GA29092@wkz-x260> X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-alpine-linux-musl) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Thu, 30 Jan 2020 22:47:07 +0100 Tobias Waldekranz wrote: > On Wed, Jan 29, 2020 at 03:44:59PM +0100, Natanael Copa wrote: > > On Mon, 27 Jan 2020 19:59:55 +0100 > > Tobias Waldekranz wrote: > > > > > Among other things, enables using 9p-filesystems with virtio > > > transport. > > > > There seems to pretty many changes. What are those other things? > > Yes, I'm aware that there's lots of noise here. I believe most of it > is just due to the fact that many subsystems depend on PCI. E.g. none > of the NET_VENDOR_ stuff adds any modules to the kernel, it just opens > up for configuring specific drivers. > > > Do we need pci usb host controller enabled? > > > > Is the pci serial controller needed? > > My method was basically: enable the feature I needed (VIRTIO_PCI) and > trust the kernel's defaults for the rest. But I agree that there are > some unnecessary modules here. Would you prefer them to be build as > loadable modules where possible, or left out completely? Would have preferred to remove stuff that will not be used. > > > Would it make more sense to add a linux-virt kernel for armv7 instead? > > It seems like our aarch64 linux-virt kernel has 9p over virtio. > > That would also work. The aarch64 config has VIRTIO_PCI enabled, but > unfortunately is missing 9p at the moment. Should I prepare a patch > set that: > > 1. Enables 9p on aarch64/virt. > 2. Adds an armv7/virt config. I think this makes more sense. > Or do you prefer to do it? Either way. I could likely have a look at it tomorrow morning so I'll have a look at it then, unless you beat me to it :) Thanks! -nc