From owner-freebsd-arch@FreeBSD.ORG Fri Dec 28 11:19:16 2007 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 D8C8416A469; Fri, 28 Dec 2007 11:19:16 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 240AE13C509; Fri, 28 Dec 2007 11:19:15 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4774DBB2.5060707@FreeBSD.org> Date: Fri, 28 Dec 2007 12:19:14 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: John Baldwin References: <200712271704.44796.jhb@FreeBSD.org> In-Reply-To: <200712271704.44796.jhb@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: arch@FreeBSD.org Subject: Re: kernel features MIB 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: Fri, 28 Dec 2007 11:19:16 -0000 John Baldwin wrote: > One of the things we have at work is a kern.features sysctl MIB that contains > nodes to indicate if a named feature is present. For example, on i386 we > have kern.features.pae and we auto enable -DPAE for kernel modules if the > currently running kernel is using PAE using that sysctl. > > One of the patches I want to commit soon is support for handling > shm_open/shm_unlink directly in the kernel via swap-backed VM objects (the > long-heralded memfd stuff). I would like to have the sysctl MIB so that > libc's for older releases (e.g. libc.so.6) could use the syscalls if they are > available so that shm segments are shared between compat apps (e.g. 4.x or > 6.x) and up-to-date apps. > > At work we don't have a pretty API for this at all, but I'm thinking for > FreeBSD we can do this: > > FEATURE(foo, "description of foo") > > which is a macro to create the 'kern.features.foo' node and set it to 1. Then > we could have a routine in libc: > > int feature_present(const char *name); > > That returns a boolean to indicate if a given feature is present or not by > invoking sysctlbyname(3), etc. > > Any objections to the idea? > I have wanted something like this for a long time. In ports land they often need to know this kind of thing, e.g. is compat4x support enabled in the kernel, etc. Kris