From owner-freebsd-virtualization@FreeBSD.ORG Sat Jun 7 16:51:29 2008 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DA981065671 for ; Sat, 7 Jun 2008 16:51:29 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outJ.internet-mail-service.net (outj.internet-mail-service.net [216.240.47.233]) by mx1.freebsd.org (Postfix) with ESMTP id F0F3C8FC12 for ; Sat, 7 Jun 2008 16:51:28 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id D2798247D; Sat, 7 Jun 2008 09:51:28 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 8BC222D6052; Sat, 7 Jun 2008 09:51:28 -0700 (PDT) Message-ID: <484ABC90.9070301@elischer.org> Date: Sat, 07 Jun 2008 09:51:28 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: James Gritton References: <484A23EE.8080308@gritton.org> In-Reply-To: <484A23EE.8080308@gritton.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org Subject: Re: R_xxx counterparts to the V_xxx macros X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jun 2008 16:51:29 -0000 James Gritton wrote: > There are places where a variable has been replaced with a V_ macro, > only to be set explicitly to the "virtual" data from thread0 or the > like. For example, I know of a few places where V_hostname is set like > this. > > It would make sense to have an R_hostname as well, an easy shortcut the > the real hostname instead of the virtual one. You'd need either a > static "vprocg0" structure, or a pointer somewhere to the main entry > (could be thread0 again, I suppose). Likewise with the other structures > where other globals may live. > > Perhaps many (most?) variables will only ever be referred to in their > fully virtual state. But for those where the intention is to use the > machine's "true" parameter, it would be more clear if that was made > explicit in the macro. It's an interesting idea, however what is the "real" hostname? what makes one vimage the 'real' one? theoretically you can get it via: INIT_VNET_INET(thread0.td_vnet) as you noted.. a macro that does that could be done I guess.. #define R_hostname ... I wouldn't do it for all variables however.. let us keep it in mind and when we have vimage in we'll see how useful it is. > > - Jamie > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscribe@freebsd.org"