From owner-p4-projects@FreeBSD.ORG Mon Apr 16 21:36:14 2007 Return-Path: X-Original-To: p4-projects@freebsd.org Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id CCA4316A402; Mon, 16 Apr 2007 21:36:13 +0000 (UTC) X-Original-To: perforce@FreeBSD.org Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 861C016A40A for ; Mon, 16 Apr 2007 21:36:13 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outV.internet-mail-service.net (outV.internet-mail-service.net [216.240.47.245]) by mx1.freebsd.org (Postfix) with ESMTP id 73E7413C4BC for ; Mon, 16 Apr 2007 21:36:13 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 16 Apr 2007 14:04:42 -0700 Received: from [10.251.22.38] (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id A22B4125B02; Mon, 16 Apr 2007 14:36:12 -0700 (PDT) Message-ID: <4623EC51.4080407@elischer.org> Date: Mon, 16 Apr 2007 14:36:17 -0700 From: Julian Elischer User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Marko Zec References: <200704161051.l3GApuxA044256@repoman.freebsd.org> In-Reply-To: <200704161051.l3GApuxA044256@repoman.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Perforce Change Reviews Subject: Re: PERFORCE change 118226 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Apr 2007 21:36:14 -0000 Marko Zec wrote: > > - pf can now be kldloaded, but is not virtualized (yet) I was thinking that the following might be an interesting way to think about modules.. kldloading a module is 2 parts.. 1/ loading it in to memeory 2/ linking it in In the base vimage you do both, but in the others, then you only can link in modules that are already loaded. i.e. each vimage is responsible for linking the modules that it needs (?) loading a new module to memeory doesn't mean that the functionality is automatically available for all existing vimages... child images do not inherrit all the linked modules of the parent.. they need to link in those they need.