From owner-freebsd-arch@FreeBSD.ORG Sat Feb 9 23:09:58 2008 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9494816A418; Sat, 9 Feb 2008 23:09:58 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 5983813C455; Sat, 9 Feb 2008 23:09:58 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m19N52t7034681; Sat, 9 Feb 2008 16:05:03 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 09 Feb 2008 16:08:17 -0700 (MST) Message-Id: <20080209.160817.168016724.imp@bsdimp.com> To: des@des.no From: "M. Warner Losh" In-Reply-To: <86sl02e736.fsf@ds4.des.no> References: <200802081802.54313.jhb@freebsd.org> <86sl02e736.fsf@ds4.des.no> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: arch@freebsd.org Subject: Re: [PATCH] Automatic kernel version module dependencies.. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2008 23:09:58 -0000 In message: <86sl02e736.fsf@ds4.des.no> Dag-Erling_Sm=F8rgrav writes: : John Baldwin writes: : > So one of the things that people run into periodically are problems= : > with mismatched kernels and modules. My understanding of our kerne= l : > module ABI compatibility is that if you build a module on in a X.Y : > build environment the module should work fine for all kernels with : > version X.Z where Z >=3D Y. : = : ...provided they were built from the same config... I think : MUTEX_PROFILING has been fixed, but there may still be cases where th= e : ABI changes dependening on kernel options. These are usually well documented. But I can't find any in the current doc set. Maybe you could point me at options that do this so we can document them (and maybe add a #warning when compiling with them)? Warner