From owner-svn-src-stable@freebsd.org Wed Apr 11 21:49:39 2018 Return-Path: Delivered-To: svn-src-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E5A8F94591; Wed, 11 Apr 2018 21:49:39 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1E286699AF; Wed, 11 Apr 2018 21:49:39 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1f6NcV-0003yu-Vt; Thu, 12 Apr 2018 00:49:35 +0300 Date: Thu, 12 Apr 2018 00:49:35 +0300 From: Slawa Olhovchenkov To: John Baldwin Cc: Konstantin Belousov , src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-11@freebsd.org Subject: Re: svn commit: r332091 - stable/11/sys/vm Message-ID: <20180411214935.GQ4305@zxy.spb.ru> References: <201804060925.w369P8c2019558@repo.freebsd.org> <84716725.OOlTe33nR2@ralph.baldwin.cx> <20180411194920.GM1774@kib.kiev.ua> <2552898.N5SmTfmv87@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2552898.N5SmTfmv87@ralph.baldwin.cx> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: svn-src-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for all the -stable branches of the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 21:49:39 -0000 On Wed, Apr 11, 2018 at 02:27:48PM -0700, John Baldwin wrote: > On Wednesday, April 11, 2018 10:49:20 PM Konstantin Belousov wrote: > > On Wed, Apr 11, 2018 at 08:52:08AM -0700, John Baldwin wrote: > > > On Monday, April 09, 2018 07:29:09 PM Slawa Olhovchenkov wrote: > > > > On Fri, Apr 06, 2018 at 09:25:08AM +0000, Konstantin Belousov wrote: > > > > > > > > > Author: kib > > > > > Date: Fri Apr 6 09:25:08 2018 > > > > > New Revision: 332091 > > > > > URL: https://svnweb.freebsd.org/changeset/base/332091 > > > > > > > > > > Log: > > > > > MFC r331760: > > > > > Make vm_map_max/min/pmap KBI stable. > > > > > > > > > > Modified: > > > > > stable/11/sys/vm/vm_map.c > > > > > stable/11/sys/vm/vm_map.h > > > > > Directory Properties: > > > > > stable/11/ (props changed) > > > > > > > > -STABLE still crashed after load vboxnet build on 11.1-RELEASE > > > > nvidia (build on 11.1-RELEASE) also don't work > > > > > > Yes, this only helps with the future KBI, it doesn't restore the > > > existing one. However, r320889 which was committed earlier should > > > have restored the KBI? > > > > I am not sure. It might have, but there might be more breakage > > accumulated. My current opinion is that both vbox and nvidia (as well as > > in-tree and out of tree drm modules) must be marked as tied. The modules > > definitely depends on much more kernel interfaces than a typical HBA or > > network controller driver, for which the stability claim is actually > > intended to apply. > > I do think virtualbox is probably too hard to make work, but I didn't think > the nvidia driver was that bad. > > I think that for kmods in ports we should consider moving to a different model > than we currently do where the port installs the source for the kernel > module to a standard location and we could have a way to rebuild all of the > modules as needed. This would permit us to provide PORTS_MODULES-type > functionality via either ports or packages (and it is a bit more flexible as > you wouldn't to deinstall/reinstall the package each time you just wanted to > rebuild the kernel module). > > I would suggest something like /usr/local/src/modules/ and a > 'LOCAL_MODULES' kernel option that is a list of ' ' to replace > PORTS_MODULES. A package could still ship an initial module by default, but > recompiling the module would either overwrite it, or if the module is built as > part of the kernel (via LOCAL_MODULES) the new one would be installed with the > kernel itself into /boot/kernel leaving the one from the package in > /boot/modules. For tied modules we could simply build it with a strict > MODULE_DEPEND line on the kernel so that the pre-built module won't load on > newer kernels and then encourage the user to use LOCAL_MODULES in pkg-message. > Using LOCAL_MODULES would be better than PORTS_MODULES as it would DTRT if you > move kernel to kernel.old during an upgrade, etc. Hmm, what about packages? I am use nvidia driver as package.