Date: Thu, 5 Jul 2018 07:56:22 -0700 From: John Baldwin <jhb@FreeBSD.org> To: Konstantin Belousov <kostikbel@gmail.com>, Matt Macy <mmacy@FreeBSD.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r335916 - head/sys/conf Message-ID: <6e5bc5e4-052c-877f-1c36-c72e276ff045@FreeBSD.org> In-Reply-To: <20180704142233.GB5562@kib.kiev.ua> References: <201807032305.w63N5guY063293@repo.freebsd.org> <20180704142233.GB5562@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/4/18 7:22 AM, Konstantin Belousov wrote: > On Tue, Jul 03, 2018 at 11:05:42PM +0000, Matt Macy wrote: >> Author: mmacy >> Date: Tue Jul 3 23:05:42 2018 >> New Revision: 335916 >> URL: https://svnweb.freebsd.org/changeset/base/335916 >> >> Log: >> Enable MODULE_TIED by default for modules compiled with the kernel > But why ? I think we should enable KLD_TIED to inline critical_* etc. for modules built as part of a kernel that are installed alongside the kernel in /boot/<kerneldir>. I don't think we need to support modules built with kernel A loaded into kernel B. I think we should not enable it for "standalone" module builds done in ports or via "cd /sys/modules/foo; make" that install to /boot/modules so that those modules can work with different kernels. This still permits someone to load a module into kernel A that they had disabled in kernel A's config file (via NO_MODULES or MODULES_OVERRIDE or some such) by doing 'cd /sys/modules/foo; make; make load'. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6e5bc5e4-052c-877f-1c36-c72e276ff045>