From owner-freebsd-current@FreeBSD.ORG Thu Feb 28 15:54:23 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00B921065672 for ; Thu, 28 Feb 2008 15:54:23 +0000 (UTC) (envelope-from zec@icir.org) Received: from xaqua.tel.fer.hr (xaqua.tel.fer.hr [161.53.19.25]) by mx1.freebsd.org (Postfix) with ESMTP id A71EA8FC27 for ; Thu, 28 Feb 2008 15:54:22 +0000 (UTC) (envelope-from zec@icir.org) Received: by xaqua.tel.fer.hr (Postfix, from userid 20006) id 55DD49B651; Thu, 28 Feb 2008 16:54:21 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on xaqua.tel.fer.hr X-Spam-Level: X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from [192.168.200.102] (zec2.tel.fer.hr [161.53.19.79]) by xaqua.tel.fer.hr (Postfix) with ESMTP id 65C539B64F; Thu, 28 Feb 2008 16:54:20 +0100 (CET) From: Marko Zec To: Dag-Erling =?utf-8?q?Sm=C3=B8rgrav?= Date: Thu, 28 Feb 2008 16:54:14 +0100 User-Agent: KMail/1.9.7 References: <47C39948.3080907@elischer.org> <200802281531.28052.zec@icir.org> <86zltlyuc2.fsf@ds4.des.no> In-Reply-To: <86zltlyuc2.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200802281654.14726.zec@icir.org> Cc: Julian Elischer , FreeBSD Current Subject: Re: warning of pending commit attempt. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 15:54:23 -0000 On Thursday 28 February 2008 16:27:41 Dag-Erling Sm=C3=B8rgrav wrote: > Marko Zec writes: > > Actually the patch provides certain level of support for > > virtualizing leaf sysctl nodes. So far I have only introduced > > macros for methods / data types that I've found necessary to > > virtualize, such as SYSCTL_V_OID, SYSCTL_V_STRING, SYSCTL_V_INT, > > and SYSCTL_V_PROC. [...] > > Thanks, this is exactly what I was looking for. Now all we need is a > way to start a vimage with hw.machine and hw.machine_arch set to a > vimage-specific value... So your question opens up a pandora's box... Obviously it's trivial to=20 virtualize a sysctl, but I still don't have a clear idea on what would=20 be the most convenient way of specifying start-up constraints or=20 parameters when instatiating a new vimage. At the moment each=20 virtualized variable is initialized to some system-wide compiled in=20 constant - we need to come up with a much more flexible / configurable=20 model... Marko